Invoke RPA Process
Description
This activity executes an RPA process and retrieves the output generated by that process.
Using Process Data
You can use variables from the Process Data drawer to dynamically configure activity properties. The Process Data drawer is available in each activity's properties dialog and provides access to variables from the following categories:
- Model Data - Process-specific data variables that you define for your workflow
- Form Data - Variables from forms associated with this process
- System Data - Pre-defined system variables (e.g., Process Initiator, Activity Name, Task ID)
- Enterprise Variables - Enterprise variables created inside the AI Command Center
- Activities Outputs - Output variables from other activities in your workflow
To use a variable, simply drag and drop it from the Process Data drawer into any property field that supports variable binding (indicated by the vertical ellipse icon). You can also use variables in JavaScript or Liquid expressions. Variables are particularly useful for mapping input and output parameters when invoking RPA processes.
For more information, see Process Data Drawer.
Design Time Configuration
Display Text
Specify the activity name that shows in your process.
Process Name
Choose an RPA process that you want to execute.
Buddy Name
Choose an RPA Buddy to execute the designated RPA process.
Log Level
Choose the log level. The RPA process will execute with the selected logging level.
Execution Strategy
Choose the appropriate execution strategy. The following options are available.
| Option | Description |
|---|---|
| Synchronous | The BPA process will start executing the RPA process and will wait to finish executing before continuing. |
| Asynchronous | The BPA process will start the execution of the RPA process without waiting for it to finish. |
Wait All Incoming
The Wait All Incoming property defines how an activity behaves when it has multiple incoming execution paths. It controls whether the activity is triggered as soon as a path completes or whether the workflow engine must wait for multiple paths to complete before executing the activity.
| Options | Description |
|---|---|
| False | The activity is triggered whenever any incoming path completes. Each incoming completion can trigger a separate execution of the activity. |
| All Configured Incoming | The activity executes only after all design-time (configured) incoming paths have completed. If a path is skipped at runtime due to conditional logic, the activity may wait indefinitely. |
| All Active Incoming | The activity executes only after all runtime-active incoming paths have completed. Incoming paths that are not taken due to conditions are automatically ignored, preventing indefinite waiting and ensuring predictable execution. |
Parameters
To use the RPA process, map your input and output parameters. Input is accepted in Key Value pair format, allowing for easy assignment of values to variables such as model or form data. Drag and drop functionality simplifies the process.
Job Id
Returns the Job Id of the corresponding RPA job
On Error
All activities support the common On Error handler to control behavior on failures (Fault, Continue, Suspend, Retry). See On Error Handler.