Versions Compared

Old Version 6

changes.mady.by.user Damian Borowiecki

Saved on

compared with

New Version Current

changes.mady.by.user Jan Dołkowski

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Proposed The proposed solution is based on Patrick’s approach for workflows Workflow: Task based update of entities.

We need to provide a generic way to handle changes in entities. Tasks should be automatically created through signals by the application backend and accessible from one place on UI and created with signals on backend site of application. the UI. All modules should be able to make contributions to the main Tasks Page.

There will be 2 types of Users interacting with the tasks:

  • Task Triage is responsible for managing what the users that can work on certain tasks. It is an actual role with the right authorities.

  • Task Executor is the person responsible for finishing executing the task. They’re defined as a group of users called Task Group.

Proposed flow of tasks:

...

Expand
titlePlantUML

@startuml

boundary DataSource as D
participant actor TaskTriage as TT
participant TaskGroup as TG
note left TG
ideally task
groups are Django groups
end note
actor TaskExecutor as TE
control TaskBasedAction as B
entity BenefciaryORM as BO
entity Task as T
queue TackActions as TA
boundary ActionStorage as AG
boundary Action as A

TT -> TG : Create Task Group
TG --> TE : Assign user to group
TG -> TT : Success
D -> B : TriggerAction(event)
B -> T : Create New Task
T -> B : Task Created
B -> D : Success
TT -> T: Assign task to group
TE -> T: Get Task
TE -> TE: Work on task
TE -> T: ResolveTask(businessStatus)
note right
This checks will be resolved by the task event.
end note
T -> TA: Trigger businessEvent(task, user, businessStatus)
TA -> TG : Get group resolve policy
note right
action and storages depends on specific events,
could be changing some data,
approviing update, etc.
for different policies we might have different
actions. sometimes one approval will be enough,
other time we want to store user decision and
act upon it later. It depends on specific task
end note
alt ANY Resolve Policy
TA -> A: PerformOperation(businessStatus)
TA -> T: CompleteTask()
else ALL Resolve Policy
TA -> A: PerformOperation(businessStatus)
TA -> TE: Save information about user completion
opt All users finished task
TA -> T: CompleteTask()
end
else N Resolve Policy
TA -> A: PerformOperation(businessStatus)
TA -> TE: Save information about user completion
opt Enough users finished task
TA -> T: CompleteTask()
end
end
@enduml

In this scenario, Tasks are defined on in the backend and triggered on by specific actions.

User Interface

...

View serves as a point in which user users can check theirs their tasks and complete the BusinessActions on them. Search criteria are used to filter on standard task fields (mentioned later on in this document).

For Task Triage:

View serves as a point in which user users can check theirs their tasks and complete BusinessActions on them. Search criteria are used to filter on standard task fields (mentioned later on in this document).

...

Type represents what kind of task the user has. Different types of tasks can have other BusinessActions.

...

Preview is an action allowing the user to check how a task affects the state. In the case of beneficiaryupdate a beneficiary update, it could display a modal explaining what changes will be applied.businessStatus allows .

Assignee is a group of users that are authorized to complete the task. Task executioner groups should have assigned approval policies that determine when a given task is considered finished by the group. It could be: at least one approval, approval threshold, all members approval.

BusinessStatus allows the user to take proper action on a given task. Possible The possible approach for this field is different for different task groups. It could be , for instance, Approve/Reject changes in an update request , or set a new amount for a policy adjustment request. It could be a 3 three-dot menu, a dropdown, or text inputs.

Assignee is group of users that are authorized for completing the task. Task executioner groups should have assigned approval policies which determine when given task is considered finished by the group. It could be: at least one approval, approval threshold, all members approval

Status represents Status represents the current state of the task. According to the FHIR standard and our current needs, we should have the following states:

  • Received - when new tasks appears appear in the system

  • Accepted - when task is assigned to the executioner

  • Completed - when changes were approved by executioner

  • Failed - when changes were not approved

...

This view shows all existing tasks in the openIMIS application. It is a low level placeholder to which other modules can contribute to. In the graphic below, Benefit Plan Tasks is a contribution from SocialProtection module. Most of the entities is are similar to ones those in the “My Tasks” view.

If a given user is a Triage but not an Executor of a task, BusinessStatus is blocked.

If give a given user is a an Executor but not Triage of a task, then the Assignee is blocked.

Entities

...

  1. Story 1 - Task Creation: As a system, when a certain event is triggered, I want to create a new task so that the corresponding workflow can be started.

  2. Story 2 - Task Management: As a Task Triage, I want to have access to all tasks I’m eligible to manage (e.g. BenefitPlanTasks).

  3. Story 3 - Task Assignment: As a Task Triage, I want to assign specific tasks to previously defined user groups.

    1. ALT: As a system, when a new task is created, I want to assign it to a user or group based on predefined rules so that the task can be executed by the appropriate party.

  4. Story 3 - Task Execution: As a task executorTask Executor, I want to see only the relevant information for the entity page and be able to validate information as necessary so that I can complete the task without confusion or errors.

  5. Story 4 - Task Completion: As a task executorTask Executor, when I finish a task, I want to update its status so that the system can determine the next steps in the workflow.

  6. Story 5 - Workflow Progression: As a system, when a task is completed, I want to determine the next steps based on the current workflow implementation and status so that the workflow can progress smoothly.

  7. Story 6 - Group Management: As a Task Triage, I want to create/update/delete group of task executioners that can be assigned to specific tasks.

...

  1. TaskCreation action is listening to an event.

Main Flow:

  1. The user performs certain action in the system.

  2. The event attached to this action is triggered

  3. TaskReceiver binded to the event gets new action

  4. New Task object is created with status RECEIVED

  5. Task is saved in storage

  6. New Task appears under “My Tasks” view for certain Task Triages

...

N/A

Postconditions:

  1. The task is has been created.

  2. Task Triage can assign the task to group.

Use Case 2 - Task Assignment:

...

  1. Task Triage has access to manage certain tasktasks.

Main Flow:

  1. Task Triage goes to the “Tasks” view

  2. Under specific extension point tasks (like Benefit Plan) Task Triage selects a group of users that will work on given task from the list of groups.

  3. Status of the task changes to ACCEPTED

...

  1. New task is saved in the system.

  2. TaskCreate event is triggered

  3. Based on criteria, the task is assigned to one group

...