A360 Element Validator logo

A360 Element Validator

by Kartikay DharDeveloper Tools

Real-time Analytics

Metrics and performance data for A360 Element Validator

Timeframe:

Advanced Analytics

Monthly Growth

Percentage change in user base over the last 30 days compared to previous period

Category Ranking

Current position ranking within the extension category compared to competitors

Install Velocity

Average number of new installations per week based on recent growth trends

Performance Score

Composite score based on rating, review engagement, and user adoption metrics

Version Analytics

Update frequency pattern and time since last version release

Performance Trends

Analytics data over time for A360 Element Validator

Loading analytics data...

About This Extension

Used to identify if an element captured by the A360 recorder is valid or not. #### V 0.5 UPDATES!!#### Use the power of GenAI to create custom Xpath for your recorder elements! Just select OuterHTML as a property and provide an OpenAI API to start creating custom Xpath to use rather than the absolute XPATH provided in DOMXPath. ################################################### PROBLEM STATEMENT The most common point of failure for any RPA process is the brittleness of the UiElements captured while using recorder. Every time a Bot fails to click, set text etc. the developer needs to check out the code, run the recorder capture again to know if the element properties have changed or not. This is a time-consuming activity and forms a major part of the maintenance activity conducted for every Bot. Another common issue is that the web elements do not match in Developer and Production environment, causing Bot failure at the time of deployment. STEPS TO USE 1.1 Select the recorder element you want to validate. Ensure that the Object Properties are not expanded. 1.2 Once the element is selected click on Read. It will pop up the enabled properties for the element. If the Read button is clicked without selecting the element or on a not Bot page, it will throw an error. 1.3 Go to the Target page and click on Validate. 1.3.1 It will notify if the Page Title is incorrect. 1.3.2 If Element is found. Element Found popup will come and the element will be highlighted. In a few cases if the element is hidden behind another element, it will mention that the element is found but will not highlight. For such elements, left click may not work and best practice is to use click. 1.3.3 If element is not found, it will throw the error and mention which primary locator failed. ADVANTAGES • Developer does not need to rerun the bot to know if the element that was captured is still identifiable or not. This will save them a lot of time. • Developer can capture the element and try different properties to know which one would be the right one to use. • No need to check out the code. Can be used directly in public repository. • Extension can also validate the Page title and notify if the Page title has changed. • Currently handles only the most used recorder properties: o HTML ID o HTML Tag o InnerText o DomxPath o Path o Class o Frames o Combobox LIMITATIONS • Currently only works for Chrome elements. • Only works with Recapture Object (Auto Detect).

Screenshots

1 of 5
A360 Element Validator screenshot 1

Technical Information

Size
25.36KiB
Languages
1 supported
Extension ID
nblgkinmfcib...

Version History

0.5
Current Version
Latest
03/21/2025
0.4
Previous Version
02/19/2025
0.3
Older Version
01/20/2025