Unable to Retire cmdb_ci Records with last_scan Older Than 30 Days via Retire Policy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours 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
