The capabilities described on this page are included in Appian's standard capability tier. Usage limits may apply. |
After you plan and build your robots and robotic tasks, you're ready to use them in your business processes. You can integrate them with a new or existing process model in Appian. This way, you can choose how and when the robotic task starts in the context of a broader business process.
Although there are multiple ways to execute a robotic task, this page focuses on how to use the Execute Robotic Process smart service in a process model.
To use a robotic task in your application, complete the following steps.
variables
as an output. If a robotic task variable is a CDT, you can reference a specific field using dot notation.Finally, you'll want to consider how to display or use the results of the robotic task. How you display the results is determined by your goal. If you're sharing a set of this information with others, an Appian record in your application could be a good option. Alternatively, if you're looking to troubleshoot or optimize your robotic task (notably in the development phases), you might want to take a look at the Execution Details in the Appian RPA console.
This section describes both approaches. Learn how to create a record type and populate it with details from a CDT, and how to create a record-powered grid.
Appian records aggregate and display your data to provide users with information they need, whether to act or be informed. When a robotic task execution concludes and sends information back to Appian, it's time to use it in your application.
See Create a Record Type to learn how to display robotic task results alongside your other Appian data.
Sometimes it's more helpful to view all information about a robotic task, including metadata about the execution. All of these details are available in the Appian RPA console.
To view execution details:
Deploying a robotic task between environments is an essential piece of the development lifecycle. During testing, the robotic task might access other testing environments so it doesn't manipulate production data or interact with live systems. Appian uses an import customization file to help you update certain values quickly and easily when deploying to another environment.
When deploying a robotic task, the ICF may need to include values for new or updated credentials that the robotic task references.
When you're ready to deploy robots and robotic tasks to another Appian environment, you'll include the design objects in your deployment package.
You may need to complete the following manual configurations in the target environment if your robotic task uses these options:
Use Robotic Tasks