OUM CID Request Management System
Quick Reference Guide for CID Staff
⚠️ Proof-of-Concept: The URL oumcidrequest.tetupai.com and email cidoum123@gmail.com are for testing purposes only. For production, CID OUM will need a subdomain under oum.edu.my and an official @oum.edu.my email address.
1. System Overview
This system manages requests from faculties to the Centre of Instructional Design (CID). Faculties submit requests via a web form or email. Requests are automatically assigned to the Project Coordinator (PC) team for triage and routing to the appropriate unit.
2. How Faculties Submit Requests
Method 1: Web Form (Recommended)
- Go to the Web Form URL (no login needed)
- Fill in requester info, course details, and request description
- Select Module Category and Learning Material type
- Attach file (max 50MB) or paste a Google Drive link
- Click Submit
Method 2: Email
- Send email to cidoum123@gmail.com
- Subject = Request title
- Body = Request description
- Attach files if needed
Emails are converted to tickets automatically (within 2 minutes).
3. How to Login
- Open browser → go to https://oumcidrequest.tetupai.com/app
- Enter your Email and Password
- Click Login
4. Test Accounts
| Role | Email | Password | Unit |
|---|
| Project Coordinator (Manager) | pc@test.com | Test@1234 | All Units |
| Learning Designer | ld@test.com | Test@1234 | Learning Designer |
| Graphic Designer | gd@test.com | Test@1234 | Graphic Designer |
| Publication Designer | pd@test.com | Test@1234 | Publication Designer |
| Editor | editor@test.com | Test@1234 | Editor |
| Multimedia Programmer | mp@test.com | Test@1234 | Multimedia Programmer |
| Video Editor | ve@test.com | Test@1234 | Video Editor |
| Animator | animator@test.com | Test@1234 | Animator |
Note: The PC account acts as Manager and can view all tickets across all units.
OUM CID Request System — Quick Reference (continued)
5. Ticket Form — Field Reference
| Form Label | Description |
|---|
| CID Request ID | Auto-generated unique ID (format: CID-2026-XXXXX) |
| Course Title | Course title submitted by faculty |
| Program Level | Undergraduate / Postgraduate |
| Program Name | Name of the academic program |
| Course Code | Course code (e.g., ABPG1103) |
| Semester | January / May / September |
| Task | Workflow status (Open, Faculty, PC, LD, Editor, GD, PD, QC, etc.) |
| Unit | CID unit handling the request |
| Module Category | Category of the module |
| Learning Material | ModuLearn, PiXEL, Flipbook, VidBytes, EduCast, etc. |
| Attachments | Uploaded files (max 50MB) |
| Link to Google Drive | Alternative to direct upload — shared Google Drive link |
6. Common Actions
| Action | How To |
|---|
| View ticket list | Go to /app/hd-ticket |
| Open a ticket | Click on any ticket in the list |
| Add internal comment | Scroll to bottom of ticket → type in text box → click Reply |
| Email the requester | Click New Email button → compose message → click Send |
| Change status | Change the Task dropdown → click Save |
| Reassign to another unit | Change the Unit dropdown → click Save |
7. How It Works — Request Flow
Faculty submits request (Web Form / Email)
↓
System auto-creates ticket + Contact + CID Request ID
↓
Auto-assigned to Project Coordinator
↓
PC reviews & routes to appropriate unit (LD, GD, Editor, etc.)
↓
Unit works on request → updates Task status as it progresses
↓
Resolved / Closed
8. Access Rules
| Role | Can See | Can Do |
|---|
| Staff (Agent) | Tickets from own unit only | Reply, change task, update ticket |
| Manager (PC) | All tickets from all units | Reply, reassign, change task & unit |
9. Tips
- Use the Task field to track where a request is in the workflow.
- Use Unit to route requests to the correct team.
- Use New Email to communicate directly with the faculty member.
- Internal comments are only visible to CID staff — not to the requester.
- Email submissions are processed every 2 minutes (not instant).
- For large files, ask faculty to use Google Drive and share the link.
10. Troubleshooting
| Problem | Solution |
|---|
| Cannot login | Check email/password. Clear browser cache. Try another browser. |
| Cannot see tickets | Check you are a member of the correct unit. |
| Email not converted to ticket | Wait 2–5 minutes. Check email was sent to the correct address. |
| Attachment upload failed | Ensure file is under 50MB. Try compressing to ZIP. |