Once you log in the the WSO2 BPS the list of tasks could be viewed by clicking on the Task List link on the manage menu.
The task list page would show you the available tasks.
The following basic filtering options are present in the task list page.
The list of tasks currently assigned to you and are in progress
The claimable tasks are the list of tasks which the user can claim and reserve. Any tasks would become claimable for a particular user if he has the role of Potential Owners of the task definition.
A list of tasks which the current logged in user have the administration rights. The user can perform the administration actions like reassignment on these tasks.
A list of notifications which are accessible to the current logged in user.
A list of all tasks that the logged in user can view. This would also include all the tasks which are already completed.
The task details could be viewed when you click on the particular task id on the task list page. The task view would depend on the current status of the task and the particular user's privileges on that task.
The actions a particular user can perform on a task would depend on the privileges granted to that user and the current status of the task. These privileges will be based on the logical people group the user belongs to. For an example only the Actual Owner of the task would be able to release a task already assigned to him.
The following transition diagram shows how the task propagates from each stated based on the action performed.
The following table lists some important task actions along with the authorised logical people groups and the pre and post state transition of the task.
Action | Description | Authorised Roles | Pre-State(s) | Post-State |
---|---|---|---|---|
Claim | Claim responsibility for a task, i.e. set the task to status Reserved | Potential Owners | Ready | Reserved |
Start | Start the execution of the task | Actual Owner Potential Owners |
Ready Reserved |
InProgress |
Stop | Cancel/stop the processing of the task. The task returns to the Reserved state. | Actual Owner | InProgress | Reserved |
Suspend | Suspend the task | Task Stakeholders Business Administrator |
Ready Reserved InProgress |
Suspended |
Resume | Resume a suspended task. | Task Stakeholders Business Administrator |
Ready Reserved InProgress |
Suspended |
Skip | Skips the task | Task Initiator Task Stakeholders Business Administrator |
Suspended | Ready Reserved InProgress |
Release | Release the task, i.e. set the task back to status Ready. | Actual Owner | InProgress Reserved |
Ready |
Fail | Execution of the task fails. | Actual Owner | InProgress | Failed |
Add Comment | Add a comment to a task. | Task Stakeholders Potential Owners Actual Owner Business Administrator |
(any state) | (no state transition) |
When a task is created it would be in Ready state. Ready state means that the task is ready to be claimed by a user in the Potential Owner logical people group. A user having the Potential Owner role can claim the task by clicking on the Claim button in the task details page. When a user claims the task the, it would go to the Reserved state which means that the task is now owned by the user who claimed the particular task.
A task could be started by either of the following logical people groups. First group being the Actual Owner group which has already claimed the task. Otherwise Potential Owners can directly start a task which would automatically be claimed to the user starting the task. Once a task is started you would see the input form rendered to capture the task output. The output form would depend on the output form uploaded with the task definition. Refer the image below for a sample output form rendering.
The task completion happens with the task owner performs the completion action provided with the output rendering form.
Once the task is completed, the particular task would be moved out from the My Tasks list of the particular user.
Users can view the events occurred on a particular task by clicking on the History tab of the task details page. The task history details would contain information about the action, user who performed that operation, time stamp of the event and any state transitions due to the event. Refer the below image for a sample list of events.