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
Administrators can efficiently deploy robotic processes between environments without needing to coordinate closely with the developer who coded the robotic process. You won't need access to an integrated development environment or the Nexus repository directly to collect these files. Instead, Appian RPA bundles everything into a ZIP file for administrators or non-developers to easily deploy to target environments.
The package includes the robotic process configuration and the related Java artifacts from Nexus. These artifacts include classes referenced by the robotic process, which are required for it to execute successfully. Private libraries aren't yet included in the export package and need to be deployed separately. Export packages also don't include public Maven libraries because those are already available to all robotic processes in the environment through the shared repository.
In Appian RPA:
- Go to the Robotic Processes tab in the Appian RPA Console.
- Find the robotic process you want to export and click Configure in the toolbar.
- In the robotic process configuration, click Download robotic process icon in the toolbar.
- The robotic process and associated artifacts are downloaded in a ZIP file.
- Repeat the previous steps for each robotic process you're exporting.
- Provide the packages 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 in Appian 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
Before you deploy, keep in mind:
- 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 the 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.
- If the user importing the robotic process isn't a system administrator, the user must share permissions with the robotic process. If the user and robotic process don't share permissions, they'll see an error message telling them they can't import.
- Robotic processes created in an older version of Appian RPA can be imported into newer Appian RPA environments. However, you can't import new robotic processes into older versions of Appian RPA.
To import the robotic process configuration in the Appian RPA Console:
- On the Robotic processes tab, click the Upload robotic process icon in the toolbar.
- Browse for the package or drop it into the Import Robotic Process window.
- Click Import to continue adding the items to the target environment. The items are added to the default repository.
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.
- Credentials (optional) - If your robotic process references credentials, make sure they are present in the target environment.
- 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.