|This content applies solely to Appian RPA, which should be marked separately from the Appian low-code platform on your customer order form. Not sure if you have access to Appian RPA? Contact us to find out.|
Appian RPA customers can initiate robotic processes in their Appian process models. The Execute Robotic Process smart service streamlines the integration and executes the process synchronously in the context of the overall process model. Synchronous execution is useful if you want to return data from the robotic process execution and use it in subsequent nodes in the same process model.
To execute a robotic process in Appian RPA asynchronously, you can call the integration using the Call Integration smart service. When the robotic process is executed asynchronously, the process model moves to the next node whether or not the robotic process is complete, and the results aren't automatically returned.
This smart service calls the Execute Robotic Process integration set up using an Appian RPA Connected System object. When the smart service is called, the integration is executed using the service account used to set up the connected system, not the user who initiated the process model. You won't need to configure additional permissions for this smart service to execute.
The Setup tab allows you to select or create an Appian RPA integration.
You can configure the robotic process's retry behavior if it fails the first time it executes. The smart service automatically retries when the robotic process runs into an unexpected failure during the previous execution.
Use the dropdown menu to select the number of retry attempts, up to 1. You can also use the expression editor to set the number of retries. The expression must evaluate to an integer between
When an integration is selected, the integration's inputs will automatically appear as node inputs. If you change the selected integration or the inputs of the selected integration are updated outside the Process Modeler, the node inputs will be refreshed the next time you view the Data tab.
|Success||Boolean||No||Whether the robotic process started successfully or not.|
|ExecutionId||Text||No||Id of the robotic process execution displayed in the Appian RPA Console.|
|Status||Text||No||If the robotic process is started successfully, returns one of the following values: ENQUEUED, RUNNING, SUCCESS, FAILURE, ABORTED. If the status is anything other than SUCCESS or FAILURE, variables may include partial results.|
|Variables||Map||No||Variables configured by the developer in the robotic process configuration.|
|Retries||Integer||No||The number of time the robotic process had to retry before successfully executing.|
|FailureSection||Text||No||If the robotic process execution fails, the name of the workflow section where the failure occurred. Returns
|Error||IntegrationError||No||If the robotic process was not started successfully, this contains information about the error encountered. If the robotic process was started successfully but has a status of FAILURE or ABORTED, error details for that process are not provided here.|
Learn more about how robotic process variables pass data between workflow actions.
Once the Execute Robotic Process smart service is initiated, the integration calls the chosen robotic process. The robotic process continues running in the background even if the process model is paused, cancelled, or deleted. To pause or cancel the robotic process, visit the Appian RPA console.
If the robotic process is queued for execution, the node remains active. The node will time out after 96 hours, for any of the following reasons:
When the node times out, you'll receive an error. If the robotic process remains in the queue, it will be removed automatically.
Execute Robotic Process Smart Service