The main way to create and edit RPA processes is to record a sequence of user actions when working with an operating system or other software. You can run a modeled process on a computer.
Let us consider the subsystem of recording and running a process.
The process recording subsystem includes the following modules:
- Recorder. Recording module. It stores all recorded activities and generates an RPA process diagram.
- Hooks. Module for intercepting user input. It intercepts events from input devices (a keyboard and a mouse) and generates activities based on the classification of these events. The generated activities are recorded to the process.
- Marker. Interface highlighting module. It obtains data about an element of an operating system or third-party software in a specified area using parsing methods. Then, the element being defined is highlighted on the screen.
- Player. Playback module. It simulates a given process by sequentially executing activities according to the process diagram.
- Emulator. Emulator of user input. It emulates working with a mouse and a keyboard in the system when running a process.
- Clipboard. Module for working with the clipboard. It interacts with the clipboard of a system when running an RPA process.
- NativeParser. Method of parsing interacting elements based on data analysis of an operating system. It is used when running and recording an RPA process.
- VisionParser. Method of parsing interacting elements based on analysis of graphical and textual information. It is used when running and recording an RPA process.
There are two ways to edit an RPA process in RPA Designer:
- Record a process by moving elements (activities) into a process diagram and configuring them.
- Record a process using the "Recorder" mode. Recorder is a state of the program that allows recording user interaction with an operating system and other software. Actions are recorded in an activity, and an RPA process diagram is created.
Activity is the smallest logical unit described in the context of an RPA process. Depending on the type, an activity consists of several simple user actions. Activities are classified and modeled at the time of recording a process. Moreover, you can configure them in more detail using additional tools. For example, when recording the "Open Browser" action, the activity consists of several simpler actions:
- Determine location of the browser shortcut on the user's desktop.
- Hover the mouse cursor over the found element.
- Double click with the left mouse button.
- Determine the moment when the browser opens and is ready for further interaction.
These are the tools for creating an RPA process used in ELMA RPA:
- Recording user actions for information input (using a mouse and a keyboard).
- Recognizing and recording metadata about elements of interaction between the user and the system (system, graphical and textual information).
- Processing system actions (working with the clipboard, opening/closing/changing the state of the software that interacts with an RPA process).
- Parameterization of an RPA process is used to run a process with specified conditions (a process context).
- Auxiliary tools for recording an RPA process (debugging tools, a wizard for creating a context, a wizard for working with images, a wizard for defining an element to interact with, etc.).
- ELMA RPA and ELMA BPM integration. A wizard for importing a context from ELMA BPM and matching it with the ELMA RPA context. This tool is used to make it easier to create and match business logic of ELMA RPA and ELMA BPM processes.
After creating an RPA process diagram, you can run it in ELMA RPA Designer. This program is switched to the playback state ("Player") and sequentially performs recorded activities.
Debugging an RPA process allows you to run only a part of the process with specified default options. In this case, the user has access to a log of the current playback of the process. It includes information about business logic of the process and technical information.
After debugging, the process is published on the server. You can run the published processes using the ELMA RPA server (the Orchestrator).
After the Orchestrator has received a task to run a process from external systems, it determines a current state of connected RPA Robots. The process is sent to the one that meets execution conditions. The bot receives the process and input parameters.
After running the process, the following information is collected on the server: the outgoing context of the process and a log of technical information about the operation.
Found a typo? Highlight the text, press ctrl + enter and notify us