Object Repository - Window Selector Change to sync to Elements

Feedback Studio
, , ,
1

Hi Team,

So we have been using object repository for almost all of our automations and with new activity migration that has increased a lot. But I see few pain points or some enhancements that might speed up the work and also at the same time help the developers to get the details quick and without errors

  1. Whenever we edit a descriptor and save …the ui tree or the object repository tree gets reset to the initial position automatically. When we have multiple elements to edit it is very difficult or unnecessary time consumption to scroll and select again to edit the next element.
  2. When we capture any of the elements, for each element, a window selector is automatically captured. It would be great to have a feature to sync the window selector from the parent page in the object repository tree. That way edit of window selector on the page element will automatically reflect in the subsequent elements that are used under the page element. Else we have to edit the window selector for each element separately. As most of the times we would have wildcards used in the titles to help with multiple variations, this change will help in reducing the rework on each element for window selector change and also maintenance would be easy and error free

Studio Version: 22.10.3

cheers

2 Likes
4

@Anil_G great feedback, thank you. Let me take it in the backlog and consider it for future releases.

Thank u.
G

1 Like
6

Has this been implemented yet even 23.4 seems having this issue

7

Hi ,
for use application/browser can we use object repository ?

8

@Raj_esh

Yes we can

Cheers

9

I have developed the code with dev selectors , made it dynamic in the property panel windows selector, now when I try in live environment, the attached window selector is setting back to dev environment.

When this happened I changed the windows selector from the object repository for the application window and it started working .

Could you pls explain this scenario ?

10

@Raj_esh

Because you need to update repo if you update idividual activity it wpuld not reflect everywhere

Cheers

1 Like
11

When we capture any of the elements, for each element, a window selector is automatically captured. It would be great to have a feature to sync the window selector from the parent page in the object repository tree. That way edit of window selector on the page element will automatically reflect in the subsequent elements that are used under the page element. Else we have to edit the window selector for each element separately. As most of the times we would have wildcards used in the titles to help with multiple variations, this change will help in reducing the rework on each element for window selector change and also maintenance would be easy and error free

Is this feature in UiPath yet? It is annoying that activities in Object Repo do not automatically get the window selector from the parent screen window selector…

12

I wholeheartedly agree with this suggestion. Now when I update my window selector, I have to do it for every object in the repository. To me the whole benefit of using the repository, is that it is faster.
This change would make my workflow a lot faster and seems like a logical one from a UX perspective, as the elements have to be categorised under a certain application/window.

13

Or perhaps if this automated process is thought to be unclear or unwanted. Allow us to use the Unique ID of the window to reference it, in the other elements

1 Like