Hello everyone,
I realized this while patching our client environment 10.2.3 to 10.2.4 and also opened a case to verify / document it. During this time I think it may be helpful to warn about a new feature. A feature that I also requested many times and IBM delivered ;) This is a good feature when there is lots of movement and data changes to clean up hierarchies, just the switch is documented wrong.
This is about the new three option choice about custom hierarchies. Hierarchy empty node retain option
Here it says, it was previously on Retain None and there was no other option. With the new patch you can select from three. However, as far as we know from our environments, old behaviour was "Retain ALL" ("retain none" was way too old I guess, 5.2.x times and we asked for it to change again that time :D )
This means if you just patch it without touching anything, after the restart, it may clean empty nodes (no people with such data at that time) even if there are assignments to them. This may cause issues when you have lots of assignments waiting for next "Manager" to arrive but there is none just during one hierarchy refresh.
What to do? Before stopping servers for patching, take all hierarchies to Maintenance mode. Patch as usual. Change the new hierarchy setting to your liking. (Retain all for previous behaviour) then take every hierarchy to online again.
Hope it helps,
------------------------------
Ali Malik Gürbüz
Bilgibirikim A.S - Turkey/EMEA
IBM Business Partner
13+ Years with ISIM/ISVG etc.
5.2.5 Certified Exam Developer *I* - 2019
IBM Champion 2025
------------------------------