27. Publish Object Repository to Orchestrator and reuse | UI Library

27. Publish Object Repository to Orchestrator and reuse | UI Library | UiPath Modern Design Project

Рет қаралды 1,009

Күн бұрын

Пікірлер: 24

@AvinashSingh-l9t 8 ай бұрын

Sir, the way you explain is top-class; even an 8th standard kid can understand easily. Thanks for this series. I hope I can meet you one day and express my gratitude by touching your feet ❤ and i am also eagerly waiting for DU series

@MukeshKala 8 ай бұрын

That’s a huge compliment, Thank you for that 😍

@divyanathk.r7157 4 ай бұрын

hi Mukesh, when i try to publish the library, i am not getting the option 'Orchestrator tenant library feed', i have only 2 option one is custom and the other is 'Orchestrator shared libraries feed, i did check the orchestrator connection and the roles and permissions also, everything is looks good to me. i have no idea what did i miss🥲, how can i publish the library process to tenant feed!

@MukeshKala 4 ай бұрын

go to orchestrator and check if you have all the permissions for libraries Role should be assigned at tenant level and folder level. → roles → edit and select all for libraries

@ashishjadhav6392 4 ай бұрын

Hello Sir, I am getting following alert while publishing Library to Orchestrator. Publish of Acme_LogIN failed. PackageFeed does not exist.

@MukeshKala 4 ай бұрын

Orchestrator Feed Setup: Verify that your Orchestrator feed is correctly configured. Check the Orchestrator settings in UiPath Studio to ensure the package feed exists and is accessible. Permissions: Confirm that your Orchestrator account has the necessary permissions to publish packages. Ensure you have the appropriate roles assigned. Package Version: Ensure the package version is unique. If the package with the same version already exists, consider incrementing the version number. UiPath Studio Version: Check the compatibility between your UiPath Studio version and Orchestrator instance. Logs: Examine UiPath Studio logs for more details on the error. This can provide insights into the specific issue. Network and Firewall: Confirm there are no network or firewall issues affecting communication between UiPath Studio and Orchestrator.

@KeerthanaParthiban-ls3xm 7 ай бұрын

I have a query mukesh.. When im using the Library in my local project suppose if i need to add one extra condition to the existing library object.. So i make changes to object and i don't want to get that changes to be in original library..so is it possible to make changes n publish the library locally.. Without affecting the original one

@MukeshKala 7 ай бұрын

The best is to use the version control like GIT or TFS , that way you can work in your local , alternatively you can edit and make sure not to publish or just create a copy of project and make changes there

@PALADUGUVENKATESH-o5n 2 ай бұрын

Can you make more videos on ReFramework and Orchestrator

@MukeshKala 2 ай бұрын

We have a lot already uplaoded : RE Framework Complete Playlist kzbin.info/aero/PLEYSwx3duQ2BoRamKrEQ6qrZvrL-mAm7p

@manujaggi6056 8 ай бұрын

Hi @MukeshKala Thanks for creating such important content. I have one question by using Object Repository. Under Object Repository, I need to create multiple screens and for each screen we have multiple UiElement descriptor. But with our existing classic approach, I used browser instance, which I was passing to xaml library project in that way, if any page title changes then there is no change needed. And with object repository approach, every screen having own title attached, if that changed this will create extra work for me. Do you suggest how I can use Object Repository in such scenario where my automation belongs to multiple pages having different title on each page which often changed or you can say dynamic(where I can't handle it with wildcard selector). Please suggest.

@MukeshKala 8 ай бұрын

Good Question : You can incorporate variables within your descriptors to handle dynamic elements. For instance, if the page title changes, you can use a variable to represent it in your selector. This way, even if the title varies, your descriptor remains adaptable. Variables can be set dynamically during runtime based on the actual page title. To achieve this, create a variable (e.g., pageTitle) and use it in your descriptor. Then, assign the correct value to pageTitle based on the current context.

@MukeshKala 8 ай бұрын

I might record a video on same

@manujaggi6056 8 ай бұрын

@@MukeshKala But still with above mentioned approach, I need to do the code to handle the dynamic title via variables from client application. And If I have 10 client application then I need to make changes in all 10 client application This was not the case with classic browser instance variable which I can pass to Classic Library xaml projects.. Still I feel Classic Design approach is best suited for such scenerio. Please correct me in case you think otherwise.