Robotic processes follow a different deployment pattern than other Appian design objects. There are some steps you should take in Appian RPA alongside your routine deployment process within Appian.
This page describes the process of deploying a robotic process in Appian. Each step includes links to relevant documentation so you can become more familiar with the process overall. As you get more experience deploying the robotic processes, you can use this page as a reference.
Prepare the robotic process and Appian deployment package
In Appian RPA:
- Export robotic process configurations:
- In the List of robotic processes in the Appian RPA Console, find the process you want to export and select the Configure icon in its Actions cell.
- On the Robotic process configuration page, click on the Download robotic process configuration icon , located in the toolbar.
- A ZIP file of the robotic process is downloaded to your computer.
- Export the robotic process source code from the Appian RPA Console or find it locally.
- NOTE: If you aren't the original developer or you don't have permissions to view the robotic process, you'll need to coordinate with the developer to acquire a ZIP file with the source code, as there is no way to download it from Nexus directly.
- Repeat the previous steps for each robotic process you're exporting.
- Provide all files to the person or team who's responsible for deploying the robotic process in the new environment.
- Prepare the deployment package.
- NOTE: The developer must make sure all robotic process dependencies are accounted for (including process models, document folders, and web APIs). There won't be any warnings on either import or export if dependencies referenced by the robotic process aren't present.
Deploy robotic processes and Appian apps
- If you don't already have a service account and API key that is used for Appian RPA,generate an API key and create service accounts for the Appian RPA connected system.
- Update the import customization file with API key for the RPA connected system.
- Update your local Maven settings to enable pushing source code from your local environment to new target environment.
- Create a new profile in pom.xml for the new environment.
- Add Nexus credentials for the new environment to the .m2 file and reference the new profile you created.
In Appian RPA:
- Deploy Appian RPA package to the target environment:
- Push the source code to the target repository.
- Import the robotic process configuration in the Appian RPA Console:
- On the Robotic processes tab, click the Upload robotic process configuration icon in the toolbar.
- Browse for the ZIP file with the robotic process.
- After uploading the file, the robotic process is deployed on the console.
- Complete the following manual configurations:
- Ensure that the correct resource is available and set up correctly.
- Verify that tags are set up appropriately between the service account and resources that need to communicate.
- Complete environment-specific configurations in the robotic process:
- Environment variables: Verify that the variables in the new environment have the correct values.
- Technical information: Verify that the source code/repo pointers are correct.
- Queue (optional) - If your robotic process is designed to process work items from a queue, configure the queues for the robotic process. This isn't part of the exported robotic process configurations, so you'll need to set this up manually.
- Schedule (optional) - If your robotic process is designed to execute on a schedule, configure the schedule for the robotic process. This isn't part of the exported robotic process configurations, so you'll need to set this up manually.
- Libraries - make sure you've also deployed any new or modified libraries that the robotic process references.
- Repeat the previous steps for each robotic process you're importing.
Finally, in Appian, deploy the Appian package according to your established process.