Library update in orchestrator

Help Orchestrator
,
1

Hello,

I was trying to find an answer on forum, but I couldn’t.
So this is the situation, I created library in Studio. Then I deploy it to the orchestrator. I use this library in a project which I deploy to orchestrator as well. But then I spotted some weaknes in library, so I added something to library and deploy it again to orchestrator. It is visible with a new version number and description. I did not updated my process and I was expecting that it will use new version of the library. But it didn’t happend. Process is using old version of library.

So this is my question, is it suppose to be this way? Every time I deploy a new version of library I should update process in studio with an update of new library and than deploy it again? Or maybe I’m missing some key step?

2

Hi @Szczepan - Libraries get added as dependencies and we specify the dependency version in each project. hence, if you update the library, you have to open your project, update the dependency version and re-publish the updated project.

3

There’s a “lowest applicable version” setting when managing packages in a project. There should be a “highest applicable version” setting so projects automatically upgrade themselves.

2 Likes
4

With the new UI libraries feature (Object Repositories) this is an even bigger headache. Here’s how it should work…

  1. UI library created
  2. 30 Projects created using UI library
  3. Application that’s part of those 30 projects is upgraded, and descriptors change
  4. UI library is updated with new descriptors
  5. All 30 Projects automatically get new version of UI library and continue functioning

Here’s how it actually works…

  1. UI library created
  2. 30 Projects created using UI library
  3. Application that’s part of those 30 projects is upgraded, and descriptors change
  4. UI library is updated with new descriptors
  5. All 30 Projects break and won’t run
  6. Manually open all 30 Projects and manually update the dependencies
  7. Go through our change management process for all 30 Projects
  8. Manually publish all 30 Projects to Orchestrator

That’s terrible. I thought the Mass Update Tool would be the solution, but it isn’t. It doesn’t actually work with Orchestrator. It should, or there needs to be some other way to automatically update the dependencies in projects without having to open them in Studio and republish them.

5 Likes
5

Hi,

I thought I was doing something wrong but apparently this is the expected behavior.

Is there any update regarding this issue?

6

Hi,

Thanks to the Project dependencies mass update tool you can select one or more libraries you wish to update to the newest release (including the ones you created on your local machine via custom feed), select the projects you wish to update them on and, finally, publish them massively to the orchestrator.

This solution leaves one last “are you sure you want to proceed?” and leaves the agency to update the package only on selected projects.

Cheers