Actions are tasks to be performed or undertaken by users when dealing with long-running workflows, and user intervention is required before proceeding to the next step in the workflow.
Click here for an overview of long-running workflows.

 

Enabling actions

---

To enable Actions at the tenant level in Automation Cloud:

1. Log in to your Automation Cloud account.
2. Navigate to Admin > Tenants.
3. On the desired tenant line, click the vertical ellipsis button and select Edit Services. The Edit Services window is displayed.
4. Select Actions and click Save. The changes are reflected in your Automation Cloud.

 

Action types

---

Form actions

Form actions request input through forms and they are compatible only with the form.io framework. Orchestrator handles form visualization, action assignment, and completion.

For details about the generating process, click here.

External actions

External actions are handled in external systems, such as JIRA or Salesforce, contributing to the suspend-resume cycle in an Orchestration Process, as external automation can create the action in Orchestrator and suspend the workflow until the action is completed. A form schema does not restrict them, and there is no visualization provided for such actions. Upon completion, data input is mapped back to the workflow variables.
Action assignment is handled externally, therefore external actions cannot be assigned to users.
In case the external automation cannot complete the action, you can do it instead based on an action performed within the corresponding external system. To complete an external action, you need Edit permissions on Actions and access to the associated folder.

For details about the generating process, click here.

Data Labeling actions

Data Labeling actions handle user input to identify data, coming from attached files, and add specific labels to it. The labels indicate what the data is about. These labels are later used to train ML models in AI Center^TM. Data labeling actions, based on classification, allow users to select one or more classes. Data labeling actions based on (NER) Named Entity Recognition, allow users to recognize specific entities in data.

When you select Submit inside the Data Labeling action, you save the labels that will later appear in AI Center.

You can create a Data Labeling action either through the Create Labeling Task activity, or by selecting Send to labelers. You can find the Send to labelers button in AI Center, in the Data Labeling page, inside the Label tab.

For details about the generating process, click here.

Document validation actions

Document validation actions handle user input in order to review and correct automatic data extraction results.
Document validation is performed in Orchestrator using the validation station. At action creation, document data is uploaded into a storage bucket, enabling the user to act upon it. Upon completion of the action, the validated extracted data is downloaded, and the workflow resumes. To delete the downloaded data automatically, check the Remove Data from Storage box in the Wait For Document Validation Action And Resume activity.

For details about the generating process, click here.

Document classification actions

Document classification actions handle user input in order to review and correct document classification.
Document classification is performed in Orchestrator using the classification station.
At action creation, document data is uploaded into a storage bucket, enabling the user to act upon it. Upon completion of the action, the validated classified data is downloaded, and the workflow resumes. To delete the downloaded data automatically, check the Remove Data from Storage box in the Wait For Document Classification Action And Resume activity.

For details about the generating process, click here.

🚧

Important!

Web browser access to Amazon and Azure storage buckets can sometimes be restricted due to Cross Origin Resource Sharing (CORS) and Content Security Policy (CSP) settings.
Allow identified entities in the web application.
For details on how to configure CORS and CSP settings, click here.

 

Action statuses

---

The following action statuses are available:

• Unassigned—The action has been generated and hasn't been assigned to any user.
• Pending—The action has been assigned and awaits user validation.
• Completed—The action has been validated. Once completed, validation cannot be reverted.