Recording tasks guidelines

Follow these guidelines when you record and run tasks.

Adjust the recorded actions
Actions such as Object Cloning or web commands are generated quickly by the recorder. For a more flexible and robust automation, adjust the recorded actions based on your target application's behavior and what you want to achieve. For example:
  • Create variables for input and output parameters.
  • Add wildcard characters to dynamic search properties or window title.
  • Set correct interactions such as Set Text and Get Property.
Learn all available actions
Underlying actions are important, so learn and familiarize using these actions. Otherwise, you might have to use easier but less reliable methods of interaction such as Keystrokes or Image Recognition.
Maximize the windows
Maximize the windows if you are going to use any application interaction methods (such as Left, Right, Double Click, Keystrokes, or Image Recognition). For example, maximize the windows if the object properties are dynamic so that you can easily locate the objects. You can also change object paths based on the screen size.
Use click action rather than left-click, right-click, or double-click action
When interacting with elements on the target application, use the Click action instead of the Left Click, Right Click, or Double Click action. The Click action is more reliable as it interacts with the identified object of the application, while the other actions rely on coordinates and interact with the surface layer of the application.

Another advantage of using the Click action is that the bot can run even if the target element is not visible on the desktop or the application screen is minimized.

The Click action is used to invoke the function behind the control. It is similar to using the space bar or the enter key on the control in focus.

The Click action also includes a Left Click action. In the Left Click action, you point the cursor to an object and perform a left button up and down action, which triggers the control. The Click action does not require a UI to perform the action while the Left Click action requires a UI to move the cursor to a specific object and click it.

Choose an appropriate interaction method
Use application interaction methods such as Left, Right, Double Click, Keystrokes, or Image Recognition, which work with the surface layer of the target application, only when the other methods do not work for your specific scenario.
Customize window titles
Change or customize the window title property in your recorded actions if you want your bot to work dynamically on multiple files or if the target application window title is not static. The bot will then work even if the file name or window title does not match the window title property of the recorded action.
To customize the window title, you can do one or both of the following:
  • Use the system variable filename for the window title
  • Replace the dynamic parts of the title with wildcards
Perform the process efficiently
Perform only the actions necessary for bots. Adding extra interactions will reduce the efficiency of the bot and increase the processing time as well as points of possible failure. Accidentally recording an interaction with an application that is not part of the process might result in errors such as Application not found during runtime.
Perform the task slowly
To ensure all the tasks are recorded correctly, perform the task at a reasonable speed. This gives all applications the necessary time to open and process operations completely before recording the action.
Note: Playback speed is not dependent on the recording speed.
Avoid dragging windows while recording
Automated processes typically do not include window actions such as minimizing, maximizing, or moving a window.
Do not double-click the application icons while recording
Use the following method while recording:
  1. Open the recorded task in the Workbench.
  2. Use Open Program and Open File commands.
  3. Replace any recorded mouse clicks.