Loading
Feature degradation | Gmail Email delivery failureRead More
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
            Sample of Automated Document Queues

            You are here:

            1. Salesforce Help
            2. Docs
            3. Health

            Sample of Automated Document Queues

            Automate document processing by routing received documents to different queues as they progress through your workflow.

            Required Editions

            Available in: Lightning Experience

            Available in: Enterprise and Unlimited Editions with Health Cloud

            For example, design a simple workflow to route received documents to an intake queue and then to a transformed document queue. Design a more complex workflow to route documents through additional queues and processes, such as to regional teams or specialists. To help your team work more efficiently, use document queues along with the Composite API.

            As a document moves from one queue to another, your workflow can update the Received Document status to Processing, Completed, or Needs Review. To provide context, use custom text in the Status Reason field. For example, add tracking information or an invocable action failure message as a status reason.

            Use this sample flow as is or as a starting point to create your own flow.

            1. Make sure your users have access to the Intelligent Document Automation features.
              See Set Up Intelligent Document Automation Users for the user setup requirements.
            2. Set up a queue called Inbound Documents for newly received documents.
              1. Select the Received Document object.
              2. Add team members responsible for processing documents.
            3. Create and activate a record-triggered flow that moves newly received documents to the Inbound Documents queue.
              1. In the Start element, trigger the flow when a Received Document record is created and the IsActive field is True. Optimize the flow for actions and related records.
              2. Add a Get Records element that gets records of the Group object with a DeveloperName equal to the API name of your Inbound Documents queue.
              3. Add an Assignment element that sets an Owner ID variable to the Group ID from the Get Records step.
              4. Add an Update Records element that updates the Owner ID of the Received Document record that triggered the flow.
            4. Create a Received Document record from a list view or through an API. Your flow automatically assigns record ownership to the Inbound Documents queue.
            5. Set up a queue called OCR Extract Complete for documents that have had their data extracted.
              1. Select the Received Document object.
              2. Add team members responsible for processing documents.
            6. Create and activate a record-triggered flow that moves documents that have had their data extracted to the OCR Extract Complete queue.
              1. In the Start element, trigger the flow when a Received Document record is updated and the OcrStatus field is Success. Optimize the flow for actions and related records.
                Also select the option to include a Run Asynchronously path. Including this path helps prevent errors if something goes wrong with the Process Received Document invocable action that runs in the background.
              2. Add a Get Records element that gets records of the Group object with a DeveloperName equal to the API name of your OCR Extract Complete queue.
              3. Add an Assignment element that sets an Owner ID variable to the Group ID from the Get Records step.
              4. Add an Update Records element that updates the Owner ID of the Received Document record that triggered the flow.
            7. To trigger a text extraction process, attach a Content Document record to a Received Document record by uploading a file manually or using the Composite API. After a few moments, the process completes and the flow automatically assigns record ownership to the OCR Extract Complete queue.

            See Also

             
            Loading
            Salesforce Help | Article