Each Verne business service may have a related review task that enables registry staff to track and perform work required to review and approve the service.
Task configuration, a.k.a. task definition, allows to specify requirements around task presentation, assignment and allowable actions. These review tasks can have the following configured:
- Task assignment:
- What team the task is initially assigned to.
- What teams the task can be reassigned to.
- Task due date:
- When the task needs to be completed by.
- Task actions:
- What task outcome options are available for each task, e.g. Approve, Reject.
- What task outcome options are available to each team, e.g. Compliance team is able to Reject and Reassign the task, but not to Approve.
Verne registers go live with tasks configured to address business requirements expressed during the design.
The task definition can be conditionally selected by a business service instance as defined in the workflow that the service is using (see service configuration setting ‘S04.1 Workflow definition’ on Business service configuration). Multiple business services can refer to the same task definition.
Configurator documentation can be found here Tasks.
Task definition consists of the three parts:
- Task details
- Teams and actions
- Action reasons
Parts (2) and (3) can be re-used by multiple task definitions, so technically in configuration they are defined separately. However in the task definition template they are combined for ease of capturing and reading the requirements.
Task details
| Task name | This is the name of the task that will be shown in the work queue or via search tasks. E.g. Register Private Company |
| Review due days | Options: specify a whole number and whether it uses working or calendar days E.g. 1 working day |
|---|---|
| Default team assignment | Options: specify code and name of one team E.g. TM01 registration team This setting determines the team that this task will be assigned to upon task creation. The task needs to be assigned to one team at all times. If initial team assignment is conditional, then this needs to be resolved by creating different task definitions with different default team assignment setting. The conditional selection of the task definition needs to be specified in service configuration setting ‘S04.3.1 Task and auto-approval details’ (see more on task settings here https://partner.fostermoore.com/products/registry-operations/business-service-configuration/). |
| Task tags | Task tags are displays as “pills” when task appears in the work queue or when it is opened for viewing. Tags are usually short words or phrases that draw reviewer’s attention to some specific content of the application or details about its submission. |
Teams and actions
This section lists all teams that this task can be assigned to, including the default team set above. For each team consultant must list actions that are allowed and that are prohibited. Verne only requires configurator to list allowed actions, however from documentation perspective it is beneficial to call out any prohibited actions to form a clear picture of team’s responsibilities.
If more than one team is listed here, then "Assign to team" option will become available and the task can be re-assigned to another team mentioned in this list.
Action reasons
These section defines if the user who selected a specific task action is required to provide reasons via ‘confirm task action’ dialog. Generally user is required to confirm the action they selected and provide reasons for it, but for some actions (such as ‘Assign to me’ or ‘Approve’) this might not be needed. For some other actions, such as assign to a team/person, more details are collected apart from reasons.
Depending on requirements Verne can enable/force user to provide reasons for the action. Reasons can be collected by selecting value(s) form the predefined list and/or by populating a free text field.
