I really like working with the Object repository as well, there are just a few annoying things I found : 1. Screens: A lot of applications have multiple sub-screens (Main / You click something -> Screen1 / You click something again -> Screen2 ... ) It's only possible to have 1 "layer" of screens under the application, which makes it difficult to structure your object repository. (I ended up with numbering my screens, 1. Main -> 1.2 Screen1 -> 1.2.1 Screen2 etc.) 2. Screens: lol I set the top-level selector for a screen, but the elements created below it, still create their own top-level selector eg. Sub-window1 (title: customer 123), even though you wildcard the customer-nr, all the elements below also need to be updated (wildcard the customer-nr and don't take the top-level selector from the screen.
I agree, it's not perfect (yet), but at the pace UiPath is moving at, I'm sure they'll correct these little glitches. Don't forget to post feedback at their forums - they actually do listen to their users :-)
Dear Jeppe, thank you for these beauty full videos! :D they are gold. I have good experience in RPA and took a break for 1 year, now coming back I'm very grateful to have found these videos made in a professional manner.
Great Video. I realize the UiPath Associate Developer class could have shown me this first to save time and rework, but then I wouldn't have known all the features and failed the test. Now I have captured the DoubleUI path screens in in Orchestrator after publishing and want to go back and improve the old apps we practiced on earlier. Thank you and look forward to learning more from you.
Great Work!!
Thanks a lot!
I really like working with the Object repository as well, there are just a few annoying things I found :
1. Screens:
A lot of applications have multiple sub-screens (Main / You click something -> Screen1 / You click something again -> Screen2 ... )
It's only possible to have 1 "layer" of screens under the application, which makes it difficult to structure your object repository. (I ended up with numbering my screens, 1. Main -> 1.2 Screen1 -> 1.2.1 Screen2 etc.)
2. Screens: lol
I set the top-level selector for a screen, but the elements created below it, still create their own top-level selector
eg. Sub-window1 (title: customer 123), even though you wildcard the customer-nr, all the elements below also need to be updated (wildcard the customer-nr and don't take the top-level selector from the screen.
I agree, it's not perfect (yet), but at the pace UiPath is moving at, I'm sure they'll correct these little glitches. Don't forget to post feedback at their forums - they actually do listen to their users :-)
Dear Jeppe, thank you for these beauty full videos! :D they are gold. I have good experience in RPA and took a break for 1 year, now coming back I'm very grateful to have found these videos made in a professional manner.
Thank you so much for the positive feedback. Much appreciated :-)
Thanks for this!
My pleasure :-)
Great Video. I realize the UiPath Associate Developer class could have shown me this first to save time and rework, but then I wouldn't have known all the features and failed the test. Now I have captured the DoubleUI path screens in in Orchestrator after publishing and want to go back and improve the old apps we practiced on earlier. Thank you and look forward to learning more from you.