Background: My organization has some types of hardware, like printers and network gear, where the corresponding CI has a fixed name, but the related asset might change when the hardware is replaced. For example, printer HDQ1P1 might have started with asset 1234, but was swapped out for asset 5678. If the old asset is repairable, it might go back to stock, or if not, it might sit in Asset Management as Retired according to our retention requirements.
This has led to some situations where duplicate CIs are identified, and each has a different asset. For example, we might have CI X and CI Y which are actually the same, but CI X has Asset A, and CI Y has Asset B.
We currently have our cascade reference rules set up on tables cmdb_ci and alm_asset to be Restricted, so that valid assets are not deleted when someone tries to delete a CI, and valid CIs are not deleted when someone tries to delete an Asset.
We've had some discussion around setting the cascade reference rules to Clear, but ideally we would only want that relationship cleared if the asset is not in use/operational.
Is there a way to configure things so that deleting CIs during de-duplication would clear the reference to the asset only if the asset is not in use/operational?
