CMDB Duplicate Task-CI's no longer duplicates
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2023 08:47 AM
I'm trying to clean up some older Duplicate CI tasks and have a few questions.
1. If the indicated CI's are no longer duplicates of each other (Serial Numbers have been updated) what is best practice to resolve the Duplicate Task? I tried deleting them but they came back when the Health Jobs ran with an updated Created On date.
2.. I don't understand the Last Evaluated On Date field. The date updates to the last time the Health Jobs ran but nothing seems to happen. Is it checking to see if the CI's in question still satisfy the duplicate criteria? If it was re-evaluated and the CI's are no longer duplicates, should the task resolve itself automatically?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2023 12:18 PM
Sabastian, What we have been doing in cases like this, is setting the Task to Closed Incomplete. If there are specific attributes on a CI which can't be populated, we Fail the Attribute with a note for later reporting, then set the Task to Closed Incomplete.