Interactive Decision
The Interactive Decision activity is a blocking workflow activity that pauses workflow execution until an assigned user takes an action by clicking on appropriate button. You can use this activity to capture explicit outcomes for approvals, reviews, and other manual decision points. This activity does not evaluate conditions. It gets blocks immediately when the workflow reaches the activity and resumes only after receiving a valid outcome removed this.
- Group: Logic
- Nature: Blocking
Availability: Supported only in Standalone workflows (Record Trigger and Manual) and Stage workflows.
Runtime Behavior
When the workflow reaches the Interactive Decision activity:
The workflow pauses execution.
Email notifications are sent to the configured assignees.
Notes and the available decision options are displayed in the client application.
The workflow resumes when a appropriate action is taken through the UI or API.
If Override is selected, the workflow follows the configured Override branch.
Default Override Behavior
The activity includes Override as a default action.
Override is always available and cannot be removed.
The activity remains blocked until an assignee takes appropriate action.
When Override is invoked from CLM or any other consumer:
The workflow automatically routes to the activity configured on the Override branch.
The workflow continues executing subsequent activities without error.
Example:
In a CLM workflow, after a draft contract is generated and reviewed, an Interactive Decision activity is assigned to the Legal team. The Legal team receives a notification and selects one of the following actions:
Approve: The workflow proceeds to eSignature.
Reject: The workflow returns the contract for revision.
Cancel: The workflow terminates.
Override: The workflow routes to the configured Override branch and continues execution.
Properties and Activity Information
Field |
Description |
|---|---|
|
Details | |
|
Display Name |
Enter the name of the activity. |
|
Reference Name |
Enter the technical name of the activity. If left blank, the system automatically generates it based on the value in the Display Name field. The generated name removes special characters, eliminates spaces, avoids consecutive underscores, and joins words with a single underscore. |
|
Description |
Provide a description that is relevant to the activity. |
| Assignee | |
| Assignee | Select a User, User Group, or Team Role to specify who can complete the required actions, such as submitting approvals, generating documents, overriding tasks, or signing. The Team Role option is available only when the workflow runs on the Agreement object. Note: This functionality is currently used in CLM application but can support any object and consumer application. When the workflow reaches an activity and assigns the task, an email notification is sent to the assigned User, User Group, or Team Role.Note: An email notification is sent only if an email template is configured. Currently, the CLM team has configured email templates only for agreement-specific notifications. |
| Notes | Use this field to add text-based comments or details related to an activity. You can record important information, reminders, or context that helps users understand the purpose or status of the activity.
|
| Properties | |
| Branches | Add one or more decision branches to represent possible outcomes.
|
| Scenario | Behavior |
|---|---|
| Invalid Outcome | Workflow remains suspended |
| Unauthorized User | Workflow remains suspended |
| Issue | Possible Cause | Resolution |
|---|---|---|
| Resume API error: "Current user is not part of assignee" | User not in configured Assignee list | Verify user belongs to User/UserGroup/TeamRole |
| Workflow remains suspended after resume | Invalid Outcome or incorrect ActivityId | Ensure Outcome matches branch name and ActivityId |
| Notifications not received | Notification service and/or email configuration is misconfigured | Verify notification settings |
Use Case: Guided Contract Routing with Interactive Decisions
This use case shows how interactive decisions in workflows help guide contracts through the right approval and routing steps. At key points in the contract lifecycle, users can select predefined actions, such as sending a contract for review or signature, so the workflow progresses accurately based on business judgment. Click here for detailed steps.