CID OUM Project Management System

Interactive Testing Guide — Amendment Workflow

System URL: https://oumcidproject.tetupai.com

Overview

Task Table

Test Accounts

Basic Flow

Amendment Flow

System Overview

This system manages CID learning materials development projects. When a faculty member submits a request, the system automatically creates a project with 27 tasks that flow through multiple CID units.

Workflow Summary

Faculty Submit Request (PC) ↓ PC Check Faculty Submission (PC) ↓ CID Receive & Acknowledge (PC) ↓ PC Request LD from Leader (PC) ↓ Leader LD Check Module Fit (LD) [Amendment? If unfit → reopen PC Check] ↓ Leader LD Nominate LD (LD) ↓ PC Appoint LD & Provide Link (PC) ↓ LD Request Editor & GD (LD) ↓ Leader GD Appoint GD (GD) + Leader Editor Appoint Editor (Editor) [PARALLEL] ↓ ↓ GD Complete Work (GD) + Editor Complete Work (Editor) [PARALLEL] ↓___________________________↓ LD Request PD (LD) [Amendment? If quality issue → reopen GD+Editor] ↓ Leader PD Appoint PD (PD) ↓ PD Complete Round 1 (PD) ↓_________________________ ↓ ↓ IR - Internal Review (LD) + FR & Sign-off (PC) [PARALLEL] [Amendment?] ↓ ↓ Send FR to Faculty (PC) ↓ ↓ ↓ Faculty Feedback (PC) [Amendment?] ↓_________________________↓ PC Inform Lead PD (PC) ↓ Lead PD Assign Bookmarking (PD) ↓ PD Bookmarking Complete (PD) ↓ Lead PD Request QC (PD) ↓ QC Review Complete (PD) [Amendment?] ↓ Upload to myINSPIRE (PD) ↓ PC Inform CLT Hide/Unhide (PC) ↓ Project Complete (PC)

Amendment Decision Points (5 Diamonds)

Review Task	Unit	If Amendments Required
Leader LD Check Module Fit (#5)	LD	Module unfit → Reopens PC Check (#2) + cascade resets tasks 3-4
LD Request PD (#13)	LD	GD/Editor quality issue → Reopens GD (#11) + Editor (#12) tasks
IR (Internal Review) (#16)	LD	Reopens GD (#11) + PD (#15) tasks + cascade resets intermediates
Faculty Feedback (#19)	PC	Reopens LD + GD + PD tasks + cascade resets intermediates
QC Review Complete (#24)	PD	Reopens GD + PD tasks + cascade resets intermediates

Task Status Flow

Waiting → Assigned → In Progress → Done (auto) (auto) (manual) (manual) Waiting = Task exists, predecessors not yet done Assigned = Predecessors done, task activated In Progress = Staff manually started work Done = Staff completed the task

Complete Task List (27 Tasks)

Template: CID Learning Materials Development

#	Task	Unit	Stage	Depends On	Reopen Targets	Notes
1	Faculty Submit Request	PC	1	—		First task, auto-Assigned
2	PC Check Faculty Submission	PC	2	1		PC verifies docs complete
3	CID Receive & Acknowledge	PC	3	2
4	PC Request LD from Leader	PC	4	3
5	Leader LD Check Module Fit	LD	5	4	PC	🔄 Module fit? If No → reopen #2
6	Leader LD Nominate LD	LD	6	5		LD Leader nominates designer
7	PC Appoint LD & Provide Link	PC	7	6
8	LD Request Editor & GD	LD	8	7
9	Leader GD Appoint GD	GD	9	8		PARALLEL ↓
10	Leader Editor Appoint Editor	Editor	9	8		PARALLEL ↓
11	GD Complete Work	GD	10	9		PARALLEL ↓
12	Editor Complete Work	Editor	10	10		PARALLEL ↓
13	LD Request PD	LD	11	11+12	GD,Editor	🔄 Quality OK? If No → reopen #11+#12
14	Leader PD Appoint PD	PD	12	13
15	PD Complete (Round 1)	PD	13	14
16	IR (Internal Review)	LD	14	15	GD,PD	🔄 Amendments IR? PARALLEL with #17
17	FR & Sign-off	PC	14	15		PARALLEL with #16
18	Send FR to Faculty	PC	15	17
19	Faculty Feedback	PC	16	18	LD,GD,PD	🔄 Amendments FR?
20	PC Inform Lead PD (Sign-off)	PC	18	19
21	Lead PD Assign Bookmarking	PD	19	20
22	PD Bookmarking Complete	PD	20	21
23	Lead PD Request QC	PD	21	22
24	QC Review Complete	PD	22	23	GD,PD	🔄 Amendments QC?
25	Upload to myINSPIRE	PD	23	24
26	PC Inform CLT Hide/Unhide	PC	24	25
27	Project Complete	PC	25	26

Cascade Reset Behaviour

When a review task reopens targets, all intermediate tasks (between the reopened target and the review task) are also reset to Waiting. This ensures the full chain re-executes.

Example: Task 5 (Leader LD Check Module Fit, stage 5) says module unfit:

Task 2 (PC Check, stage 2) → Assigned (reopened target)
Task 3 (stage 3) → Waiting (cascade)
Task 4 (stage 4) → Waiting (cascade)
Task 5 → Waiting (review task itself)

When task 2 completes again, Auto Activate fires: 3 → 4 → 5.

Test Accounts

Password: All test accounts use the same password. Click to reveal
Test@1234

Faculty (Website User)

Name	Email	Access
Test Faculty	`[email protected]`	Web Form only (/cid-request)

CID Staff (System Users)

Name	Email	Role	Unit Lead?
Dr Nooni	`[email protected]`	System Manager	PC Lead
Pn Fadzilah	`[email protected]`	Projects Manager	LD Lead
Cik Syaliza	`[email protected]`	Projects Manager	PD Lead
En Zulhairi	`[email protected]`	System Manager	MP Lead + VE Lead
Test GD	`[email protected]`	Projects User	GD Lead
Test Editor	`[email protected]`	Projects User	Editor Lead
Test LD	`[email protected]`	Projects User	Staff (LD unit)
Test PD	`[email protected]`	Projects User	Staff (PD unit)
Test PC	`[email protected]`	Projects User	Staff (PC unit)

Test Scenario A: Basic Flow (No Amendments)

This tests the happy path where all review tasks pass without amendments.

1Faculty Submits Request

Login as: [email protected]

Action:

Go to /cid-request
Fill in: Course Code, Course Name, Faculty, Module Category, Semester
Click Submit

Expected: Success message. A new Project is created with 27 tasks.

2PC Lead Sees First Task

Login as: [email protected] (PC Lead)

Action: Go to /app/task

Expected:

"Faculty Submit Request" task is status Assigned
Task is auto-assigned to Nooni (PC Lead)
All other 26 tasks are status Waiting

3Complete Tasks Sequentially

Action: For each task in sequence:

Open the task
Change status to In Progress (optional, simulates staff starting work)
Change status to Done
Save

Expected: When a task is marked Done, its successor tasks automatically change from Waiting to Assigned.

!Key Verification Points

Check these along the way:

After task 8 (LD Request Editor & GD) is Done → tasks 9 AND 10 both become Assigned (parallel)
Task 13 (LD Request PD) only activates when BOTH task 11 (GD) AND task 12 (Editor) are Done
After task 15 (PD Complete) is Done → tasks 16 (IR) AND 17 (FR) both activate (parallel)
For review tasks (#5, #13, #16, #19, #24): set Amendments Required = No before marking Done

Test Scenario B: Amendment Workflow

This tests the amendment loop where a reviewer finds issues and sends work back for corrections.

!Prerequisites

Before testing amendments: Complete tasks 1-14 (up to "PD Complete Round 1") following the basic flow. This activates the IR review task.

AIR Review Finds Issues (Amendment Required)

Login as: [email protected] (LD Lead — does Internal Review)

Action:

Open task "IR (Internal Review)" (should be status Assigned)
Set Amendments Required? = Yes
Change status to Done
Click Save

Expected (Amendment Reopen triggers):

Task "GD Complete Work" (task 11) → reopened to Assigned
Task "PD Complete (Round 1)" (task 15) → reopened to Assigned
Intermediate tasks (12-14) → reset to Waiting
Task "IR (Internal Review)" itself → reset to Waiting
date_completed cleared on reopened tasks

BGD and PD Do Corrections

Login as: [email protected] (GD) then [email protected] (PD Lead)

Action:

Open "GD Complete Work" → set status to Done → Save
Complete intermediate tasks as they activate (LD Request PD, Leader PD Appoint PD)
Open "PD Complete (Round 1)" → set status to Done → Save

Expected:

After BOTH GD and PD are Done again, "IR (Internal Review)" auto-activates back to Assigned
The loop is ready for another review round

CIR Review Passes (No Amendments)

Login as: [email protected] (LD Lead)

Action:

Open "IR (Internal Review)" (now Assigned again)
Set Amendments Required? = No
Change status to Done
Click Save

Expected:

No tasks are reopened
Normal flow continues — successor tasks activate

Faculty Feedback Amendment (Same Pattern)

DFaculty Feedback Requires Amendments

Login as: [email protected] (PC Lead)

Action:

Complete tasks up to "Faculty Feedback" (task 19)
Open "Faculty Feedback"
Set Amendments Required? = Yes
Change status to Done → Save

Expected:

Reopens: LD task + GD task + PD task (most recent Done task per unit, stage < 16)
"Faculty Feedback" resets to Waiting

QC Review Amendment (Same Pattern)

EQC Review Requires Amendments

Login as: [email protected] (PD Lead)

Action:

Complete tasks up to "QC Review Complete" (task 24)
Open "QC Review Complete"
Set Amendments Required? = Yes
Change status to Done → Save

Expected:

Reopens: GD task + PD task (most recent Done, stage < 22)
"QC Review Complete" resets to Waiting

Amendment Verification Checklist

#	Check	Pass?
1	Review task with Amendments Required = Yes reopens correct target tasks
2	Reopened tasks change to "Assigned" status
3	Intermediate tasks (between target and review) reset to "Waiting"
4	date_completed is cleared on reopened tasks
5	date_received is preserved (not cleared)
6	Review task resets to "Waiting"
7	After corrections done, review task auto-activates to "Assigned"
8	Multiple amendment rounds work (loop 2-3 times)
9	Amendments Required = No allows normal flow to continue
10	"Amendments Required?" dropdown only visible on 5 review tasks
11	Non-review tasks do NOT show the amendments dropdown
12	Task 5 (LD check module fit): Yes → reopens task 2, resets 3+4 to Waiting
13	Task 13 (LD check quality): Yes → reopens task 11 (GD) + 12 (Editor)