- Release notes Action Center
- 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
- 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
- Get App Tasks
- Add Task Comment
- Update Task Labels
- Configure task timer
- Actions
- Processes
- Notifications
- Audit
Action Center
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.
Visit Processes types to learn about the generating processes for each type of action.