Restrict CI insert/update in CMDB when operational status is 'Retired'

[Nishant16]

I need to restrict CI's insert/update in CMDB when the Operational status is 'Retired' from a CI. For this i tried writing a business rule on condition 'Operational status' is 'Retired' and abort the action, however it doesnot work, even when i update the operational status from 'Operational' to 'Retired' then also it gives the error and cannot update the CI operational status to retired.

why the Business rule fail when the Operational status is still 'operational' and not updated to 'Retired' still gives an invalid update error.

Can someone suggest? what is the best approach to restrict ci insert on Retired Operational status?

[Dr Atul G- LNG]

Hi @Nishant16 

Why not you use UI policy and make the field read only at retire as status.

[Nishant16]

hi Atul
I want to restrict all/any updates to the CI when the operational status is Retired, so that if any CI which is Terminated on Azure, discovering in Servicenow can also be aborted on insert.
This is where the BR is failing and i cant seem to figure out

[Dr Atul G- LNG]

Thanks for clarification @Nishant16 . In this case ,as data updated by other system BR is best option.

[Abhijit]

try condition Operation Status changes to "Retired"