Give us a way to upgrade dependencies in Processes in Orchestrator without having to manually republish every project

Feedback Orchestrator
,
#1

It was already a headache to manage dependency versions, and as we grow in our number of automations the headache gets worse.

With the new UI libraries feature (Object Repositories) the headache has grown again. 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.

1 Like
#3

Why on Earth would you remove such a feature? Keeping dependencies updated is a massive hassle, especially now with the new UI object libraries features. This is 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

But 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. Open all 30 Projects manually and update dependencies manually
  7. Republish - including our required Change Management process - all 30 automations

Awful.

2 Likes
Auto Update option missing under Manage Packages
#5

@postwick thanks for your feedback. We are aware of these limitations and we are constantly looking for ways to improve.

Are only UI Libraries the issue for you? Or you encounter the same roadblocks with standard activity libraries also?

#6

Same issue with standard libraries, too. All libraries, activity libraries, UI libraries, standard or custom.

No way to tell Processes to use the latest, no way to bulk update Processes in Orchestrator except for the bulk update tool, but that works out of SVN which presents a problem. The code in SVN may not be the same code that’s in production Orchestrator, so updating in SVN then publishing to Orchestrator is not a safe solution.

1 Like
#7

Thanks for your feedback, I merged the discussions a bit.

1 Like
#8

I totally agree with @postwick , we are facing the same problem

1 Like
#9

Also, The Mass Update Tool doesn’t publish the result to orchestrator , am i missing out something?

1 Like
#10

Nope. I figure all that tool does is go through your code repository and update the project.json files. You’d still need to open and republish the code with Studio/Orchestrator.