3 of 3 people found this helpful
Our process for this is as follows. It's not pretty, but it seems to work for both the Asset and Config teams.
1. For the CI that is deemed to be the duplicate, set it's AssetLifeCycleStatus to Disposed or similar. Change its name to either a prefixed or suffixed alternate. Example, if CI Name is 'Fred', then rename it to
'Disposed-Fred' or 'Fred-Disposed'. Don't use the Delete status since this will fire a bunch of workflow you may not want. This process will keep the various associations and transactional relationships you need and stop the ITSM apps breaking.
2. If there are related CIs, you need to review these and see if they need the same treatment.
3. After an agreed period of time (when the associations to older transactions no longer matter), you can then look for these CIs and physically remove.
4. For the approval mappings, there's not really any magic trick to help here, you need to locate these in the same process as you go through above (renaming the CI etc) and update or remove the mapping.
Thanks Carey.I hope bmc brings in better process to manage these CI relationships and approval mappings.As duplicates CI's can never be eliminated.
One more question,if we rename the CI name as you suggested above,would they reflect in associations I mean in Incident/Change under relationship.
1 of 1 people found this helpful
Yes, they will still be there under the Relationships for the INC/CHG but will have the new name showing (the relationships are based on the recon id of the CI so it simply points to the same CI whose name and status are now changed).
Please feel free to mark any of the answers you get here as Helpful or even better, Correct
Showing the new name for associations is not so good.But will think about the options