You are here:
Submit for Approval Action
Submit one Salesforce record for approval using Classic Approval Processes. This action doesn't submit a record for approval using Flow Approval Processes.
Required Editions
| View supported editions. |
In Flow Builder, add an Action element to your flow. In the Action field, enter Submit, and select Submit for Approval.
Set Input Values
Use values from earlier in the flow to set the inputs for the approval request.
| Input Parameter | Description |
|---|---|
| Record ID | The ID of the record that you want to submit for approval. This parameter accepts single-value resources of any type. That value is treated as text. |
| Approval Process Name or ID | The unique name or ID of the approval process that you want to submit the record to. The process needs to have the same object type as the record you specified in Record ID. Required if Skip Entry Criteria is set to true. If this parameter and Submitter ID aren’t set, the flow succeeds only when: Make sure that:
This parameter accepts single-value resources of any type. That value is treated as text. |
| Next Approver IDs | The ID of the user to be assigned the approval request when the approval process doesn’t assign the approver. This parameter accepts collection variables of type Text that include exactly one item. |
| Skip Entry Criteria | If set to true, the record isn’t evaluated against the entry criteria set on the process that is defined in Approval Process Name or ID. This parameter accepts any single-value resource of type Boolean. |
| Submission Comments | Text that you want to accompany the submission. Don’t reference merge fields or formula expressions. Submission
comments appear in the approval history for the specified record. This text also
appears in the initial approval request email if the template uses the
This parameter accepts single-value resources of any type. That value is treated as text. |
| Submitter ID | The ID for the user who submitted the record for approval. The user receives notifications about responses to the approval request. The user needs to be one of the allowed submitters for the process. If you don’t set this field, the user who launched the flow is the submitter. If a workflow rule triggers a flow that includes this element, the submitter is the user who triggered the workflow rule. Workflow rules can be triggered when a user creates or edits a record. When the record is approved or rejected, the user who launched the flow or triggered the workflow rule is notified. This parameter accepts single-value resources of any type. That value is treated as text. |
Store Output Values
To use the approval request’s outputs later in the flow, store them in variables. The values are assigned when the approval request is created.
| Optional Output Parameter | Description |
|---|---|
| Instance ID | The ID of the approval request that was submitted. This parameter accepts single-value variables of type Text, Picklist, or Multi-Select Picklist. |
| Instance Status | The status of the current approval request. Valid values are Approved, Rejected, Removed, or Pending. This parameter accepts single-value variables of type Text, Picklist, or Multi-Select Picklist. |
| New Work Item IDs | The IDs of the new items submitted to the approval request. There can be 0 or 1 approval processes. This parameter accepts collection variables of type Text. |
| Next Approver IDs | The IDs of the users who are assigned as the next approvers. This parameter accepts collection variables of type Text. |
| Record ID | The ID of the record that the flow submitted for approval. This parameter accepts single-value variables of type Text, Picklist, or Multi-Select Picklist. |
Usage
At run time, the approval request isn’t created until the interview’s transaction is completed. Transactions are complete when the interview either finishes or runs a Screen, Local Action, or Wait element.
