Welcome to Community Week 2025! Join us to learn, connect, and be recognized as we celebrate the spirit of Community and the power of AI. Get the details  

CMDB Data Manager Retirement Policies

Gus1
Tera Expert

We're trying to setup a retirement policy for the vCenter Instance class.
We've created the following CMDB Retirement Custom Definition (Rule):

Gus1_0-1729532771309.png


And we've created the following policy:

Gus1_1-1729532853664.png


When the scheduled job "CMDB Data Manager Retire Policy Processor" is executed the task is created and processed in the cmdb_data_management_task table but the ci's found don't appear to have been retired. What are we missing here?

1 ACCEPTED SOLUTION

Tony Branton
ServiceNow Employee
ServiceNow Employee

The Retirement Definition you set is using a "is not" operator, so this means that when Data Manager attempts to set a CI's Install Status field it will use any value except "Retired".

 

The purpose of Retirement Definitions is to specify the field and value for a CI class that equates to retirement.  In the case above the Retirement Definition should be Install Status is Retired.

 

Note that Retirement Definitions can only specify a single value for a field included in the definition - multiple values for a single field are not supported.

View solution in original post

1 REPLY 1

Tony Branton
ServiceNow Employee
ServiceNow Employee

The Retirement Definition you set is using a "is not" operator, so this means that when Data Manager attempts to set a CI's Install Status field it will use any value except "Retired".

 

The purpose of Retirement Definitions is to specify the field and value for a CI class that equates to retirement.  In the case above the Retirement Definition should be Install Status is Retired.

 

Note that Retirement Definitions can only specify a single value for a field included in the definition - multiple values for a single field are not supported.