Flow Approval Processes

Use the new Request Approvals component to add up to 10 flow approval processes to a record page. Delete approval submission records to meet GDPR and other compliance requirements. This release also includes performance improvements and new configuration options for the Orchestration Work Guide.

  • Add Multiple Flow Approval Processes to a Record with the Request Approvals Component
    Give submitters up to 10 autolaunched flow approval processes to select from with the Request Approvals component.
  • Debug, Suspend, and Resume Flow Approval Processes
    Approval admins can now suspend, resume, and debug approval submissions and their associated orchestration runs. Suspending and resuming gives you greater control over in-progress approval submissions. The Debug action provides run-specific diagnostic information for in-progress, suspended, and errored approval submissions.
  • Open the Next Work Item from the Same Running Flow Approval Process
    Help users complete their assigned approval work items from the same running flow approval process 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 running flow approval process. If the user has no remaining work items, 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.
  • Delete Approval Submission Records to Meet GDPR Requirements
    Fulfill GDPR and other compliance requests to delete customer data relating to approvals. When you delete a parent record, Salesforce deletes related approval submissions in a terminal state and cancels in-progress ones. You can then delete the canceled approval submissions related to the deleted parent record.
  • Update Existing Flow Approval Processes 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 running flow approval processes. 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 flow approval processes, update the flow approval process’s API version to 68.0 or later.
  • Flow Approval Processes Now Route Record-Change Events to a Dedicated Channel
    Running flow approval processes now route record-change events to a dedicated channel, reducing traffic in the step-completion channel. Previously, running flow approval processes 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 approval work items and delayed the progress of running flow approval processes. This change is automatic and requires no configuration.
  • See New and Outdated Approval Work Items Without a Manual Refresh
    The Orchestration Work Guide component automatically shows the status of your approval 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.
  • Limit Approval Work Item Visibility to Keep Review Steps Confidential
    Prevent reviewers at one step from viewing the work items assigned to reviewers at other steps. You can now set the sharing model to private to control who can view each work item, independent of approval submissions. By default, access to an approval submission extends to all its associated work items. To grant read access to other users or groups, create criteria-based sharing rules on the approval work item object.