Appian RPA robotic processes are powered by Java code contained in a central repository. As you create or modify code, you'll need to deploy your changes for the updates to appear in the Appian RPA Console. Since you cannot directly access the source code stored in the central repository, it's recommended to use a version control system like Git to manage your Java code.
This page describes the steps you need to take to deploy code. Refer to specific guidance on how to deploy libraries. You'll need to add the workflow library definition in the Appian RPA console prior to using a workflow library in a robotic process.
Administrators can find repository configuration settings through the Appian RPA Console.
These fields are automatically populated for your environment and shouldn't need to be changed. If you change these values, robotic process executions may fail because the source code won't be accessible from the resources.
For a given method or library, you'll need to deploy the code's binary file to the repository for updates to appear in the console.
When you're ready to deploy, you'll need to compile, package and deploy the Maven project as robot binaries, using the utilities provided by Maven and Eclipse.
We are going to create a "Maven Build" configuration:
If you're using IntelliJ, click Clean and then click deploy in the Maven menu to deploy the changes. Maven will auto-push to the repository using the credentials stored in your settings.xml file.
Note: If you prefer, you can deploy using the command line. Navigate to your robotic process folder and run the command
mvn clean deploy to push the binaries.
On This Page