You are here:
Linked Workflow Behavior and Access in Agentforce Operations
After a workflow starts running from a blueprint, understand how linked workflows behave when you pause, end, delete, or update them.
Required Editions
| License Required |
|---|
This feature is a workspace that’s external to your Salesforce org and requires an Agentforce Operations license. To purchase an Agentforce Operations license, contact your Salesforce account executive. |
Pausing and Ending
| Action | Result |
|---|---|
| Pause parent | Agentforce Operations automatically pauses all child workflows. The system notifies the child workflow owner by email. If you update the workflow owner, the person who updated the owner also receives a notification. If the workflow doesn't have an owner, the default owner receives the notification. |
| Pause child | A problem indicator appears on the linked child workflow task in the parent. |
| Resume parent | Agentforce Operations resumes any child workflows that the system paused when you paused the parent. The system removes the problem indicator. |
| End child | A problem indicator appears on the linked child workflow task in the parent. workflow |
| End parent | Agentforce Operations stops all child workflows. The system notifies the child workflow owner by email. If you update the workflow owner, the person who updated the owner also receives a notification. If the workflow doesn't have an owner, the default owner receives the notification. |
Deletion
| Action | Result |
|---|---|
| Parent workflow deleted | Agentforce Operations automatically unlinks the child workflow. The child's header shows that you deleted the parent. |
| Child workflow deleted | A problem indicator appears in the linked child workflow task in the parent workflow. |
| Child blueprint deleted before child workflow starts | The linked workflow task can't start and shows a Blueprint no longer exists warning. |
Access
Access levels aren't inherited between parent and child blueprints and workflows. People with view or edit access levels to the parent don't automatically get access to the child. Grant access levels as needed and make sure that the access matches across parent and child blueprints and workflows.
To publish a parent blueprint with child blueprints, a user must have access rights to publish blueprints on the parent blueprint and the child blueprint.
To start a parent workflow with child workflows, a user must have access rights to start workflows from the parent blueprint and the child blueprint.
Approvals
To add an approval step for a linked blueprint, set an approval task to start after the linked blueprint task. At run time, Agentforce Operations automatically adds the output fields from the child workflow to the approval. You can configure the If Rejection Action to restart the task containing the linked child workflow or restart the linked workflow task itself.
Blueprint Versions
When you create a parent workflow, the system locks the version of the child blueprint. If you update the child blueprint in a new version, the existing parent workflows continue to use the version they started with.
When you create a new version of a child blueprint, Agentforce Operations notifies the workflow runner to check the parent blueprint for possible updates.
Field Passing
When you update a child blueprint with new fields, you must update the parent blueprint to pass those fields. If you don’t update the parent blueprint, at run time, new parent workflows get stuck at the linked child workflow task until you add the missing information. The parent blueprint preview shows a Missing Information warning.
If the value of an input field changes in the parent, Agentforce Operations automatically passes the new value to the child workflow. When field values passed to a child workflow change after the child has started, the system records the change in the child workflow’s activity log and sends an email notification to the workflow runner.
If you delete a field on a parent workflow that maps to a required input field on the child workflow, the child workflow can’t start. When the child workflow is blocked from starting, a warning appears on the linked child workflow task. Add a new field on the parent that maps to the required input field for the child.
If someone deletes a child workflow before it returns an expected output field, a problem appears on the linked child task in the parent workflow with details about the error.
