Subject: Reference between Bundles
Dear Sir / Madame,
I normally create a bundle (for example W2-Install Office Stuff) which contains several sub bundles (like Office 2010, Groupwise 2014 , etc etc). And yes... this works fine.
If I look into the sub bundle (for example Groupwise 2014) there is NO possibility to see in what other bundles this one is used. The only possibility I have found so far: delete this bundle and see what information the system gives you back "this cannot be deleted because it is referenced to ....
Why this question? Several collegues have their own Bundle (W1 - Produktion Netherlands, D1 - Office Germany, etc etc). If I want to release a new Groupwise bundle ... and sent them a email, please update your sub bundles (which not everybody does)... I have to open and find them myself. This is very frustrating.
Hearing from you
Kind regards,
William Biemans
Wuppermann Staal Nederland BV
William.biemans@wuppermann.com
Tel: +31 (0)168 357190
by: William B. | over a year ago | Application Mgmt
Comments
Hi William,
On the Summary Tab of a bundle you have an entry 'Dependency Bundles' which shows a 'Display Bundle Dependencies' entry which you can click. This then shows an overview of the bundletree here the current bundle is dependant on. This I think is exactly what you want.
Instead of notifying other to update their dependant bundles I would suggest using a wrapper bundle for that (it's what I always do); for example you have two launch bundles for GroupWise like 'GroupWise NL' and ' GroupWise DE' (for whatever reason as in most cases you could this with just one bundle...).
Today on the Install Tab you probably use a Install Bundle Action 'Install GroupWise Client 2014 SP1'. This means you and the german admin both have to update their 'GroupWise NL' and ' GroupWise DE' bundles case you created 'Install GroupWise Client 2014 SP2'
What I would do is create a wrapper bundle 'INST Groupwise 2014' and on the Install tab create and Install Bundle Action that installs 'Install GroupWise Client 2014 SP1' now and 'Install GroupWise Client 2014 SP2' whenever you are ready with that. The GroupWise launch bundles would no longer need to install the 'Install GroupWise Client 2014 SP1' but can now install the wrapper 'INST GroupWise Client 2014'.
Regards, Sebastiaan
This is a good summary, however If we were able to click on one of those bundle dependencies and open the actions for the selected sub bundle for modification.
For instance, there is a bundle (lets call Install Jave) that is a sub bundle Install XYZ app. (This same java bundle may be a sub bundle related to many bundles.)
Let's say this "Install java" bundle is obsolete and needs to be disabled and deleted.
It cannot be deleted until it is unrelated to all the other bundles.
Allowing to click on the dependency would be helpful to expedite the modification of the bundles (removing the "Install Java" bundle.
Hi Paul,
Indeed an 'Install Bundle' action should be clickable so the depandant bundle can be opened easily. My vote for that:)
A solution for situations where you have to remove-and-readd a dependent bundle could be introducing a 'Replace' or 'Deprecate' option on bundles.
Say:
I have a bundle 'java 7.x' that is used as a dependency in multiple other bundles. I'm aware this situation could existed despite I mostly use a wrapper in between 'INST Java 7' in those bundles:) (see my previous comment).
So, as the Summary tab of the 'java 7.x' has a 'Display Bundle Dependencies' already we could add a 'Replace' button which the starts off a Wizard showing a list of the parent bundles (like the 'Display Bundle Dependencies' does) in which you can select all the parent bundles in which you want to replace the current install bundle action for 'java 7.x'. Now the wizard allows you to select that bundle which would be 'java 8.x'. Last step in the wizard would be to leave all updated parent bundles in Sandbox mode or publish them immediately.
Regards, Sebastiaan
Agreed. that wizard would be great.
I use the Display Bundle Dependencies link on the Summary page as well. I would like the Dependency Bundles list to have hyperlinks. This way I can at least go to that bundle to make changes.