Automation 360 extension setting

If the bot execution takes longer when you use the Recorder to automate a static page running on the Google Chrome or Microsoft Edge browser, then follow these steps to enable the setting in the Automation 360 extension:

Click the extensions icon at the top right corner of the browser window.
Click the vertical ellipses next to the Automation 360 plugin and select Manage extension.
Enable the Allow access to file URLs option.
Restart the browser and run the bot.

Benefits of using Recorder package instead of SAP package

We recommend that you use the Recorder to automate SAP applications. When you use the Recorder to automate SAP applications, you have the following benefits:

You can automate objects without creating a session. When you use the SAP package you must create a session.
You can automate the object directly without generating the field paths or having any prior knowledge of the field paths. When you use the SAP package, the package will execute actions directly on control field paths when properties in the search criteria match the object that the bot searches during execution.
If the Recorder runtime window overlaps the object that you want to automate, then the Recorder hides the runtime window before you automate the object.
Recorder supports actions in the If, Loop, and Wait packages that enables you to check if an object exists in the specific browser or window.

Note: When compared to the Recorder package, the SAP package enables you to automate an application without activating the application window.

Capture action

Use the Capture action to capture an interaction with a user interface (UI) object. This action enables you to add a single interaction when you are building a bot.

Note:

The Capture action replaces the Object Cloning command from Version 11.3.
If you open a window in any of the supported browsers with a user account that is different from the one used to log in to the computer, the Recorder might not capture and play the control actions accurately.

Using the Capture action

You can capture and automate objects inside a cross-domain IFrame that has multiple IFrames with same frame source and IFrames that are loaded dynamically during runtime in Google Chrome and Microsoft Edge Chromium browsers. After you have captured an object inside a cross-domain IFrame, the frame path is stored in the FrameDOMXPath property, by default.

You can automate the following applications running on Microsoft Edge Chromium with IE mode:

Java web applications
Applications that are accessed through the Citrix Workspace app.
Citrix Virtual Apps

The new FrameDOMXPath property identifies the frame in which the object is located. You must select this property to run the bot successfully to automate objects on a cross-domain IFrame.

Note: If you clear the FrameDOMPath property from the search criteria, the Recorder fails to identify the frame.

Important: In the Google Chrome browser, you can capture and automate objects inside a cross-domain and use multiple frames with the same frame source.

When you are automating web pages running on Google Chrome and Microsoft Edge browsers, the Recorder > Capture action no longer scrolls down the web page if the target object is visible on the screen. This improves the user experience and the reliability of automation when there is a fixed top pane on the web page and if some physical actions such as mouse clicks do not work as expected.

When you are automating a web page on a Google Chrome, Microsoft Edge Chromium, or Mozilla Firefox browser, you can capture the pop-up windows, alert dialog boxes, confirmation dialog boxes, and prompt dialog boxes that appear.

Recommendations:

When you want to automate an alert dialog box on a web page, we recommend that you add a delay before the Recorder > Capture action because sometimes, the alert dialog box appears after a delay on the application window.
To accurately capture or automate objects on SAP applications, we recommend that you enable scripting. If scripting is not enabled, the following prompt message is displayed below the bot runtime window:
SAP scripting disabled: Enable scripting for more reliable captures

If you do not enable scripting, instead of using SAP technology, the Recorder uses MSAA technology for capturing objects.

Automate applications running as an admin user

You can capture objects on applications that are running as an administrator by selecting the Capture and run with admin privileges option from the Bot editor.

<span>Capture objects using Capture and run with admin privileges option</span>

Before you automate applications running as an admin user, ensure the following:

Bot Agent is installed in system profile.
Bot Creators and Bot Runners have admin rights on the device to automate the applications.

When you select the Start recording option in the Bot editor to record multiple applications, and switch applications running in elevated and non-elevated mode, the bot might not be able to identify the change between modes. In such cases, for all captures on applications in elevated mode, select the Capture and run with admin privileges option and then re-capture the object.

Note: Elevated mode gives you permission to run applications as an administrator.

Important: When you try to automate any Java or SAP application that is non-elevated by using the Recorder in elevated mode, the bot encounters an error.

To avoid this error, de-select the Capture and run with admin privileges option from the Bot editor and run the Recorder in non-elevated mode to capture Java or SAP applications.

Object properties

When you select an object to capture, the Universal Recorder collects data on the object's properties in order to identity the object during run time. You can do the following with the object properties:

Verify that the captured object properties match your intended object.
For example, when capturing a table from a website, ensure the Control Type and HTML Tag values are TABLE.
Retrieve a property value. Use the Get property action and enter the name of the property in the Property name field or select an object property from the list of available properties. The list includes suggested property values from the search criteria in the Object Properties table. To select an object property from the list of properties, move the mouse pointer to the right of the Property name field and click the arrow.
For example, to retrieve the text of a link, use the Get property action and enter HTML InnerText in the Property name field or select HTML InnerText from the list of properties.
You can select a combination of properties for the bot to search the object in your business application window uniquely.

The search algorithm for the Recorder package ensures that when you run a bot an object is captured only if its properties match the exact search criterion that you selected in the Object properties table. If the properties of the object do not match the search criterion exactly, then the bot fails with an error message. However, if the search criterion includes a wildcard character, then the bot captures the first object that matches the criterion.

For example, to capture a text box from an application that has three text boxes named firstname1, firstname2, and firstname3, if you select HTML name as the search criterion, enter the value firstname in the HTML name field, and run the bot, then the bot fails with an error message because a text box with the HTML name firstname does not exist. However, in the HTML name field, if you enter firstname*, and run the bot, then the bot captures the first text box that matches the criterion.

Note: This functionality is available for the bots you create using the 2.4.0-20211016-070100 version of the Recorder package starting from Automation 360 v.23. If you have created bots using a previous version of the Recorder package, you must recapture the objects to use this functionality.

Actions performed on captured objects

After capturing the object, specify the action for the bot to perform on the object at run time. For example, when you capture a hyperlink, you can select to click the link or to retrieve the link text. To see table of all objects and possible actions, see Actions performed on objects captured with Universal Recorder.

Note: If you encounter an error when running a bot that captures an object from Internet Explorer and the error message is about Google Chrome, see Your Chrome Plug-in is either not installed or disabled (A-People login required.

Background processing

Background processing enables an automation that involves interacting with an application in the foreground (such as mouse clicks) to run in the background. We recommend that you use the option to run in background to increase the visibility of the target object and improve bot accuracy. The following actions support background processing:

Click
Set Text
Get Text

Secure recording

When secure recording mode is enabled, bots do not display the target object images after capture. This ensures that sensitive data is not shown.

Note: Although the bots do not display the target images after capture, the images are still stored in the Control Room because they are required to run the bots.

When you record a task in secure recording mode, the Preview window temporarily shows an image of the captured area. This image is hidden after you navigate away from the Bot editor window or refresh it.

A user with admin privileges must enable this setting. See Settings.

Proxy support

If your device is configured with a proxy, all outbound requests from this package are routed through the proxy server. See Connect Bot Agent to a device with a proxy.

Use cases on how to use recorder

Use these example tasks to become familiar with the use of the recorder in building bots.