Behavior of 'Auto-close VI on Retired CI' within VR module

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-08-2022 04:35 PM
We enabled the 'Auto-close VI's on Retired CIs' option with the Vulnerability Response module. We then marked a CI as "retired". Both status and operational status fields for this CI were set to "retired". However, we are not seeing the existing open Vulnerable Items related to the CI change to "closed-retired".
How does this setting work? Does it only apply to new VIs created AFTER the setting is enabled?
- Labels:
-
Vulnerability Response
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2024 01:27 AM - edited ‎06-16-2025 07:33 AM
Hello Karthick,
the Life Cycle Stage and Life Cycle Status fields represent the the CSDM life-cycle states that can be mapped from the different CMDB state field (Install Status, Operational Status, etc.)
in order to get those populated, you'll need to configure Life Cycle Mapping records to populate the value of the above mentioned CSDM Life Cycle Stage and Status.
You can find here more details around the CSDM Life Cycle mapping: https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/configuration-manag...
and more examples can be found on Now Create: https://nowlearning.servicenow.com/nowcreate/en/pages/assets?id=nc_asset&nc_ai_search=true&sys_id=fb...
Best Regards,
Yasser
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-12-2025 05:08 AM
Hi @sarahjantz ,
I have checked the scheduled job - "Close detections/VIs for decommissioned CIs" and there is some is one issue in the code in the script include being called "Close detections/VIs for decommissioned CIs".
In the function :