Assigned Tasks / Assignees
Overview
LearningBuilder supports two primary mechanisms of allowing people to perform their tasks:
Queues
Assignees
In a queue, a Workflow Step is configured to be “completed by” a specific Role, which allows anyone with that Role to act on the Workflow while on that Step.
In an assignee scenario, a Workflow Step is configured to be “completed by” a specific person identified on that Workflow.
Mechanism | Example |
|---|---|
Queue | There are multiple Reviewers, and any Reviewer is capable of reviewing any arbitrary application. Configuring a “Review” Step so that it is completed by the Reviewer Role allows Reviewers to “pull” applications from the review queue as they are ready to review them. |
Assignees | There are multiple Reviewers, but each application is assigned to a specific Reviewer by an administrator. The Workflow contains an Attribute that identifies the assigned Reviewer. An Administrator selects the assigned Reviewer in that field, and only that specific person can review that application. |
Workflows using the Assignee feature can be assigned to people that do not have a LearningBuilder account. This is documented in https://heuristicsolutions.atlassian.net/wiki/spaces/DOCS/pages/427950190.
Assignees are only supported on Create Activity and Complete Activity Workflows at this time.
Configuration summary
| 1 | Assign permissionsGrant the |
| 2 | Add an Attribute to identify the AssigneeAdd an Attribute to the Workflow so that a user can identify the specific assignee to grant access to.
|
| 3 | Make a subsequent Workflow Step “completed by” that AssigneeEdit a subsequent Step in the Workflow so that it is “completed by” the Assignee Attribute you created in Step 2. This configuration means that only the person identified by that specific Attribute (or an administrator with appropriate permissions) can access the Workflow while it's on that Step. Configuring a Step to be completed by an Assignee |
The “My Tasks” Interface
When the assignee logs into LearningBuilder, they will see a Task indicator that gives access to the Workflow(s) currently assigned to them.
Known limitations
Features that do not support the Assignee functionality:
Shared Activities
Criteria-Added Activities
Stand alone Activity process, i.e Complaints
You cannot send an email to a previous Assignee, then change the Assignee field’s value with a Behavior, and then send an email to the new Assignee.
See “Technical Details”.
Technical details
The Assignee association occurs when an Action is performed and the Workflow field values are saved, which happens before any Behaviors are executed. It is important when implementing any Assignee process that if used the fields are required to ensure data is collected before behaviors like email notifications are triggered.
For more details, see https://heuristicsolutions.atlassian.net/wiki/spaces/DOCS/pages/4830232632