Click UI Element
Close UI Window
Collapse UI Element
Drag UI Element
Expand UI Element
Find UI Element
Get UI Number
Get UI Selection
Get UI Text
Get Window Details
Invoke UI Element
Select UI Element
Set UI Element Value
Toggle UI Element
Update UI Window
Use UI Window
The green input connector in the header is used to trigger the block to start executing.The green output connector in the header triggers when a number has been successfully found.The title of the block (“Get UI Number”) can be changed by double-clicking on it and typing in a new title.
This property contains the locator for the UI element from which the number is to be found.A UI element locator can either be dragged and dropped onto this property from the ‘Desktop’ tab on the left side of the screen or be captured by clicking on the property and selecting “Capture new element”.Once set, the UI element locator can be edited by clicking and selecting “Edit element”.The property can be cleared by right-clicking and selecting “Clear element”.
This property contains the number that was found.
This green output connector triggers if suitable number is not found within the time specified in the timeout field (see below). If no building blocks are attached to this connector and the element is not found, then the case will end in status Fail.This connector can be used to branch the execution of the flow depending on whether the element is found or not.
This property instructs the building block how to get the text from the captured element:
“Title”: Only the text from the direct captured element.
“All children”: The combined text from all child elements to the captured element.
“Title and all children”: The combined text from the direct captured element and all children to the element.
If the captured element contains more than one child element, like a panel with more 2 or more label, the text form the individual elements will by default be separated by a space. If Split Lines is checked, the text from the individual elements will be separated by a new line instead.
The application canvas position where the UI element was found in X, Y coordinates. It is relatively to top-left corner of the screen which is generally 0, 0.In case of multi-screen environments X, Y coordinates may vary depending upon below scenarios:a) Element’s position can be negative (if main screen is on the right side and window is opened on the left screen)b) Bigger than screen resolution (if main screen is on the left side and window is opened on the right screen)Click the expander button to work with the X and Y coordinates separately.Please note that any UI element that is set to not visible will have position 0, 0.
The application canvas position and size of the found UI element in X, Y, Width, Height coordinates, starting with the upper-leftmost pixel. It is relatively to top-left corner of the screen which is generally 0, 0.In case of multi-screen environments X, Y coordinates may vary depending upon below scenarios:a) Element’s position can be negative (if main screen is on the right side and window is opened on the left screen)b) Bigger than screen resolution (if main screen is on the left side and window is opened on the right screen)Click the expander button to work with the area’s position and size and their nested sub-properties separately.
By setting this property, the UI element locator will work inside the provided source element, instead of working on a captured element.This means it’s possible to capture a row in a table in one building block, and by using the source property making it easy to find and click a particular cell or field in that exact row.
Define a format that the number must meet to be captured. For instance, by defining “Price: [NUMBER] USD” as the format, the block will return “123.00” from this text: “Price: 123.00 USD”.
Select whether the format should be case sensitive. By default, it is case insensitive.
Define the character used to separate 1000s in the number. The default value will be that set on Studio’s regional settings in Windows — typically “,” or “.”.
Define the character used to separate decimals in the number. The default value will be that set on Studio’s regional settings in Windows — typically “,” or “.”.
Define a filter that the number must meet to be retrieved. For instance, only retrieve numbers that are “Greater than” 100. If the number found doesn’t match the filter, the Not Found connector will be triggered.
The value used by the filter.
Select which occurrence of the numbers to use, if more than one is found.Select “All” to iterate through all of the occurrences. By selecting “All”, the sub-properties Current index and Completed are shown (see below), and the top connector is triggered for each occurrence.
The current index when iterating through all occurrences of a number.
This green output connector triggers when the iteration of all occurrences are completed.
This property contains the total number of found UI elements that match the locator set above.
The maximum time spent searching for a number before giving up and triggering “Not found”.The default value is 10 seconds. However, in many situations it can make sense to lower the default value to something far smaller, for instance 0,1 seconds because typically the page content doesn’t change much after loading.Note: All cases have a “global timeout” that can be configured in the “Settings” panel. This is unrelated to the timeout of a single building block. However, a running case will automatically be cancelled if it runs for longer than the global timeout.
When checked, the building block will wait for any changes happening on screen within the specified timeout before finding the number from the element specified.
Updated March 14th 2018.