This page describes what you can see and do on the Robotic processes tab in the Appian RPA Console.
In the List of robotic processes, you can see the robotic processes you have access to.
Click on any robot to views its executions log, where detailed information about all executions performed so far is available.
Looking to create a robotic process? Head to the Developer page for more information.
This screen displays all the information regarding the selected robot. For example, you can see the "Payroll" robotic process's information, which is in charge of salary payment to every employee in a company.
You can start a new execution of this robot by clicking on the Execute button in the toolbar. By doing so, you will access the Robot execution screen.
Also in the toolbar, you can see the Configure button , where you can access the Robot setup screen.
The results section includes metrics for the results obtained by the robotic process while processing items since its first execution.
Click on the Charts icon to view the results.
The values displayed here correspond to all the executions performed by the robot, including:
This list displays specific information about each execution and lets you act on each one.
The information shown is as follows:
If it was started via API, the information entered in the corresponding parameter is included, according to the pattern:
<message> @ <resource> by <user> (api)
If it was started by an application, it will follow this pattern:
Schedule on <date> @ <resource> by <user> (cron)
If it was started by another robot ("executing robot"):
Schedule from robot <robot_name>#<num_execution> running on <executing_robot_name> @ <executed_robot_resource_name> by <user> (robot)
In addition, when an execution is canceled, the following information is shown here. For this, the existing message will be displayed with additional text, as follows:
<previous_message > canceled by <user>
|Deletes the execution and all the associated files|
|Download of the execution's trace as a plain text file|
|Change the execution from Test to Non Test and the other way around|
|Blocks / Unblocks the execution so it can't be deleted. Blocked executions are shown in bold font.|
|Pause a running execution|
|Resume a paused running execution|
|Cancel an execution|
All string values in tag symbols are dynamic.
Click an execution to access the Execution information screen, which includes the process workflow and the execution log.
It is also important to highlight that executions labeled as tests will be displayed using a specific style with a different background.
The execution log shows the robotic process's progress in its operation, through its workflow. It also shows its activity log, informational messages, exceptions and errors. Within the robotic process's design, you can include information that will be displayed in the execution log.
The execution log provides the following benefits:
Another feature provided by the console is the execution of a robot that you have registered. You can set up a robot to include execution parameters, that is, information that will guide robot's behavior during its operation.
Click the Configure icon to set up a robot from the console's Robotic Processes tab.
On the setup page, you can enter the parameters you need to guide the process's behavior as you want it to be during its operation.
Click on the Charts icon in the toolbar to view a graphical representation of the results obtained by the robot from processing items each month.
The values displayed correspond to all executions performed by the robot during the selected month (by default, current month), with the following details:
You can browse previous months to analyze the evolution of the data.
This dynamic chart shows aggregated information about all the items being processed in current executions of the robot. On the Robot executions page, click on the Executions running icon ( ).
The information shown is divided in three groups:
This option is only available for Administrators.
In the toolbar on the List of robotic processes page, you'll see a Enable/disable execution of robotic processes icon that allows you to enable or disable all robots' execution. This option is useful if you need to perform any task without robotic processes running at the same time.
When you click this icon, you'll need to confirm the action. You can also optionally add a customized message. When you confirm, a red alert will display so you know that all robotic processes' execution is disabled.
Robots currently running are not canceled, but new executions are prevented in every resource.
From the Robotic processes page, you have access to a number of other options in the toolbar.
This screen allows you to manage the different sessions saved with the documenter tool. Click the Documenter icon in the toolbar to get started.
To start working with the Documenter, first download and run its executable. After you launch the file, you will know Documenter is running by the icon shown in the taskbar.
Documenter captures the actions performed by both the keyboard and the mouse. Each time an action is performed, such as a mouse click or pressing the "Enter" key, the icon highlights: . All these actions are automatically saved into a file using the filename format session-from-DATEFROM-to-DATETO.zip, which is stored with the executable itself. DATEFROM and DATETO are the initial date and the session date in YYYYMMDD_HHMMSS format.
When you have finished your session recording, right-click on the documenter icon and select Quit.
To upload a session previously recorded with the Documenter, click on the icon located on the upper right hand corner.
To access all captured actions, upload the ZIP file into the Documenter section. Once uploaded you can access the documented session where you can watch all captured images together with their associated events.
This section shows the list of sessions uploaded to the console and allows you to perform different actions on them.
The information shown is as follows:
Click on any row to see that session's details.
On this screen, you can find each action performed during the session.
The information shown is as follows:
By clicking on any row, you can access to the action's details screen. In this window, you can find a summary of the action and all its data.
You can also access any of the other actions within the session by clicking on the list located on the right side.
This screen allows you to manage the credentials available for the robotic processes in the console. You can access this section by clicking on the Credentials icon .
It is important to highlight that credentials are controlled through permissions, therefore a robotic process or library will have access only to those credentials with at least one permission in common with it. Learn more about permissions.
This section displays the list of credentials defined in the console, and allows you to perform different actions on them.
It includes the following information:
The Update password icon that appears next to the literal [PROTECTED], allows you to update the password. By clicking on that icon, you will be asked to enter the new password and confirm its value.
In the Credentials editor, you can create new credentials inside the console.
Fill these fields to create new credentials:
A library or nano-robot is a little piece of code that provides a generic functionality to the different robots defined within the Appian RPA console. The library can provide actions that can be reused from a robot's workflow to perform certain operations, or even could be invoked from the robot's code itself. For example, a library would be the robot that provides a VPN or proxy connection.
A Maven dependency is close equivalent to an Appian RPA library, since it is a piece of code that can be reused in other Maven artifacts. However, by doing so, we are introducing some coupling between our code and that library in some extent. The main difference between a Maven dependency and a library is that our Maven artifact does not need external references to it, but still it can interact with it, either invoking actions from our robot's workflow, or by direct calls using the methods provided by the Appian RPA API.
On the Libraries page, you can manage the libraries available for the robots in the console. Click the Libraries icon in the toolbar.
Libraries are protected by permissions. This means a robot can only use libraries with common permissions.
This section displays a list containing all the libraries defined within the console, and allows you to perform several actions on them.
The information shown in this list is as follows:
You can create new library definitions within the console or edit existing ones.
To edit a library definition, click on it in the List of libraries. Its data will appear in the form.
These are the fields you should fill in here:
There two buttons to work with library definitions:
This options is only available for Administrators.
The Repositories screen allows you to manage the Maven repositories that will be used by the robots to download the dependencies needed to execute.
Click on the Repositories icon in the toolbar.
The recommendation here is to sort the repositories to show the specific ones in first place and then the generic ones:
This way you ensure that robots can download everything they need to execute. An incorrect setting of the repositories can result in executions with errors, or a robot unable to execute, since the resource is not installed properly.
This section shows a list with all the repositories defined within the console, and allows you to perform different actions on them.
The information displayed is as follows:
In this section, you can add new repositories within the console.
The information you should provide here is:
In the console, you can view details about deleted robotic processes.
On This Page