Appian RPA no longer uses Nexus as its default code repository. You can still use Nexus as your code repository if your site was previously on a version below 20.3, but Nexus may be removed in a future release. To use the local Appian RPA console repository instead of Nexus, you'll need to complete a few manual steps, described on this page.
These steps apply to any Appian RPA developer who has previously developed or deployed a robotic process in the environment. If you are a new Appian RPA developer and have not deployed a robotic process prior to this release, you don't need to complete these steps. Everything is taken care of automatically.
These steps apply only to Appian RPA customers who are migrating from Nexus to the local Appian RPA console repository. If you are continuing to use Nexus or you're a new Appian RPA customer starting with this release, you won't need to make any of the changes listed below.
The repository change requires some manual steps to ensure your code deployment and robotic process executions continue as expected:
This section describes the steps to complete each of these changes.
settings.xml to use your Appian username and an API key to authenticate with the Maven repository built into the RPA Console.
To find your API key:
<servers>section of the
1 2 3 4 5 <server> <id>jidoka</id> <username>appian_username</username> <password>maven_API_key</password> </server>
See Maven Setup for more details on repository authentication.
You'll also need to update the repository URL listed in
pom.xml of each robotic process:
<url>element within the
<mydomain>is your base environment:
pom.xmlfile points to the new repo, if the old URL was listed in other spots.
Administrators need to update the default repository in Appian RPA's settings:
Developers will need to migrate their robotic process code and workflow libraries to the console repository. The simplest way to do this is to re-deploy code after the settings.xml file has been updated to reference the new repository. The robotic process's artifacts will be pushed to the new repository so it can be referenced in the console and for each subsequent robotic process execution.
Learn more about deploying code.
Finally, you'll need to update existing robotic processes so their configuration references the new repository:
On This Page