Working on automating in Chrome and so far the bot has been able to click through all the steps of this process but for some reason, it’s getting hung up on clicking this specific selector.
The target “Edit” button is anchored to another element in the same row to filter out the potential duplicates that were identified. Both show as valid and visible
The method of configuring selectors found in the Modern design experience is a bit new to me, but I tried both the Fuzzy and Strict selectors (for both Target & Anchor elements) and have had no luck.
Target element Strict & Fuzzy selectors
Everything I know about RPA leads me to believe that if an element is both valid AND visible, the bot should have no problem interacting with it. If anyone has a fix for this I would greatly appreciate it.
Studio version 22.10.4
UiPath.System.Activites 22.10.4 (can’t update due to Studio version)
UiPath.UIAutomation.Activities 23.4.7
The Click activity. I have the “Verify execution” attribute set to the pop-up window that should appear after clicking the Edit button which explains the error message below
The error message on execution
To isolate cause, can you try to set HardwareEvent at input method in Click activity?
If it doesn’t work, please check whether mouse pointer moves into where you expect. We might be able to identify it’s selector matter or others.
Some elements work better with Strict Selector than Fuzzy for capture, my advice is to try to enable Strict and Fuzzy with anchor and disable computer vision and image if they are enabled.
Important: the Strict selector is bringing the “TableRow” tag, if the line changes position at each execution, it is necessary to edit this information using a variable, you can use a “Get Attribute” action to obtain the line of the “last tracking no:” object and use the line number information obtained from the variable in the strict selector of the “edit” object.
I don’t see anything related to “HardwareEvent” in the Click activity in question.
The mouse itself isn’t moving to the element but that’s the case for every other Click activity before it. I think being in the “Use Application” scope defaults everything to Simulate Click/Type
Went back and updated the selector. The target is the Edit button and the Anchor is the table cell in the same row w/the text “Last Tracking No:” Have both the strict and fuzzy selectors enabled and both are as robust/specific as I can make them, I also disabled Computer Vision and am getting the same result.
It’s weird because the bot can SEE the element but the Click action itself isn’t registering for some reason.
Normally I wouldn’t use an Anchor but I figured it wouldn’t hurt. At first the selector wouldn’t even validate without an anchor because there were a lot of potential duplicates on screen. That went away when I enabled both the Strict and Fuzzy selector.
Again, avoid css-selector. Open it in UI Explorer, remove the css-selector property (uncheck the box) and add other properties to create a better selector.
One think I can see is you are not trying to refine your selector at all…please use ui explorer and try refining it and yes css selector is not at all reliable in many cases
@postwick My apologies, I didn’t see the CSS selector was still active in UIExplorer. I thought it was just disabling the Strict selector. I unchecked that option for both the Target and Anchor elements but still am not seeing the desired result of the Click activity.
@Anil_G I have now checked just about every box (aside from CSS) in the UIExplorer for this Edit button which has now made it unique according to UiPath (it had been identifying duplicates everytime I re-indicate the element). The Click activity itself doesn’t fail, but the intended popup window doesn’t appear after the fact.
Whether the Target element is by itself or has an Anchor attached to it (that is also unique) the Click still won’t show the popup window that’s intended.
That’s not a correct way to do a selector. You don’t want to just check everything. Check only the things you need in order to uniquely identify the element. For examples, is it always in the same tableRow?
The selector itself is considered “unique” enough with just the tableRow (yes it’s always the same), tag, and aaname attributes specified in UIExplorer.
However, when I go to save the changes I’m brought back to the Selection Options menu where the warning of Duplicates Found is displayed. Upon hitting Validate, I get the below message.
Since the UIExplorer already said it’s valid with many or few attributes specified, I decided to ignore that message and try it anyway. Same result as before.
Please see below for the iterations of the Target selector I’ve tried (none are using CSS in any way)
Strict only. After unchecking the CV and Image boxes, the duplicate warning went away. UIExplorer also showed a successful Validation & highlighted the correct element.
Fuzzy only, added the ID attribute to distinguish from the above Edit button. No duplicate warning, Valid & correct highlight in UIExplorer
Strict only with ID & TableRow attributes specified (ID shows ctl06 & tableRow shows 3 as opposed to ID ctl04 & row 2 for the above Edit button)
I would try more iterations but I’m noticing that however I refine the selector to be as unique as it needs to be, the Click activity doesn’t register on the site because there is still no popup that appears after the fact. I’ve weeded out all the duplicates, zeroed in on specific types of selectors, triple-checked in the UIExplorer that the element is both Valid and visible, and have still had no luck.
Get rid of the anchor. Just use tag, aaname, and tablerow in your strict selector.
If the click still isn’t producing the expected result…what is the Click activity’s Input Mode set to? I often find Hardware Events works best in these cases where the defaults don’t work.
ashokkarale
Anil_G
Soudios
ppr
Yoichi
lrtetala
Anjani_Kapoor
sarikayaebru
rodrigo.simao
Jon_Smith