An Appian RPA robotic process is the result of the integration of all Appian RPA platform components. Powered by code, a robotic process follows steps that are configured in the Appian RPA Console and executes on a specified resource. This page discusses how to create a robotic process in Appian RPA, including some general guidelines and steps in the Console.
Robotic processes are intended to supplement human activity in an application. Robotic processes don't possess the judgment that human beings have, so there is some potential for the robotic process to encounter exceptions, or patterns the process doesn't know how to handle. Additionally, the robotic process may take a long time to execute due to application processing time. After all, the applications are designed to handle input from human beings, which is much slower than that of a robotic process.
Because of this behavior, any Appian RPA robotic process must be:
Creating a robotic process based on one in another environment? Learn how to export and import robotic processes.
As with any business technology, you'll want to consider data security in every part of your engagement with Appian RPA. Visit the Securing Data in Robotic Processes page to learn more about data security in every phase of a robotic process.
After you've set up your development environment, you're ready to create your first robot. This page demonstrates how to create a robotic process in the Appian RPA Console.
Templates give developers a head start when creating new robotic processes. A robotic process template can be configured to use your chosen set of methods, actions, queues, variables, and more to save time and avoid any of these details being overlooked during setup. Appian RPA includes some default templates for common operations, but you can create templates to share within your business or with other developers through the App Market.
To create a robotic process using a template:
When you create an Appian RPA robotic process, the source code is downloaded to your computer. In addition, the Maven project will be automatically deployed in the repository.
More on Maven setup.
A zip file with the source code is available. Copy this file into the folder where you will develop the robotic process.
A robotic process's source code uses this structure:
pom.xml(contains robotic process information and configuration details Maven needs to build properly)
Some templates include more files. Visit the template documentation to learn more about what's included.
The source code looks like this in your computer's file system:
Now you have the new robotic process created in the Appian RPA Console. Next, you'll need to configure the robotic process's workflow and technical details.
See Configuring a Robotic Process to get started.
Now let's launch the robot. Remember that the resource must be activated for execution to be successful.
Select the appropriate execution options.
To learn more about execution options, see Executing a Robotic Process.
To clone a robotic process previously created in the Appian RPA Console, go to the robotic process configuration and click Clone robotic process .
A window appears and asks you for the new robotic process name. By default, it will be the same as the robotic process you are cloning.
You can include its executions, thus keeping one robotic process's executions log on its clone. By default, executions will be included. Uncheck the Include executions option to exclude them from the copy.
On This Page