Data Manager retire Policy

[baba]

Hi All,

in my PDI i tested the 'Retire Policy' in the Data manage for stale CI ( 2 CIS ) which were not updated for specified timeframe(More than a month). it created Remediation tasks in the cmdb_data_management_task_to_ci table.  once of the task was approved the life cycle stage and Life cycle stage status changed to End of life and retired respectively. But for Windows server CI Operational status is not changed to Retire as per attachments.

[Tony Branton]

Unless you've installed the CSDM Activation plugin and enabled the mapping table, any updates to the Life Cycle Stage/Status fields will not automatically sync to the Operational Status field.  The CSDM Activation plugin was originally a pre-requisite for using Data Manager, however we removed that dependency in the Tokyo release and allowed you to set your own Retirement Definitions.

Retirement Definitions allow you to specify the status fields you want to use to define retirement for a CI class.  Any child CI classes inherit a parent CI class's Retirement Definition.  If you set a Retirement Definition for a child CI class it overrides the parent class's Retirement Definition.

The Retirement Definition is used to set the associated status field(s) in a CI record based on the CI class, and the same definition is then used by the Archive and Delete policy types to act on retired CIs.

We ship OOB Retirement Definitions, however at least one definition must be active and a definition for the  Configuration Item (cmdb_ci) class is set as always being active.  You can change the default definition's configuration to use something other than the Life Cycle Stage/Status fields e.g. Operational Status - remember that all CI classes will inherit that definition unless you specify another definition e.g. using Operational Status = Retired for cmdb_ci_server.

Once you set a Retirement Definition and make it active you should see Data Manager set the associated status field on your CIs.

Note: unless you have a business requirement, there's no need to install and activate the CSDM Activation plugin and mapping table.

[Maniteja_2003]

Hello @baba ,

To have synchronization between the legacy fields (like Operational Status) and the new life cycle fields available on the CI, you need to enable Life Cycle Sync.

Steps to Enable It:

1. Navigate to All > CSDM > Life Cycle Mapping (this redirects to the Life Cycle Mappings table).

2. In the top right corner, click the Enable Life Cycle Sync UI Action.

Note:
If any required fields are not populated in the existing records, Life Cycle Sync will not be enabled. When you click Enable Life Cycle Sync, a pop-up appears listing the fields that must be mandatorily populated. Please ensure those fields are filled before enabling Life Cycle Sync.

[Tony Branton]

As mentioned above, you do not need to install and activate the CSDM Activation plugin in order to use Data Manager for Retire/Archive/Delete operations.  You can configure Retirement Definitions in Data Manager to set the status fields appropriate for your use case.  This approach avoids any overheads incurred by installing and activating the CSDM Activation plugin.