Quick Object Repository Demo

Hi There!

We’re preparing to launch Object Repository in 20.10. I made a quick demo around this here. In the demo I used a naive example to explain the basics and get the message through but we’ll promise to come with a more robust demo example soon.

Please share your thoughts with us around Object Repository. What works, what doesn’t, what’s missing and how can we make this better. :rocket:

If you want to get the latest 20.10 beta build, download from cloud.uipath.com or flip the Studio channel to Preview updates and we’ll automatically upgrade you.

Note: 20.10 Object Repository is not backward compatible with 20.4 and 20.8 Object Repository.

Cheers,
Studio Team

20 Likes

Link to documentation

4 Likes

This is amazing to say the least !

Thanks,
Nithin

Thanks @Nithin_P - have you had the chance to use it? What are your thoughts?

@Mircea.Grigore

Will the upgrade work for chrome to Edge ?

1 Like

While the intention of Object Repository is not to treat “Browser Change” scenarios, we have seen it work in practice internally. I recommend you try this current version and let us know your thoughts. Thank you! PS: For future releases, we are working on a more elegant solution for “Browser Change” scenarios.

2 Likes

@Mircea.Grigore

I think object repository for elements and publishing as library is great . I tried my hands on the same .I also tried the upgrade from chrome to edge for "https://www.rpachallange.com " . while saving the Edge elements as library ,the descriptors did not get recognized .

But overall drag and drop feature for descriptors and adding activities is awesome .
publishing the descriptor as library is awesome too :slight_smile:

1 Like

Hi Navneetj3, would love to see what you built and understand what is not working.

1 Like

ObjectRepository123.zip (12.8 KB)

@Mircea.Grigore

PFA the project file . I have added descriptors for both chrome and Edge. For Edge the workflow is not recognizing the Descriptors while adding as dependency .

Thanks
navneet

Great, giving more and more value to Orchestrator!

Does this work for browser, the era we are in most apps are browser based on cloud, we need this solution to work in robust manner for browser, please confirm as i heard in the video saying “it was not built necessarily for browser based”

Hi @Mircea.Grigore,

Firstly, thanks for the great demo. It will benefit the RPA developers who are building bots using the same application. It will be even better if the object repository can be exported together with the element name for offline discussions with the application SME (subject matter expert). Before upgrading the bot, the SME may be consulted about the UI changes. The Lead RPA developer would then update the UI library for the application and then advise the various CoP RPA developers to test and re-publish their respective bots.

The time saving will be realized on the second and subsequent upgrades after the bots are first upgraded to use Object Repository. That is for existing production bots, it will still required re-training the bot… will there be an easier way to identify, match or migrate to the Object Repository…

1 Like

Of course it works for browser based apps. Desktop, Web and Mobile apps are all supported. In the video, i mentioned that switching processes descriptors to work from browser type A to browser type B, for example from IE to Chrome, was not the main scenario we intended the feature for. Object Repository aims at solving a reusability issue and then an upgrade issue. While the reusability issue is more obvious, the upgrade issue is about updating processes when the underlying application (lets say Sharepoint) was upgraded and some selectors now fail. In this case, the only change needed is to build a new version of your selectors, publish them as a library, update your process dependencies.

1 Like

Thanks @GreenTea, we are looking at options to migrate processes that use classic UIA to modern. I assume this is what you meant?

1 Like

Hi @Mircea.Grigore,

Yes. The feature to migrate from classic UIA to modern will shorten the bot upgrading time. So that production bots can quickly be usable again. Thank you.

Thank you for the demo! This is an exciting feature that helps us reduce a lot of redundancy.

What will make a transition to the changes even smoother is if a library version within a process automatically chooses the latest version available on the package stream. That way, if my library is used in 5 projects, I would not need to go and upgrade each one of them.

Is such a feature in the pipeline?

PS: This is a long requested feature on the forum already :slight_smile: How to always use latest library version?

Hi @anupamck - this is indeed something we are looking at for upcoming releases. Thanks for bringing this up!