San Diego Next Experience UI does not allow UI Path software to recognise any elements on the screen. What do i need to do to get this working.

[Andy S]

We are enabling Next Experience in a phased Pilot after upgrading to San Diego back in May.

We have noticed that UI path software was successfully able to recognise all elements of San Diego platform screens before we switched on Next Experience. This is worrying for us as we do have users in the business who rely on screen readers to help them with their role. We are going to be asking them to regression test Next Experience with some screen reader tools. The initial question is around UI path because we rely on that to identfiy elements and click on elements for execution of scripts.

Is there a plugin required to allow UI Path to work with San Diego Next Experience.

[MohanSadaiyan]

Hi Brad,

Our Uipath Software is not able to identify the uielements of Next Expreience UI of Servicenow.
Even we tried to use Active Accessablity mode it worked sometimes but sometimes Not.
can we get any permant solution from Servicenow.

[Andy S · Accepted solution]

I can now share how we resolved this issue.

We upgraded the UiAutomation package version (from 19.11.4 to 20.21.10) and changed selector type to 'Active accessibility. The UI Path software could then identify all elements within the platform as it had previously been able to do in UI16.

[MohanSadaiyan]

Hi Andy,

For us it's not working by using Active Accessblity mode too.
Do you have anyother solution.