This page describes the ways you can execute a robotic process.
To extend automation, robotic processes can be triggered automatically when scheduled or integrated within a process. The method you use to execute a robotic process depends on its purpose and context. Choose one of the following options that describes your use case:
|Appian RPA Console||This manual method is best for developers while testing|
|Robotic Workforce Manager (RWM)||This manual method is best for business users to initiate ad-hoc executions|
|Appian RPA connected system||This integrated method is best for developers to integrate robotic processes into a business process. After you set up the connected system, call an integration from your process model.|
|Another robotic process||This integrated method is for developers to leverage modular, reusable robotic processes|
In the Appian RPA Console, the robotic process's workflow is defined using a series of actions. You can trigger a robotic process as an action in the workflow.
Click the action to select it, then click the list icon to associate a method or module.
Enter the ID of the robotic process to execute.
You can find the robotic process ID by going to the configuration page. The ID is a read-only value generated when you create the robotic process and can't be changed.
You can manually execute a robotic process within the Appian RPA Console. Open the robotic process's configuration and click the Execute icon. The Execute robotic process page appears:
Before clicking on the Execute button , you must fill in all required fields, defined on the Robot configuration menu.
If the robot has any restrictions to keep it from executing (new executions disabled, maximum number of simultaneous executions, etc.), a warning message will appear.
The top of the Execution options window contains the required input, such as instructions. For example, in the picture above, the input of the process is a ZIP file containing the PDF files to process.
Aside from instructions, the available options for an execution appear in the Advanced options section:
To capture the robotic process execution in a video, select Enable video recording? in the list of execution options. Choose whether to capture the full recording or choose the minutes when the recording should start and end during execution. You can also specify a frame rate if you want a higher quality recording.
After the robotic process executes, you can find the video recording in the toolbar on the Execution details page.
Deferred Execution lets you set the parameters of a manual execution and delay until a chosen time. If selected, two drop-down fields appear, where you can choose the day and time of the start of the execution:
This screen contains all the information regarding the selected execution.
The information from the execution is presented in three tabs:
From the Execution details screen, you can also select icons in the toolbar to perform actions:
Go to resource From an execution, it can be very useful to go directly to resource detail page where the execution was launched.
To do so, click the Go to resource icon in the toolbar.
Re-execute You can launch a specific execution again, keeping the instructions and other input configuration as in the original. This can be useful when a specific resource was selected and the same will be selected in the re-execution.
To re-execute a robot, click on the Re-execute icon () in the toolbar.
Go to robotic process configuration You can also access the robot configuration page from the execution page, since is a common situation when you want to modify or check certain characteristics of the robot while you are developing it.
To access the robotic process configuration, click the Go to robotic process configuration icon in the toolbar.
On this tab, you can find the information regarding the workflow related to the robot for the selected execution. Though the workflow may have been changed later, you will always see the version of the workflow here as it was at the time the execution was performed.
The items shown here are:
During a robot execution, the workflow will show the action being executed at that moment highlighted. As the robot is continuing its job, the rest of the action will be highlighted accordingly.
On this tab, you will find all the information related to the results of the selected execution.
The information available here is as follows:
The execution trace, or robot's debugging log, is shown here in detail. It is very useful information for both users and development teams.
With the execution log, it is possible to follow the robot's progress through its workflow. It also shows its activity log, informational messages, exceptions and errors. Within the robot's design, you can include information that will be displayed in the execution log. Bellow you can find some of the benefits provided by the execution log:
The results of processed items are highlighted in color in this log.
At the top of this tab, you can see several types of log, which can be enabled or disabled by clicking on each icon. This way, we can focus only on one of them. The available types are shown below, grouped by its nature:
Besides, in the right-hand side there are icons to:
When the option for video recording has been enabled, you will find this icon in the upper right-hand corner that will allow you to access the video player and view the execution recording. You can also find the icon that will allow you to download the video. Both options are only available if the user has appropriate permissions.
When an execution log is very long, the final part of the log will be loaded, being able to load the full trace by clicking on View full trace.
At the beginning and the end of an execution, Appian RPA will show a summary with information about the agent, such us:
In the following image we can see this information at the beginning of the execution:
Here, we can see the same information at the end of the execution, where the platform shows also a calculation about the difference between the memory and disk usage after the robot ends:
In this example, we can see that, after the robot ends, there are about 34Mb more of free memory, 16Mb more of reserved memory and about 24Mb less of available disk space.
To run our robot, we have already seen that we need to deploy our Java code to the Maven repository specified for robot deployment. This way, it will be available for being managed from the console and the Appian RPA Agent that is running on the resource.
Remember that to deploy our robot we will execute this Maven command:
mvn clean deploy
Once this is done, we can check the robot setup on the console and that the workflow corresponds with the code. We can do this by checking if we have all the methods that we have developed for each action in the workflow (see Technical data).
By clicking on the button Start the Execution from the menu Robots on the console, the agent will download the robot and its dependencies on the resource and start the execution.
There are different ways to launch a robot.
There are two groups of execution options:
In the case of our example robot, it is not needed to fill any of the execution options, therefore it is enough to click on the execution button.
On the form that precedes the launching, we can specify several execution options:
If we enable the video recording, some specific data will be required:
Specific execution options are determined by the instructions included in the robot settings. Instructions require input data each time the robot is launched from the console. The are options Text, Password, Combo, Boolean, and File, and executions options appear differently for each one.
More on instructions.
On This Page