process studio - workflows - outcome node management

  • Updated

Overview

Configure an Outcome node to define when a Workflow execution ends. When the conditions of the Outcome node are met, the execution is completed, and all other branches still in progress are stopped.

 

Key Components

  • Outcome node: A terminal element in the workflow that accepts multiple inbound paths but has no outbound paths.
  • Convergence logic: Defines the condition to satisfy the node. The Any condition marks the execution complete as soon as the first inbound branch finishes. The All condition waits for every inbound branch to finish before marking the execution complete.
  • Completion code: A required categorization code that records how the execution ended. A completion code can be used on more than one outcome node in the same template.

 

Prerequisites & Dependencies

  • A Workflow template must be created.   
  • Completion codes must be configured in the Outcome Codes tab.

 

Required Permissions

  • Admin permissions with Workflow configuration access.

 

Configuration Steps

  1. Connect the required inbound paths to the Outcome node.
  2. Click the Outcome node to display the configuration panel.

  3. Select the convergence logic from the Condition menu. Available options are Any and All.

    Note: If Any is selected, the execution completes as soon as the first inbound branch finishes. If All is selected, the execution waits for every inbound branch to finish before completion.

  4. Select a completion code from the Completion Code menu.
  5. Click Save.

 

Technical Considerations

  • When an outcome node is satisfied, the execution ends immediately. Anything still in flight on other branches stops simultaneously.
  • When an execution completes, the treatment of remaining open tasks is determined by the closing policy configured on the template.
  • Dead ends are permitted within the canvas. A path does not have to connect to an outcome node, but unconnected branches will stop silently at runtime.

 

Validation

Executions can be monitored from the global list located at Control Center -> Process Studio -> Workflows -> Running tab or within the contextual Workflows view of a specific Project or Lead record. 

When the execution reaches the Outcome node and satisfies the condition, the status of the execution is updated to Completed.

 

Limitations

  • Outcome nodes cannot be placed inside a schedule container. They exist only in the main workflow to mark where the execution ends.   
  • A template without an Outcome node produces executions that never end automatically. These executions will accumulate in the Running status until they are stopped manually.   
  • If upstream exclusivity dictates that only one branch can ever reach an Outcome node configured with All convergence, the execution will stall indefinitely.