Hi,
We have the following use-case:
VR information is gathered by a VR tool and stored in it's database. On weekly basis we process this information in ServiceNow. Let's say VR info is gathered on the Monday of the week. The involved CI is operational decommissioned and set to Retired_Non-Operational in the CMDB on the Thursday of the same week. During the weekend the gathered VR info is processed.
What we need is that the VR info gathered during this week (in this case the Monday when the CI was still operational) is registered on the CI for historic and analysis purposes. But doing this the CI is set to Installed_Operational again (logical as it is updated) while it's not the case here.
We know that there is a setting to skip already Retired CI's but we can not use this one as we lose the valuable VR info. Does anyone has an other suggestion on how to attack this behavior?
Thanks,
Ed
