- Release notes
- Installation and upgrade
- Before you begin
- Getting started
- Activities
- Designing long-running workflows
- Start Job And Get Reference
- Wait For Job And Resume
- Add Queue Item And Get Reference
- Wait For Queue Item And Resume
- Create Form Task
- Wait For Form Task And Resume
- Resume After Delay
- Assign Tasks
- Create External Task
- Wait For External Task And Resume
- Complete Task
- Forward Task
- Get Form Tasks
- Get Task Data
- Add Task Comment
- Update Task Labels
- Actions
- Processes
- Audit
Action types
Form Actions ask for input through forms and they are compatible with the form.io framework only. Orchestrator handles form visualization, action assignment, and completion.
According to your use cases, you can further customize your form actions. Visit Working with Form Actions to learn what features you can use inside form 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.
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.
Starting with Action Center 2021.10, document types used in Document Validation and Document Classification Actions can be created either as single files or as part of a group in their corresponding taxonomy.
Read more in our Document Understanding guide.
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.
Form Actions ask for input through forms and they are compatible with the form.io framework only. Orchestrator handles form visualization, action assignment, and completion.
According to your use cases, you can further customize your form actions. Visit Working with Form Actions to learn what features you can use inside form 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.
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.
Starting with Action Center 2021.10, document types used in Document Validation and Document Classification Actions can be created either as single files or as part of a group in their corresponding taxonomy.
Read more in our Document Understanding guide.
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.
