Workflow task
This module describes a workflow task: who it is sent to, what is expected from the recipients and what happens if they do not answer.
The lifecycle determines when the task leaves: each of its states can send one. This module defines what it holds and how it ends.
Workflow tasks apply to contents as well as to business objects (Case). A switch in the navigation bar moves from one configuration to the other.
Task options
Acceptance rule: moment when the task is considered accepted.
- All recipients have accepted
- At least one recipient has accepted: on the first acceptance.
- One recipient on each group has accepted: at least one member of each of the Groups to control acceptance, defined just below.
Attachment version (contents only): version of the document attached to the task.
- Latest version
- Attached version when launched: current version at the launch of the task.
- With specific version tag: version carrying the indicated Version tag.
Task default recipients: a user, a group or a metadata holding users or groups. Free values holding wildcards are accepted, resolved on the metadata of the content. For instance: grp_${extended.zone | lowercase}_test gives grp_eu_test.
Task supervisors: same types of values as for the recipients. The supervisors follow the progress of the task and can change its recipients.
Send email and Teams notification to supervisors for new tasks
Display lifecycle and workflow preview: displays that preview in the received task.
Comment required
Requires a comment when accepted or when rejected of the task.
Delegation
Task can be delegated: allows a recipient to hand their task to another user.
Recipients groups: restricts the users offered for delegation. Without a defined group, every user is offered.
Use delegation groups when recipients are modified from supervision: applies these same groups when a supervisor changes the recipients of the task.
Task duration
Configure a task duration: enables a reminder and an automatic action when the task drags on.
- Days before sending a reminder:
0disables the reminder. - Days before executing action:
0disables the action. - Action to execute: Reject task or Abort workflow.
Labels
Category: category the task is grouped under in the inbox.
Label of the Accept button and Label of the Reject button: these labels can be overridden by the lifecycle configuration, in the Transitions tab of a state.
Each label is entered for each language.
Message template
Text of the task received by the recipients.
Language: the message is entered for each language, chosen in the drop-down list.
Subject: subject of the message.
Body: text of the message.
Send email for new tasks: sends an email (or a Teams notification) to each recipient. When the option is active, a dedicated email template becomes configurable: sender address, subject and body.
The message of the task accepts the metadata of the content as wildcards: ${<aspect>.<metadata>}, for instance ${core.name} for the name of the document.
The email template accepts the same metadata, as well as the wildcards specific to this context:
| Wildcard | Inserted value |
|---|---|
${sender_name} | Sender of the task |
${recipient_name} | Recipient of the task |
${document_link} | Link to the document |
${task_link} | Link to the task |
For a localized metadata, [$LOCALE] is replaced by the current language. For instance: ${core.title[$LOCALE]}.