Insights & updates from our experts
From now on, when the status of a configuration item is set to ‘Removed’, its service, service instance, CI and user relations are automatically removed.
Apart from helping to keep the CMDB relations accurate, this ensures that removed configuration items (i.e. CIs for which the support organization no longer has any responsibility) no longer show up in the Service Hierarchy Browser (SHB).
In addition to automatically removing these relations after a CI has been removed, a small usability feature has been added that makes it easier to identify inactive CIs. When the status of a CI is ‘Archived’, ‘To Be Removed’, ‘Lost or Stolen’ or ‘Removed’, its name is written in strikethrough characters when it is presented in View mode, and the disabled symbol is displayed over the CI’s picture to indicate that it is no longer active.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.







.webp)
%20(1).webp)



.webp)














