Restrict CI insert/update in CMDB when operational status is 'Retired'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-11-2023 09:34 AM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2023 08:19 AM
I strongly suggest using the conditions on the IRE rules to restrict the insert/update based on the retired state. Please refer to https://docs.servicenow.com/bundle/vancouver-servicenow-platform/page/product/configuration-manageme...
When every rule has this condition then when insert/update it won't match on any rule and it will abort the insert/update automatically.