---
schema_version: "1"
id: acd78af15ec3231a8b6ceeb1146b712426c6f6551689aff25d2145174385260c
title: Other Changes to Flow Approval Processes
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_automate_automated_approvals_other_changes.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_automated_approvals_other_changes.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: fccd50087cbd2d436bd4c78716540abdaf2d204b9ed1622f4f948ef36909a488
description: Learn about improvements to Flow Approval Processes.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Other Changes to Flow Approval Processes

Learn about improvements to Flow Approval Processes.

**Where:** This change applies to Lightning Experience in Enterprise, Performance, Unlimited, all Einstein 1, and Developer editions.

**Why:** Flow approval process designers can now:

- Provide input values and setup options one time per Flow Builder session instead of for every flow approval process debug run. Flow Builder preserves debug data such as triggering record inputs, debug options, and input variable values when you switch between Edit mode and Debug mode. Refreshing your browser or closing Flow Builder clears all debug settings. To clear debug settings manually, click **Reset Debug Settings**. Test input and test output that you set for steps aren't affected.
- Reduce email volume from approval work item notifications for individuals up the role hierarchy by using the new Send approval work item emails only to queue members setting. This approval setting limits notifications for queue-assigned approval steps to only queue members and their delegates. The setting has no effect if role hierarchy isn’t enabled.
- Use the Step panel’s Configure Test Output tab, previously known as Debug Configuration, to set test output values. The Manually Set Output Values option is now labeled Use Test Output. The new terminology reinforces that you’re specifying test values to use instead of running actual steps. All functionality remains the same.
- Place the Orchestration Work Guide, renamed from Flow Orchestration Work Guide, on the record page of an approval step’s related record in Experience Builder.
- Use the updated options in the Decision Logic section of the Decision element. See [Decision Logic Labels Were Updated for Clarity](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_ai_decision_ui_change.htm&release=260&type=5 "The labels for the Decision Logic section of the Decision element were changed to Define Manually (Default) and Define with AI (Advanced). The new labels clarify that defining conditions manually is the first choice when working with structured data. When you can't define conditions because you're working with complex or unstructured data, use AI.").