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…
- UI library created
- 30 Projects created using UI library
- Application that’s part of those 30 projects is upgraded, and descriptors change
- UI library is updated with new descriptors
- All 30 Projects automatically get new version of UI library and continue functioning
Here’s how it actually works…
- UI library created
- 30 Projects created using UI library
- Application that’s part of those 30 projects is upgraded, and descriptors change
- UI library is updated with new descriptors
- All 30 Projects break and won’t run
- Manually open all 30 Projects and manually update the dependencies
- Go through our change management process for all 30 Projects
- 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.