---
schema_version: "1"
id: 861bd4373aa8266ea116cccff5f3a934e4d19d5c9a24cddc8e9889698b87f2a5
title: Route Reviewed Data to Records and Business Processes
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_flow_task_route_reviewed_data.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_flow_task_route_reviewed_data.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1e97061282e38e237f2c0fcd3faea1beb8048ca38f7f819f07c666c4e2a13ab3
description: Call the screen flow from the orchestration, branch on review outcomes, and add actions to update records, send notifications, or trigger other processes with the reviewed data.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Route Reviewed Data to Records and Business Processes

Call the screen flow from the orchestration, branch on review outcomes, and add actions to update records, send notifications, or trigger other processes with the reviewed data.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=platform.flow_ref_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Learn about the editions and user interfaces that support Flow Builder. Some Flow Builder features integrate with other Salesforce products that require additional licenses.">View supported editions.</a></td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">This feature requires the MuleSoft for Flow: IDP add-on. <strong>Professional</strong> Edition requires the API access add-on. To purchase, contact your Salesforce account executive.</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Document processing features require <a href="https://help.salesforce.com/s/articleView?id=ai.generative_ai_enable.htm&amp;type=5&amp;language=en_US" target="_blank">Einstein generative AI</a> turned on in Setup, and Data 360 provisioned and enabled for your org.</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">MuleSoft for Flow: IDP features used with Agentforce require the Foundations or Agentforce 1 edition. To purchase these editions, contact your Salesforce account executive.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d159055e93">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d159055e93 ">To create, read, edit, and delete document processing
              configurations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d159055e93 ">Manage Document Processing Configurations</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d159055e93 ">To open, edit, or create an orchestration in Flow
              Builder:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d159055e93 ">Manage Flow</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d159055e93 ">To create screen flows for human review
              interfaces:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d159055e93 ">Manage Flow</td>

          </tr>
        </tbody>
      </table>

Before you route reviewed data, ensure you have:

- An orchestration with the Extract Data from Document action and a decision that routes to human review
- A screen flow with the Review Extracted Data component and approval actions
- Experience with subflows and decision elements in Flow Builder

After the review screen runs, route approved data to final processing and rejected data to notifications or alternative processes. Add actions to update or create records, send notifications, or trigger other business processes with the reviewed data.

1. In the orchestration, add a subflow element to call the screen flow.
2. Add decision elements to handle the review outcomes (approved versus rejected).
3. Add actions to process the final data based on review outcomes.
4. Test the flow with sample documents.
    
    Upload test documents and verify extraction, review workflows, and final processing steps. Confirm the flow triggers when documents are uploaded or when you run it manually, and that low-confidence extractions route to human review when configured.

Your document processing pipeline with human-in-the-loop review is complete. You can now process documents with human oversight for data validation.

To run the workflow, activate the flow and trigger it with a document. For a full walkthrough, see [Review Contract Data and Update Records with Human-in-the-Loop Example](https://help.salesforce.com/s/articleView?id=platform.automate_flow_task_example_contract_review_hitl.htm&release=264.0.0&type=5 "This example walks through a screen flow where a sales operations analyst reviews extracted contract data, corrects low-confidence values, then updates Contract and Opportunity records.").

#### See Also

- [Subflow Element](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_subflow.htm&release=264.0.0&type=5 "Launch another active flow that’s available in your org. A flow launched by another flow is called the referenced flow.")
- [Decision Element](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_decision.htm&release=264.0.0&type=5 "Evaluate a set of conditions, and route users through the flow based on the outcomes of those conditions. This element performs the equivalent of an if-then statement.")