For Studio v2020.10 and higher, this activity is only available in the Classic Design Experience.
A container that enables you to attach to an existing Table UI element and perform multiple actions within it.
- 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.
If this activity is included in Try Catch and the value of the ContinueOnError property is True, no error is caught when the project is executed.
- DisplayName - The display name of the activity.
- Column Name - Specifies Column name from the table. After indicating the table cell, the list with all available Column names is displayed in the activity. Variable created in this field is of
- Row Number - Specifies Row number or use First empty row possibility. Variable created in this field is of
- Target.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.
- Target.Element - Use the UiElement variable returned by another activity. This property cannot be used alongside the Selector property. This field supports only UiElement variables.
- Target.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.
- Target.TimeoutMS - Specifies the amount of time (in milliseconds) to wait for the activity to run before the
SelectorNotFoundExceptionerror is thrown. The default value is 30000 milliseconds (30 seconds).
- Target.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_nullmessage is sent to check the existence of the
<uia>tags. If they exist, the activity is executed.
- Web applications:
a. 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".
b. 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.
- Table Row Index - The row index that is found in case the first row is empty. Otherwise, the value in this field is equal to the input in the Row Number property. This field supports only
- UiElement - The UiElement to be used in subsequent children activities.
Updated 6 months ago