I have a quesiton related to what is acceptable or best-practice for selectors towards this:
Specifically the “None” radio button above. Within Chrome and using Inspect, that “None” button looks like this:
See that highlighted ang-options, why doesn’t UI Explorer show that as selectable attribute to work with ?
Manually inputting this into UI Explorer, UI Explorer correctly validates this element. Interestingly, the Highlight button in UI Explore is disabled after doing this:
My question is is using Angular elements (I’m guessing it is an Angular attribute) within UiPath and Selectors a bad practice ??
TIA
Hey @riverrat437
Yep may be and it’s based on scenarios as well.
May be the angular attributes keep on changing dynamically.
Also, the selector UiExplorer identified is not the one you are checking in the inspect panel. It can be the child of it or parent may be. That’s why the angular attribute may not be appearing. You can play a bit with visual tree.
Also please have a look at the property panel below visual tree which has additional props for the selector to be utilized.
Hope this helps.
Thanks
#nK
Hello and thank you for the reply.
The properies panel under the visual tree does not include these either. This is where my question is coming from.
Manually including the highlighted attribute in my image, UI Explorer did validate the update selector target correctly. Just wondering why UI Explorer does not include that specific attribute and the other “ang” attributes as well.
Hey @riverrat437
By default it includes all the necessary attributes supported by the UiFramework you choose.
Thanks
#nK
Hello @riverrat437
If you are not able to use that angular attribute you can find the reliable attribute from the uiexplorer and use it. There should be some attribute that matches to the label.
Thanks
Just a context. My screen image is a little misleading. The angular elements are NOT in the left panel for selection. That one ang element showing up in the selector editor is there simply because I added it manually as I wanted to see if it worked in UI Explorer.
My question on if using using angular elements is bad idea still stands.