UI Automation Activities

Designer panel

• Indicate on screen - Indicate the UI element to use as target.

  After you indicate the target, select the Menu button to access the following options:

  • Indicate on screen - Indicate the target again.
  • Edit Selector - Opens the Selector Editor wizard where you can configure the selector.
  • Open in UiExplorer - Opens UI Explorer with the UI element selected in the visual tree.
  • Change Informative Screenshot - Change the screenshot of the target application or web page.
  • Remove Informative Screenshot - Remove the screenshot of the target application or web page.
  • Show Informative Screenshot (double click) - Display the full the screenshot of the target application or web page.
  • Add to Object Repository - Add the current UI element to a library project, from where it can be reused throughout your automation process.
• Toolbar Button - Specifies the button from the system or application SAP toolbars. After indicating the SAP Toolbar on the screen, the list with all available buttons is displayed in the activity.

Properties panel

• ContinueOnError - Specifies if the automation should continue even when the activity throws an error. This field only supports Boolean values (True, False). The default value is False. As a result, if the field is blank and an error is thrown, the execution of the project stops. If the value is set to True, the execution of the project continues regardless of any error.

  Note: If this activity is included in Try Catch and the value of the ContinueOnError property is set to True, no error is caught when the project is executed.
• DelayAfter - Delay time (in milliseconds) after executing the activity. The default amount of time is 300 milliseconds.
• DelayBefore - Delay time (in milliseconds) before the activity begins performing any operations. The default amount of time is 200 milliseconds.
• DisplayName - The display name of the activity.

• Button - Specifies the button from the system or application SAP toolbars. After indicating the SAP Toolbar on the screen, the list with all available buttons is displayed in the activity.
• Target - The target element. Target element must be set. Before indicating on screen, this field is set to (null). Once the target is indicated, all properties regarding the element that was indicated are displayed.
  • ClippingRegion - Defines the clipping rectangle, in pixels, relative to the UiElement, in the following directions: left, top, right, bottom. It supports both positive and negative numbers.
  • Element - Use the UiElement variable returned by another activity. This property cannot be used alongside the Selector property. This field supports only UiElement variables.
  • Selector - Text property used to find a particular UI element when the activity is executed. It is actually a XML fragment specifying attributes of the GUI element you are looking for and of some of its parents.
  • Timeout (milliseconds) - Specifies the amount of time (in milliseconds) to wait for the activity to run before the SelectorNotFoundException error is thrown. The default value is 30000 milliseconds (30 seconds).
  • WaitForReady - Before performing the actions, wait for the target to become ready. The following options are available:
    • None - Does not wait for anything except the target UI element to exist before executing the action. For example, you can use this option if you want to retrieve just text from a web page or click a particular button, without having to wait for all UI elements to load. Note that this may have unwanted consequences if the button relies on elements which are not yet loaded, such as scripts.

    • Interactive/Complete - Waits all of the UI elements in the target app to exist before actually executing the action.

      To assess if an application is in the Interactive or Complete state, the following tags are verified:

      • Desktop applications - A wm_null message is sent to check the existence of the <wnd>, <ctrl>, <java>, or <uia> tags. If they exist, the activity is executed.
      • Web applications:
        • Internet Explorer - The <webctrl> tag is used to check if the Ready state of the HTML document is set to Complete. Additionally, the Busy state has to be set to False.
        • Others - The <webctrl> tag is used to check if the Ready state of the HTML document is Complete.
      • SAP applications - First the presence of the <wnd> tag verified, after which a SAP specific API is used to detect if the session is busy or not.

• Private - If selected, the values of variables and arguments are no longer logged at Verbose level. This field supports only Boolean (True, False) values. The default value is False.

• AlterIfDisabled - If selected, the activity executes the action even if the specified UI element is disabled. This field only supports Boolean values (True, False). The default value is True.