Skip to content

tasks.md

Latest commit

 

History

History
72 lines (40 loc) · 2.25 KB

tasks.md

File metadata and controls

72 lines (40 loc) · 2.25 KB

Tasks

The Tasks microservice is a enterprise only feature.

The Tasks microservice provides mappings and functionality for User Tasks, primarily managed by the Workflow/Camunda microserivce.

Tasks allow forms (such as those from the Formio microservice) to be loaded and presented to the user through the API, Admin UI and Portal UI.

Use Cases

  1. Staff review of citizen submissions/service requests.
  2. Delayed payments.
  3. Additional requests from government to individuals/citizens.
  4. Third-party interactions that occur after initial service request submission. (Citizen starts a request, but it requires the review and approval from another citizen before it is sent to staff for processing).
  5. ...

Screenshots

...

Postman

Postman screenshot

Portal

Portal task list

Portal Task Rendering

Admin

Admin Task list

Admin Task information view

Admin Task info view after Claim action

Admin Task info view after UnClaim action

Admin Task Rendering

Admin Task Submissions List

Admin Task Submissions Info view

Data Flow

  1. Task is created in camunda with a Assignee (Individual or Staff) and a Candidate Group (Business Unit)
  2. Tasks microservice queries Camunda for user tasks. Candidate Group (Business Unit) is used for permissions management.
  3. Tasks microservice manages actions between user and Camunda.
  4. Form schema is returned based on formkey of the user task.
  5. Form is validated against form validation serve (typically Formio microservice).
  6. On successful validation data is put into a Task Submission. Task Submission is then passed into Camunda User Task as part of the Task completion endpoint in Camunda.

The Task Submissions Entity/data is used as a generic data store that stores all task submissions so that Task Drafts can be managed as well as submitting data to other systems other than Camunda.