A Get Web Number building block is used to find a number on a web page or nested inside a web element in an already open browser window when working with web automation.
Please note that this block only works with browser windows that were previously opened using the Start Web Browser block or their “child” windows.
Fully expanded, the Get Web Number block shows the following properties:
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 Web Number”) can be changed by double-clicking on it and typing in a new title.
This property contains the locator for the web element from which the number has to be extracted.
A web element locator can either be dragged and dropped onto this property from the “Web” tab on the left side of the screen or be captured by right-clicking on the property and selecting “Capture new web element”.
Once set, the web element locator can be edited by right-clicking and selecting “Edit web element”. See the many different Learning Center video examples of how this works.
The property can be cleared by right-clicking and selecting “Clear web element”.
This property contains the number that was found.
This green output connector triggers if a number is not found before the timeout (see below). This is typically used to branch execution flow or to explicitly fail a case by linking it to a Fail block.
The browser canvas position where the number was found in X, Y coordinates. The top-left corner of the browser canvas is position 0, 0.
Click the expander button to work with the X and Y coordinates separately.
Please note that any web element that is set to not visible (eg. using a CSS class) will have position 0, 0.
The browser canvas position and size of the number found in X, Y, Width, Height coordinates, starting with the upper-leftmost pixel. The top-left corner of the screen is position 0, 0.
Click the expander button to work with the area’s position and size and their nested sub-properties separately.
By setting this property, the web element locator will be limited to only work inside the source element.
For instance, if in a previous building block, a table web element found, by setting that as the source element, it’s possible to search for numbers inside only that table.
By setting this property, the building block will use a specific browser window.
Define a format that the number must meet to be retrieved. For instance, by defining “Price: [NUMBER] USD” only numbers inside text such as “Price: 123.00 USD” will be retrieved.
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.
The value used by the filter.
Select which occurrence of the number 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).
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 occurrences of a number that match the locator set above.
The maximum time spent searching for a number before giving up and triggering “Not found” (see above).
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 a value other than “None” is selected, the building block will use scrolling when searching for numbers. This can be useful when searching in scrollable content such as web pages where elements are loaded asynchronously, eg. using infinity scroll.
The maximum number of times to perform a scroll before giving up searching for numbers.
The amount of scrolling that will be performed on each scroll repeat.
The delay in seconds between each of the scroll amounts.
When checked, any found number’s containing web element is automatically scrolled into view.
Delay the search for the web element until there has been no changes to the page’s DOM for a specific period of time — for instance 3 seconds.
Delay the search for the web element until there has been no active XHR requests for a specific period of time — for instance 3 seconds.
This is useful when waiting for behind-the-scenes updates with XHR to occur. Some enterprise web applications use XHR and DOM changes extensively behind the scenes, even switching out existing button tags with new ones. This includes Microsoft Dynamics 365 and Salesforce.
Updated March 13th 2018.