UiPath Activities

The UiPath Activities Guide

Create Document Validation Action



Make sure that the connection between Robot and Orchestrator is correctly established. Here you can find more information about how to connect robots to Orchestrator.
For Action Center integration, CORS/CSP settings are required. More details here.

Creates an action of type Document Validation in Orchestrator Action Center. The output of the Create Document Validation Action activity can be used with the Wait for Document Validation Action and Resume activity to suspend and resume orchestration workflows upon human action completion in Action Center.


Here you can check the -Preview versions of this activity.


Action Details

  • ActionCatalog - Specifies the name of the action catalog.
  • ActionPriority - Specifies the priority level of the action. The possible values are Low, Medium, High, and Critical. The default value is Medium.
  • ActionTitle - Specifies the title of the action.

Action Output


  • ContinueOnError - Specifies if the automation should continue even when the activity throws an error. This field only supports Boolean values (True, False). The default value is False. As a result, if the field is blank and an error is thrown, the execution of the project stops. If the value is set to True, the execution of the project continues regardless of any error.
  • DisplayName - Specifies the display name of the activity.
  • Timeout (milliseconds) - Specifies how long to wait (in milliseconds) for the activity to connect to Orchestrator before an error is thrown. The default value is 30000 milliseconds (30 sec). This field supports only integer and Int32 variables.

Document Validation Data Input

  • AutomaticExtractionResults - The automatically generated extraction results, stored in an ExtractionResult proprietary variable. If a variable is added to this field, the results of the automatic extraction results are displayed, enabling you to review and modify them. If left empty, the Validation Station opens for the user to manually validate the data. This field supports only ExtractionResult variables.
  • DocumentObjectModel - The Document Object Model you want to use to validate the document against. This model is stored in a Document variable and can be retrieved from the Digitize Document activity. Please see the documentation of the activity for more information on how to do this. This field supports only Document variables.
  • DocumentPath - The path to the document you want to validate. This field supports only strings and String variables.
  • DocumentText - The text of the document itself, stored in a String variable. This value can be retrieved from the Digitize Document activity. Please see the documentation of the activity for more information on how to do this. This field supports only strings and String variables.
  • Taxonomy - The Taxonomy against which the document is to be processed, stored in a DocumentTaxonomy variable. This object can be obtained by using a Load Taxonomy activity or by deserializing a string into a DocumentTaxonomy object. This field supports only DocumentTaxonomy variables.


  • Private - If selected, the values of variables and arguments are no longer logged at Verbose level.

Storage Details

  • BucketFolderPath - The path of the directory inside the storage bucket where the files used as part of the action are to be stored and retrieved. This field only supports string values, with / as the separator to indicate subdirectories. For example "Finance/AccountsPayable".
  • BucketName - Specifies the name of an existing storage bucket where the action stores its data.


Make sure that you have enabled all needed permissions for Orchestrator. Go to Folder Permissions for the Robot role in Orchestrator and verify that:
For Storage Files permissions, Create and Edit options are selected.
For Storage Buckets permissions, View option is selected.
For Actions permissions, Create option is selected.

Updated about a month ago

Create Document Validation Action

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.