Task types
Multiple tasks are linked together in an activity definition to complete a task flow. Different types of tasks can be added to a task flow.
The various task types are:
- Approval Task – a task that sends an approval notification to the user who runs the task. The Partner is unable to proceed with the activity until the task is approved by the Sponsor.
- Attribute Task – a system task for assigning attributes to partners.
- Custom Fields Task– a task that maps an API response to custom fields.
- Partner Task – a task that a Partner user must run.
- Sponsor Task – a task that a Sponsor user must run.
- System Task– a task that is used to automatically start an API dialog.
If an activity has an attribute task and there are no attributes defined on the system, the Sponsor is not able to mark the activity as Final.
Approval task
The person designing an activity can use an Approval task to block the processing of the activity at a predefined point, until an unblocking request is received. When an Approval task is added, Select task to reopen up to when rejecting can be selected and a task designated as the task up to which the system should reopen tasks.
If the Send Email When Approved check box is selected, the partner gets email when the sponsor approves the approval task.
If rejecting the Approval task, a Sponsor user can change the task defined as the Task to reopen task. If the approval task is rejected, all the tasks until the task that was selected from the list at Task to reopen are reopened for processing.
Sponsor task
A sponsor task can have a role with a scope of Sponsor Only or Both. If no role is associated with the sponsor task, only the Sponsor Administrator can start that task.
If a particular role is associated with the sponsor task, the task can be run by a Sponsor user with the same role or by the Sponsor Administrator. You can change the owner of the task to another sponsor user with the same role.
Sponsor users with the correct role can run the activity by going to or . Sponsor users are only able to start the activity if the Sponsor task is the first task in the activity flow. Partner users can start the activity no matter which type of task is first.
By default, sponsor tasks are not shown to Partner users. However, to show the task to Partners, you can select the Show to Partner check box in the Sponsor Task setup window. The Partner sees the task only if the Partner user selects the Show all Tasks check box on the Task Execution page.
System task
A system task comprises of API dialogs that is used to automatically run APIs. If the API fails, the activity status updates to Error. The Sponsor user needs to resolve the root cause of the API failure.
Example
- Legal_General_Task – must be run by Partner Users who handle legal activities in the Organization
- Contract_Approval_Task – must be run by Sponsor Users who handle Contracts
- HR_General_Task – must be run by Partner Users who handle HR activities in the Organization
- Legal_Sponsor_Task – must be run by Sponsor Users who handle Legal
The Sponsor creates three roles: a Partner Only role, HR, and a Sponsor Only role. Contracts, and a Both (Partner and Sponsor) role, Legal.
- Assign the Legal_General_Task to the Legal role. (All the roles with a scope of Partner Only or Both are visible for the general task.)
- Assign the Contract_Approval_Task to the Contracts role. (All the roles with a scope of Sponsor Only or Both are visible for the Sponsor Approval task.)
- Assign the HR_General_Task to the HR role. (All the roles with a scope of Partner Only or Both are visible for the general task.)
- Assign the Legal_Sponsor_Task to the Legal role. (All the roles with a scope of Sponsor Only or Both are visible for the Sponsor Approval task.)