Unable to Retire cmdb_ci Records with last_scan Older Than 30 Days via Retire Policy

颯史小 · 3 weeks ago

I want to use the “Retire Policy” in CMDB Workspace > Data Manager to retire records in cmdb_ci whose last_scan date is older than 30 days.

I tried the following steps:

Open Manage retirement definitions (cmdb_retirement_custom_definitions)

Click Add definition

Create and save a definition using the above condition

However, when I try to save it, I get the error:

“The use of 'OR' conditions are not permitted when defining retirement state. Single conditions and conjoined conditions using 'AND' are allowed.”

Does this mean that this method cannot be used? Do I have no choice but to write a business rule?

I want to use the “Retire Policy” in CMDB Workspace > Data Manager to retire records in cmdb_ci whose last_scan date is older than 30 days.

I tried the following steps:

・Open Manage retirement definitions (cmdb_retirement_custom_definitions)
・Click Add definition
・Create and save a definition using the above condition

However, when I try to save it, I get the error:

“The use of 'OR' conditions are not permitted when defining retirement state. Single conditions and conjoined conditions using 'AND' are allowed.”

Does this mean that this method cannot be used? Do I have no choice but to write a business rule?

Maniteja_2003 · 3 weeks ago

Hi @颯史小 ,

Please follow the below steps to create a Data Management Policy:

Navigate to CMDB Workspace.
Open the Management tab. In the Quick Links section under Management, select Data Manager.
Click on Create New Policy to create a new Data Management Policy.
In the General tab, fill in the mandatory fields such as Name and Policy Type. Select the Policy Type as Retire, then click Continue.
In the Filters tab, apply the required conditions to filter the CIs. Click Apply Filter, review the records, and then click Continue.
Choose the assignment type for the task — either a specific User, a User field, or a Group.
In the Options tab, select the Subflow that should run after the scheduled job executes.
In the Schedule tab, click continue to schedule the Policy.
Review the policy details and click Publish Policy.
Navigate to Scheduled Jobs and search for Retire Policy Processor.
Open the scheduled job and click Execute Now to run the policy manually.
Once executed, the system creates CMDB Data Management Tasks with the Assigned To field populated based on your configuration. You can view these tasks in the My Work tab within the Workspace or directly from the cmdb_data_management_task table.

Regards,
Maniteja.

View solution in original post

颯史小 · 3 weeks ago

Thank you. Your answer was very helpful.
I have an additional question:
I want to delete CIs that have been retired for 90 days.
Is it possible to achieve this using only a deletion policy?
Currently, it is possible to specify a value such as ‘Life Cycle Stage is End of Life,’ but I don't know how to set a condition like ‘90 days after that value was set.’

Maniteja_2003 · 3 weeks ago

Hi @颯史小 ,

Creating a CMDB Retirement Custom Definition applies a default filter to the selected class. This filter is automatically reflected when you create a Data Management Policy.

For example, if you create a Retire custom definition, the conditions you specify there are applied by default while creating the Retire policy. As a result, only the CIs that meet those conditions will be displayed.

Additionally, within the policy itself, you can further refine or add more filters if needed. Please note that the custom definition is applied to every policy created for that class, serving as a baseline filter across all related policies.

Regards,
Maniteja

颯史小 · 2 weeks ago

@Maniteja_2003
My question is specifically about the Deletion Policy, not the Retire custom definition.
In this case, how should I configure the conditions in the deletion policy to achieve the 90‑day‑after‑retirement deletion?