CI Retirement Tasks Skipped / Canceled

[JasonW39]

I've created a Retirement Policy that fires a CMDB task when computer CIs have not been discovered in 60 days.

I've run into a few instances where a CI where a task was fired, but the group that the task is assigned to does not want to retire the CI (as it will likely return to the environment).  If the approver decides to reject the task, or if they change the status to 'Closed Skipped' or 'Closed Canceled' -- will a new task be generated next time the corresponding job runs, or will the CIs associated with the Closed / Skipped / Rejected CMDB task get added to some kind of exclusion list?

Thanks!

[Tony Branton · Accepted solution]

Unless the CI record is added to the exclusion list in Data Manager, the next time a Retire policy is executed the CI will show up in the task generated.  CI records can be excluded in the following:

• Review page when editing a Data Manager policy (excepting Certification policy types)
• Reviewing records in a task
• The Excluded Records section in Data Manager

Screenshots for each of the options:

Figure 1 - Excluding from policy

Figure 2 - Excluding from task

Figure 3 - Excluded Records view in Data Manager

Hope this helps.