Important! Read this.
We have launched a new documentation website. If you're using Enterpise Edition 10 (or higher) or Express/Business Edition 2.4.1 (or higher), visit this page.
We have moved to a new documentation platform. This section is no longer supported. For the up-to-date information, see RPA Recorder | How to use RPA Recorder.
The section explains general operations performed by RPA Recorder, such as creating, editing, and publishing of recordings. Descriptions illustrate how to use a typical robotic automation workflow.
Level of experience required
To start RPA Recorder/WorkFusion Studio, launch Intelligent Automation Cloud Express. On opening WorkFusion Studio, the RPA Recorder main window appears.
Recording process recommendations
Do not be fast during recording process, take small pauses after each action.
After finishing the recording, test it and play the recorded flow.
You can record your workflow in chunks by appending each new recording to the existing file.
Click the Insert Recording button.
When creating complex automation flows, it may be useful to run bot execution not from the beginning but from the current step and thus save time and effort.
When testing various actions, it might be useful to temporary disable some steps, excluding them from the execution flow though not completely deleting.
To disable a step, uncheck the respective checkbox in the Active column – the step gets grayed out. To enable a step, check the respective checkbox again.
When the playback is finished, you can check the recorder variables values. See Recorder variables Log for more information.
There are cases when you have downloaded a sample recording from WorkFusion Forum or Knowledge Base. To play it, you should add it to your Media Files first. To do this, follow the steps below.
Recorder uses surface-based (image-based) and object automation approaches
The image-based approach refers to the bot capturing images of active elements while recording and trying to find the same images and click (hover, drag, scroll) on them during script execution.
In some cases, the screenshots taken by the bot can be too large or small, not unique, or can have some unnecessary elements, e.g., tooltips, pop-up windows from other applications, etc.
|Bad screenshot example|
The situation can be easily solved by capturing a new image manually, or by editing image offsets.
Click Capture new image under the action screenshot.
A countdown in the bottom-right corner allows you to get prepared for the screen capturing. Meanwhile, you can switch to another app, open menu items, etc.
Before capturing actually starts, an overlay with the help text appears.
The delay before screen capturing can be set in Window > Preferences > WorkFusion Studio > RPA Recorder > Image.
By default, robot clicks (hovers, scrolls, drags) directly into the center of the captured image. You can set the cross-hair to a custom place by clicking the image.
A pop-up dialog with 100% zoom on image is shown. Here, you have an option to set the offsets
You can choose any image located in the project folder for the active action.
The image can be copied from any folder on your machine using drag'n'drop or copy-paste.
In automation workflows, most actions are executed quite quickly, but some actions require a pause before their execution, e.g., page loading, document saving, opening new applications, etc.
To set action delays, proceed as follows.
Set a delay type.
Wait up to XX ms – Bot will retry executing the action during specified timeout if the action has been failed. As soon as the action is successfully executed, Bot proceeds to the next one.
Polling interval XX ms – interval between retries.
It is preferred to use retries rather than delays before action.
You can use variables to store initial or run-time values that need to be entered from keyboard or copied to clipboard.
See Recorder Variables for more information.
All variables need to be defined in the Recorder Variables table and can be used in actions' parameters.
As the workflow completes, the variables, which values have been changed during the execution, are reset to their defaults.
Loops can be used:
Loops can also contain other actions (clicks, drags, keystrokes) as their children.
To read more, go to Loops.
When the robotics automation is tested and appears to run smoothly, you can publish it to Control Tower.
Intelligent Automation Cloud Business enables you to import both bot tasks and recorder scripts from Control Tower.
Paste the link you copied earlier into the Bot Task link field and click Next.