Configure the Orchestration Work Guide to keep users focused on completing work items from the same orchestration run. Orchestration runs are now faster and more responsive with automatic performance improvements.
- Open the Next Work Item from the Same Orchestration Run
Help users complete their assigned work items from the same orchestration run without returning to the list view. When a user completes a work item, the Orchestration Work Guide opens the next work item from the same orchestration run. If the user has no remaining work items from the same run, the component shows their updated work item list for the current record. The Automatically Open Next Work Item option is available in both Lightning App Builder and Experience Builder. - Update Existing Orchestrations to Run Background Steps Synchronously When Actions Support It
Background steps that call synchronous actions now run synchronously, reducing end-to-end latency for your orchestration runs. Previously, any background step containing an Action element ran asynchronously, regardless of whether the action itself was synchronous. To take advantage of this change in existing orchestrations, update the orchestration's API version to 68.0 or later. - See New and Outdated Orchestration Work Items Without a Manual Refresh
The Orchestration Work Guide component automatically shows the status of your orchestration work items as they change. New work items get a New badge. Work items that someone else completed are disabled and have an Outdated badge instead of disappearing from the list. Badges and completed work items remain until you leave the page or manually refresh it. - Orchestration Runs Now Route Record-Change Events to a Dedicated Channel
Orchestration runs now route record-change events to a dedicated channel, reducing traffic in the step-completion channel. Previously, orchestration runs listened to a single platform event channel containing both record-change events and step-completion events. When bulk data operations triggered thousands of record-change events, step-completion events for steps completed after that bulk update were queued behind them. Sharing the queue stalled completion of some work items and delayed orchestration progress. This change is automatic and requires no configuration.