You are here:
Considerations for Flow Approval Processes
Consider entry and exit condition requirements, events triggered by record changes, input values, and email notifications when you design and use flow approval processes.
Required Editions
| View supported editions for Flow Approval Processes. |
Entry and Exit Condition Requirements
Resources selected for a requirement for a step entry condition or a stage or step exit condition can contain flow approval process resources or global variables. There are limitations for what you can include in a requirement.
- To use a record for the Resource or Value fields, you must select a field on the record.
- The referenced record must use fields from its object, not fields from a related record.
Stage and Step Requirements
You can use up to 10 requirements to determine when a step is ready to start or when to mark a stage or an approval step complete. A change to a record referenced in one of these requirements can trigger the orchestration run associated with an approval submission to evaluate the status of the current stage and the outstanding steps within it. However, some requirement resources don’t trigger condition evaluations.
These requirement resources don’t trigger condition evaluations.
- Resource is a null record.
- Resource is a record with an invalid ID.
- Resource is a global variable in an autolaunched approval orchestration.
- Resource is a global variable other than $Record in a record-triggered approval orchestration.
- Resource is a record of an object that doesn’t support change events.
Events for Record-Change-Triggered Flow Approval Processes
A requirement for a step entry condition or a stage or step exit condition can contain a reference to a record. Changes to that record can trigger the flow approval process to evaluate the status of the current stage and the outstanding steps within it. There are limitations for when the record can trigger condition evaluations.
- The referenced record’s parent object must support change events.
- The referenced record fields aren’t IsDeleted, SystemModeStamp, or any field that’s derived from a related record or a formula.
- The referenced record can't be null or have an invalid ID.
- The referenced record can be a global variable in an a flow approval process.
Input Values for Flows
If the combined input values for a flow called by an approval step or by a background step is more than 32,768 characters, the flow approval process fails. This error can be caused by passing one or more records to a flow called by a step. To avoid this error, pass a record ID to the referenced flow, and use a Get Records element in the flow with the passed ID. Using a passed ID with a Get Records element also means that you always have the latest version of the record.
Email Notifications
When a flow called by a step fails and causes an orchestration run that's associated with a parent approval submission to fail, two email notifications are sent.
- A flow error notification
- A flow approval process error notification
