Loading
Salesforce now sends email only from verified domains. Read More
Automate Your Business Processes
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Build the Review Interface for Extracted Document Data

            You are here:

            1. Salesforce Help
            2. Docs
            3. Automate Your Business Processes

            Build the Review Interface for Extracted Document Data

            Create a screen flow with the Review Extracted Data component so reviewers can validate and modify extracted data before the flow continues.

            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 build the review interface, ensure you have:

            • A document processing configuration that extracts the data you want to review
            • An orchestration with the Extract Data from Document action and a decision that routes to human review when your conditions are met
            • Experience creating screen flows in Flow Builder

            In record-triggered flows you can't add a screen element directly. Use an approval action and call flow orchestration to run the review flow.

            Add the Review Extracted Data component on the same flow path as the Extract Data from Document action. The flow then auto-populates Content Document ID and Document Processing Configuration ID. If your flow branches (for example, by document type), give each branch its own Extract Data from Document action and its own Review Extracted Data component. Each component gets the IDs from the extraction action in that branch. The review screen shows all fields and tables from your document processing configuration and highlights low-confidence values.

            Note
            Note When the screen flow is started from an approval action and flow orchestration (for example, a record-triggered flow that runs when a file is attached to a record), extraction and review are on different paths. You must create variables in the orchestration to pass content document ID, document processing configuration ID, and extraction output into the screen flow, and to pass the screen flow output (for example, modified data) back to the orchestration and parent flow.
            1. Create a screen flow for the human review interface.
            2. Add the Review Extracted Data screen component and pass the Extract Data output from the Extract Data from Document action.
            3. Add approval buttons or actions (for example, Approve, Reject, or Modify) using standard screen flow components.
            4. Add a File Preview component to show the original document alongside the extracted data.

            After you build the review interface, route the reviewed data to records and business processes. See Route Reviewed Data to Records and Business Processes.

            See Also

             
            Loading
            Salesforce Help | Article