A360 Element Validator

Used to identify if an element captured by the A360 recorder is valid or not.

As of May 2026, A360 Element Validator has 15 users in the Developer Tools category.

Usersup 25.0 percent+25.0%
15
15
Ratingno change0%
— reviews
Reviewsno change0%
Version
0.5
Manifest V3

History

1 snapshots

Tracking since Apr 29, 2026.

15.2413.511.76Apr 29, 2026May 26, 2026
View as table
DateUsersRatingReviewsVersion
Apr 29, 2026120.5
Now150.5

Permissions & access

Permissions
activeTabstorage
Host access
None declared

Screenshots

A360 Element Validator screenshot 1A360 Element Validator screenshot 2A360 Element Validator screenshot 3A360 Element Validator screenshot 4A360 Element Validator screenshot 5

About

#### 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).

Technical

Version
0.5
Manifest
V3
Size
25.36KiB
Min Chrome
88
Languages
1
Featured
No

Metadata

ID
nblgkinmfcibcjmjidmkhogbmhhfhaan
Developer ID
u12cc1650699d053f36d2d1e775edf762
Developer Email
[email protected]
Created
Dec 17, 2022
Last Updated (Store)
Mar 21, 2025
Last Scraped
May 26, 2026
Website
Support URL
Privacy Policy

Similar extensions

Alternatives to A360 Element Validator, ranked by description similarity.

Data sourced from the Chrome Web Store · last verified May 26, 2026.