- 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
- 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
- Troubleshooting
Action apps
Action apps and action properties in Action Center, including the input/output property model and supported data types.
An action app is a type of app designed in UiPath Apps, whereby users can create forms or UI interactions, with specific options for tasks requiring human intervention (Action Center tasks), such as approvals. The input and output properties of the action app are defined by adding an action property.
Runtime requirement
An action app needs an available unattended or testing runtime to open. Creating an Action Center task does not use a runtime. Opening the task does, because the action app starts a serverless job on the machine template assigned to the folder.
Each open action app holds one runtime on that machine template while it runs. Assign enough unattended or testing runtimes to the template to cover the number of tasks that users open at the same time, plus some spare runtimes. A task that fails to load can still start its job later and hold a runtime for a short time.
If all runtimes are in use, the job stays pending. The task page keeps loading for about a minute, then shows an "Orchestrator job exception" error.
Action properties
An action property allows you to design and define the specifics of an Action app. Adding an action control allows you to define the input and output fields on the Action app.
Action properties cover the following categories:
- Input properties: Define the data that the users need to provide to execute an action app.
- Output properties: Define the result data from a performed Action app.
- Input/Output properties: Certain properties could be input and output.
Types of data that action definitions use
Action definitions allow different types of data in the input and output fields, such as:
- Date
- Decimal Number
- Text/String
- Yes/No answer (Boolean)
- Whole Number
These are only some examples, as many other data types can be defined.
You can also mark these properties as Mandatory, making it mandatory for users to enter a value before proceeding.
Setting up action properties
When creating or modifying an app in UiPath App Studio, you have the option to add and configure actions. It is during this process that you can configure parameters of an action using action definitions.
To learn more on how to add an action and configuring action definitions, check Adding an action to your app in the Apps guide.