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.

Form actions have a size limit of maximum 1MB. If you attempt to save or complete a Form action that has a size bigger than 1MB, you receive an error.

App actions are custom user actions, similar to Form actions, for which Apps provides the visual interface for rendering the task in Action Center. Apps also offers pre-made templates which allow you to customize out-of-the-box customizations for your requirements.

From Action Center, you can view your Action App, corresponding to your task, by navigating to Admin Settings, and then Tenant. Under Action Apps, you can view an Action App history, and navigate to App Studio to edit it.

Visit Working with App Actions to learn how to use the feature.

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.