- Release notes
- Before you begin
- Getting started
- Actions
- About Actions
- Exploring Actions
- Managing Actions
- Action Catalogs
- Processes
- Troubleshooting
About Actions
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.
Form actions request input through forms and they are compatible only with the form.io framework. Orchestrator handles form visualization, action assignment, and completion.
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.
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.
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.
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.
Visit Processes Types to learn about the generating processes for each type of action.
The following task statuses are available:
- Unassigned - the action has been generated in Orchestrator 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.
