Work Order Workflow
Context
Work order is created for an approved estimate in order to award the work to CBO and then send it for the approval process. The approval process contains various workflow levels and states associated with those levels.
Scope
Work order preparation for a work by the Work Order Creator and then its verification and approval by other users (actors) in the workflow.
Details
Role (Actors) - Action Mapping
1
WORK ORDER CREATOR
Create
Search
View
Edit/ Re-submit
Submit
Reject
Junior Engineer/ Assistant Engineer
2
WORK ORDER VERIFIER
Search
View
Verify and Forward
Send Back
Executive Officer
3
WORK ORDER APPROVER
Search
View
Approve
Send Back
Send Back To Originator
Reject
Municipal Engineer
4
CBO ADMIN
Accept
Decline
Community based organization contact person (President/ Secretary)
Workflow States
1
Submit
Work Order Creator
Pending for verification
Submitted
2
Verify and Forward
Work Order Verifier
Pending for verification
Pending for approval
Verified
3
Send Back
Work Order Verifier
Pending for verification
Pending for correction
Sent Back
4
Send Back
Work Order Approver
Pending for approval
Pending for verification
Sent Back
5
Send Back To Originator
<any roles having access>
<Current Status>
Pending for correction
Sent Back
6
Edit/ Re-submit
Work Order Creator
Pending for correction
Pending for verification
Re-submitted
7
Approve
Work Order Approver
Pending for approval
Approved
Approved
8
Reject
<any roles having access>
<Current Status>
Rejected
Rejected
9
Accept
CBO Admin
Approved
Accepted
Accepted
10
Decline
CBO Admin
Approved
Pending for re-assignment
Declined
11
Edit/ Re-submit
Work Order Creator
Pending for re-assignment
Pending for verification
Re-submitted
SLAs
Work Order
Edit/ Re-submit
Pending for correction
1
Edit/ Re-submit
Pending for re-assignment
1
Verify and Forward
Pending for verification
2
Approve
Pending for approval
1
Accept
Approved
7
User Interface (UI)
UI design is going to be the same as the estimate workflow. Only the workflow states will be displayed as per the table given above.
Acceptance Criteria
1
Actions are configured based on role-action mapping.
2
Workflow states are defined as provided and the state transition is done accordingly.
Last updated