OUM CID Request System

User Guide & UAT — 3 Perspectives

https://oumcidrequest.tetupai.com
⚠️ This URL is for proof-of-concept testing only. For production, CID OUM will provide a subdomain under oum.edu.my.
Faculty Member

Overview

As a faculty member, you can submit requests to the Centre of Instructional Design (CID) and track the status of your submissions. Your account is created by the CID administrator — there is no self-registration.

1. How to Login

  1. Open your browser and go to:
  2. You will be redirected to the login page.
  3. Enter your email and password provided by CID admin.
  4. Click Login.
  5. After login, you will see the ticket list page.
Login page
Login page — enter your email and password

2. Submit a New Request

  1. From the ticket list page, click the + Add Request button.
  2. The request form will open. Fill in all required fields:
FieldDescriptionRequired
Your NameAuto-filled from your profileYes
Your EmailAuto-filled from your profileYes
FacultyAuto-filled if linked; otherwise selectYes
Course TitleTitle of the courseYes
Program LevelUndergraduate or PostgraduateYes
Program NameName of the programYes
Course Codee.g. HMEF5083Yes
SemesterJanuary, May, or SeptemberYes
Year4-digit year, e.g. 2026Yes
Request DetailsFull description of your requestYes
Module CategorySelect categoryYes
Learning MaterialModuLearn, PiXEL, Flipbook, etc.Yes
Link to Google DriveUpload files to Google Drive, paste link here. Set sharing to "Anyone with the link can view".No

Click Submit. You will see a success message.

Web form for submitting requests
Web form — fill in all required fields and click Submit
✅ Expected: "Request Submitted Successfully!" message appears. A unique CID Request ID (e.g. CID-2026-00001) is generated.

3. View My Requests

  1. After submitting, click the "View My Requests" button to go back to the ticket list.
  2. You will see a list of all your submitted requests.
  3. Click on any request to view its details and current status.
✅ Expected: You can see your submitted requests. Each request shows the current Task status (e.g. Faculty, PC, LD).

4. What You Can and Cannot Do

ActionAllowed?
Submit new requests✅ Yes
View your own requests✅ Yes
Track request status✅ Yes
Add comments/replies✅ Yes
Edit request details❌ No (read-only after submission)
View other people's requests❌ No
Change task/status❌ No
⚠️ If you accidentally try to edit and save, you will see a "Read-Only Access" error. Simply close the dialog — the page will auto-refresh.

UAT Checklist — Faculty Member

  • Login with faculty account
  • Ticket list page loads after login
  • Click + Add Request — web form opens with name, email, and faculty auto-filled
  • Fill in all required fields and submit
  • Success message appears
  • "View My Requests" button navigates back to ticket list
  • Submitted request appears in the list
  • CID Request ID is in format CID-2026-XXXXX
  • Can open and view request details
  • Cannot edit request fields (read-only)
  • Can add a comment/reply on the request
  • Cannot see other users' requests
  • SLA fields are hidden
  • System activity toggle is hidden (only communications visible)
Project Coordinator (PC)

Overview

As Project Coordinator, you are the central hub for all requests. Every new request is automatically assigned to the PC unit. You review, coordinate, and route requests to the appropriate units (LD, Editor, GD, etc.). You can see all tickets across all units.

1. How to Login

  1. Go to:
  2. Enter your email and password.
  3. Click Login.

2. View All Requests

  1. After login, you will be redirected to the ticket list.
  2. You will see all tickets from all units (PC is a member of all units).
  3. Click on any ticket to open it.
✅ Expected: You can see all tickets regardless of which unit they are assigned to.
Ticket list view for PC
Ticket list — PC can see all tickets from all units

3. Review a New Request

When a faculty member submits a request, it is automatically:

  • Assigned to Project Coordinator unit
  • Task set to Faculty (default initial status)
  • PC Team Lead auto-assigned via ToDo
  • CID Request ID generated (e.g. CID-2026-00001)

Open the ticket and review the request details, course information, and Google Drive link.

4. Route Request to a Unit

After reviewing, route the request to the appropriate unit:

  1. Open the ticket.
  2. Change the Task field to the target stage (e.g. LD, Editor, GD).
  3. Change the Unit field to the target unit (e.g. Learning Designer).
  4. Click Save.
✅ Expected: Task and Unit updated. The "Task Activity" tab shows previous task as "Done" and new task as "Assigned". The unit's Team Lead is auto-assigned via ToDo.
Ticket detail view
Ticket detail — Details tab with course info, fields, and CID Request ID

5. Assign to a Specific Agent

Optionally, assign the ticket to a specific person within the unit:

  1. Open the ticket.
  2. In the sidebar (right side), find Assign To.
  3. Click and select the agent's name/email.
  4. The agent must be a member of the ticket's current unit.
⚠️ If you try to assign someone from a different unit, the system will reject it with an error message.

6. Task Activity Tab

Each ticket has a "Task Activity" tab showing all 20 task stages with status tracking:

StatusMeaningRow Color
AssignedCurrently active — this unit is working on itGreen
DoneCompleted — moved to next stageGrey
Not ApplicableSkipped — not needed for this requestYellow
(blank)Pending — not yet reachedWhite

As PC, you can:

  • View the full log of all 20 stages
  • See who is assigned and when
  • Read comments added by agents at each stage
  • Set stages to "Not Applicable" if not needed
Task Activity tab
Task Activity tab — 20 task stages with color-coded statuses (green = Assigned, grey = Done, yellow = Not Applicable)

7. Receive Completed Work from Agents

When an agent completes their task, they use the "Assignment Done" feature. This automatically:

  • Routes the ticket back to Project Coordinator unit
  • Sets Task to PC
  • Creates a comment with [Assignment Done] prefix and the agent's notes
  • Assigns the PC Team Lead via ToDo

You then review the work and route to the next unit.

8. Add Comments

  1. Open the ticket.
  2. Scroll to the bottom (Activity section).
  3. Type your comment and click Send.

Comments are also synced to the Task Activity tab under the currently assigned task row.

9. Print a Ticket

  1. Open the ticket.
  2. Click the menu (⋮) at the top right.
  3. Select Print.
  4. Choose format: "HD Ticket with Task Log" for colored task log.
  5. Print or save as PDF.

10. Task Activity Log Report

A comprehensive report that lists all task stages across all tickets in a flat, exportable table. Useful for tracking progress, monitoring workload, and generating reports.

  1. Go to the report URL: Alternatively, from the ticket list page, System Managers can click the "Task Activity Log Report" button in the toolbar.
  2. The report loads automatically with all data.
  3. Use the column header filter boxes to narrow down results (e.g. filter Task Stage = "LD", or Faculty = "Faculty of Education").
  4. Click the CID Request ID or Ticket ID to open that ticket directly.
  5. To export, click the menu (⋮) → Export to download as Excel or CSV.

What the Report Shows

Each row = one task stage from a ticket's Task Activity Log, joined with ticket metadata. Only rows with status Assigned, Done, or Not Applicable are shown.

ColumnDescription
CID Request IDClickable link to ticket (CID-2026-XXXXX)
Course TitleTicket subject
FacultyFaculty name
Course Code / Semester / YearCourse information
Program Level / Program NameProgram details
Learning MaterialModuLearn, PiXEL, etc.
Current UnitCurrent unit assignment
# / Task Stage / Task StatusTask row index, stage name, and status (Assigned/Done/Not Applicable)
Task Unit / Assigned ToUnit and person at time of assignment
Date/TimeWhen the task was assigned
CommentsTimestamped comments from agents
Ticket Created / Ticket IDCreation date and system ticket ID (clickable)

Alternate Row Coloring

Rows belonging to the same ticket share the same background color, alternating between white and light blue for each ticket group. This makes it easy to visually distinguish which rows belong to which ticket.

Task Activity Log Report
Task Activity Log Report — alternate row colors per ticket group, clickable CID Request ID

Access

RoleCan View ReportReport Button on Ticket List
System Manager✅ Yes✅ Yes
Agent Manager✅ Yes❌ No
Agent✅ Yes❌ No

UAT Checklist — Project Coordinator

  • Login with PC account
  • Can see all tickets from all units
  • New request appears with Task = Faculty, Unit = Project Coordinator
  • CID Request ID generated correctly
  • PC Team Lead auto-assigned on new ticket
  • Change Task (e.g. Faculty → LD) — Task Activity tab updates correctly
  • Change Unit (e.g. PC → Learning Designer) — Team Lead auto-assigned
  • Assign specific agent via sidebar — only unit members allowed
  • Task Activity tab shows 20 rows with correct statuses and colors
  • Can set task stage to "Not Applicable"
  • Comments sync to Task Activity tab
  • Receive ticket back from agent via Assignment Done
  • [Assignment Done] comment visible in Activity and Task Activity tab
  • Can print ticket with "HD Ticket with Task Log" format
  • Can send email to requester via "New Email" button
  • Task Activity Log Report loads at report URL
  • Report shows alternate row colors per ticket group (white / light blue)
  • CID Request ID and Ticket ID columns are clickable
  • Column filters work (e.g. filter by Task Stage or Faculty)
  • Can export report to Excel/CSV
Agent (Unit Staff)

Overview

As an agent (LD, Editor, GD, PD, Multimedia Programmer, Video Editor, Animator), you handle requests assigned to your unit. You can only see tickets assigned to your unit. When you complete your task, use the "Assignment Done" feature to route the ticket back to PC.

1. How to Login

  1. Go to:
  2. Enter your email and password.
  3. Click Login.

2. View Your Unit's Requests

  1. After login, you will be redirected to the ticket list.
  2. You will see only tickets assigned to your unit.
  3. Click on a ticket to open it.
✅ Expected: You can only see tickets where the Unit matches your team. You cannot see tickets from other units.

3. Work on a Request

  1. Open the ticket assigned to your unit.
  2. Review the request details, course info, and Google Drive link.
  3. Do your work (design, edit, review, etc.).
  4. Add comments in the Activity section to document progress.

4. Complete Your Task — Assignment Done

When you have finished your work:

  1. Open the ticket.
  2. Click the "Assignment Done" tab.
  3. Write your completion notes in the "Task Completion Notes" field.
    Example: "Content development completed for all 10 topics. Ready for editorial review."
  4. Click Save.
✅ Expected:
  • Green alert: "Assignment completed. Routing back to Project Coordinator..."
  • You are automatically redirected to the ticket list
  • The ticket is now with PC unit (you can no longer see it)
  • A comment with [Assignment Done] prefix is created
  • Task Activity tab: your task = Done, PC = Assigned
Assignment Done tab
Assignment Done tab — write your completion notes here, then click Save to route back to PC

5. Task Activity Tab

You can view the "Task Activity" tab to see the full history of the ticket's journey through all units. You can add comments in the Comments column for your assigned task row.

⚠️ You cannot change the Status column (Assigned/Done/Not Applicable) — only PC/managers can do that.

6. What You Can and Cannot Do

ActionAllowed?
View tickets in your unit✅ Yes
Add comments on tickets✅ Yes
Use Assignment Done to route back to PC✅ Yes
View Task Activity tab✅ Yes
Add comments in Task Activity tab✅ Yes
View tickets from other units❌ No
Change Task Activity status❌ No (PC/managers only)
Access system settings❌ No

UAT Checklist — Agent

  • Login with agent account
  • Can only see tickets assigned to own unit
  • Cannot see tickets from other units
  • Can open and view ticket details
  • Can add comments in Activity section
  • Comments sync to Task Activity tab
  • "Assignment Done" tab is visible
  • Fill completion notes and save
  • Green alert appears and auto-redirect to ticket list
  • Ticket no longer visible (now with PC unit)
  • [Assignment Done] comment created with notes
  • Task Activity tab: own task = Done, PC = Assigned
  • Cannot change Task Activity status column
  • Cannot access system settings or configuration
🔑 Login Accounts

Overview

All accounts use the same default password: Test@1234

Login at: https://oumcidrequest.tetupai.com

Real CID Staff Accounts

NoNameEmailRoleUnit(s)Team Lead Of
1Puan Shawira binti Abu Bakarshawira@oum.edu.mySystem ManagerPC
2Encik Zulhairi bin Salihzulhairi@oum.edu.mySystem ManagerPC, Multimedia Programmer, Video EditorMultimedia Programmer, Video Editor
3Dr Nooni Ezdiani binti Yasinnooni@oum.edu.mySystem ManagerEditor, LD, PCPC
4Puan Nor Fadzilah binti Ishakfadzylah@oum.edu.myAgentLDLD
5Cik Syaliza binti Mat Zainsyaliza@oum.edu.myAgentPDPD

Test Accounts

UnitEmailRoleTeam Lead?
Project Coordinatorpc@test.comAgentNo
Learning Designerld@test.comAgentNo
Graphic Designergd@test.comAgentYes (GD)
Publication Designerpd@test.comAgentNo
Editoreditor@test.comAgentYes (Editor)
Multimedia Programmermp@test.comAgentNo
Video Editorve@test.comAgentNo
Animatoranimator@test.comAgentYes (Animator)
⚠️ GD, Editor, and Animator units still use test accounts as Team Lead until real staff are assigned.

Role Hierarchy

RoleAccess LevelWho
System ManagerFull admin — all settings, scripts, permissionsShawira, Zulhairi, Nooni
Agent ManagerView all tickets across all unitsSystem Managers (auto-included)
AgentView tickets in own unit onlyAll staff (real + test)
Helpdesk ContactFaculty — submit and view own tickets onlyFaculty members

Team Lead Assignments

UnitTeam LeadEmail
Project CoordinatorDr Nooni Ezdiani binti Yasinnooni@oum.edu.my
Learning DesignerPuan Nor Fadzilah binti Ishakfadzylah@oum.edu.my
Publication DesignerCik Syaliza binti Mat Zainsyaliza@oum.edu.my
Multimedia ProgrammerEncik Zulhairi bin Salihzulhairi@oum.edu.my
Video EditorEncik Zulhairi bin Salihzulhairi@oum.edu.my
Graphic Designer(test account)gd@test.com
Editor(test account)editor@test.com
Animator(test account)animator@test.com

Typical Workflow

#StepWhoAction
1Submit RequestFacultyFills web form and submits
2Auto-AssignSystemTicket assigned to PC unit, PC Team Lead assigned
3Review & RoutePCReviews request, changes Task & Unit to target (e.g. LD)
4Work on RequestAgent (LD)Completes work, adds comments
5Assignment DoneAgent (LD)Writes completion notes, saves → auto-routes to PC
6Review & Route NextPCReviews LD work, routes to Editor
7......Cycle repeats through all required units
8ResolvePCSets Task to Resolved/Closed when all work complete

Troubleshooting

ProblemSolution
Cannot loginCheck email and password. Clear browser cache. Try a different browser.
Cannot see any ticketsCheck that your user is a member of the correct unit (HD Team).
"Not Permitted" errorYou may be trying to access a ticket from another unit. Go back to the ticket list.
"Read-Only Access" error (Faculty)Faculty cannot edit tickets. Close the dialog — page will auto-refresh.
Assignment rejectedYou can only assign agents who are members of the ticket's current unit.
Web form fields not loadingClear browser cache and reload. If dropdowns are empty, contact admin.

URLs Summary

PurposeURL
Login (All Users)https://oumcidrequest.tetupai.com
Ticket List (after login)https://oumcidrequest.tetupai.com/app/hd-ticket