In a legacy application, UI elements are very difficult to be identified. in this application, using get visible text able to get the visible rows in the data table. But if a row is selected in that table, few other extra rows are getting selected. Now have to deselect the unnecessary highlighted rows and keep only those that are required.
what are the approaches for doing it
Can we deselct the rows with out cv
what advantage can we have with CV in this scenaro
Hi @deepaksvg99
If the selectors are not relevant then it is better to filter the unwanted rows post extraction, Can you share an example of your scenario…, CV will be Able to extract the visible rows of the table only
Can you share an example of your usecase please!
Without CV, you can use keyboard shortcuts, image-based clicks, or coordinate-based automation to deselect unwanted rows, though it’s less reliable. With CV, you gain more accuracy as it detects highlighted rows visually and can selectively click or deselect specific areas. CV also improves stability in legacy systems where selectors are inconsistent or unavailable.