You are here:
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
| Available in: Lightning Experience |
| View supported editions. |
| This feature requires the MuleSoft for Flow: IDP add-on. Professional Edition requires the API access add-on. To purchase, contact your Salesforce account executive. |
| Document processing features require Einstein generative AI turned on in Setup, and Data 360 provisioned and enabled for your org. |
| MuleSoft for Flow: IDP features used with Agentforce require the Foundations or Agentforce 1 edition. To purchase these editions, contact your Salesforce account executive. |
| User Permissions Needed | |
|---|---|
| To create, read, edit, and delete document processing configurations: | Manage Document Processing Configurations |
| To open, edit, or create an orchestration in Flow Builder: | Manage Flow |
| To create screen flows for human review interfaces: | Manage Flow |
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.
- In the orchestration, add a subflow element to call the screen flow.
- Add decision elements to handle the review outcomes (approved versus rejected).
- Add actions to process the final data based on review outcomes.
-
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.
