Overview
The Starting Rule is the entry point and the first step in every workflow template. Its purpose is to start the Workflow automatically when a specific event happens or when triggered manually. The starting rule has no inbound paths, and there is exactly one per template. A new canvas renders a placeholder for the starting rule, and no other element can be added until it exists.
Prerequisites
- An existing Workflow template in draft status.
- A defined Context type for the Workflow template.
Required Permissions
- Admin permissions with Workflow configuration access.
Configuration Steps
- Navigate to Control Center.
- Select Process Studio -> Workflows and edit or create a new workflow.
- Open the Starting Rule editor by clicking the node.
- Enter or modify the starting rule Name in the Edit Starting Rule panel.
- Select the Trigger Type: Event-Based or Manually.
- Event-Based: Select an Object and an Event Type. Event types are defined per object; custom objects carry standard Created, Updated and Deleted events, while system objects define their own specific events.
- Manually: No event is configured. Manual workflows are triggered via API or via a button configured in the Views section with Workflows as the type. The button must be placed on a view inside the context, and clicking it sends the context ID. If the button sits on an object inside the context, it also sends the owner object ID.
- Enable the Conditions toggle switch to configure conditions that define the node outputs.
- Each outbound path carries its own condition.
- Path evaluation is ordered and the first match wins. The paths are evaluated in sequence, and only the first matching path will be followed during the execution.
- Path order is fixed by creation order and cannot be reordered.
- Every path requires a condition. If no conditions are defined, a default path fires immediately when the event arrives or the workflow is triggered manually.
- Click Save to apply the configuration.
Technical Considerations
- Owner Object and Context: The object selected in an event-based trigger can be the context object itself, or a related object (either dependent or reached through a relationship field). When the event fires on a related object, the execution still runs on the parent context record, and the related record is recorded as the execution's owner object. This concept drives rule scope.
- Concurrency: The same template can run more than once on the same context record simultaneously. Every time the event fires and the conditions are met, a new execution is created. Strict condition discipline is required to ensure the workflow starts only on the intended transition.
Validation
After saving the configuration and publishing the template, the starting rule will actively listen for the configured events or manual triggers. A draft template triggers nothing.
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.
Common Issue
- No Execution Created: If no path condition matches the event data, no execution is created. This is expected behavior.
- Excessive Executions: If the conditions are too loose, every update to the monitored record that passes the condition will generate a new concurrent execution.