Hi community and hi to @Tony Branton
I'm digging deeper into to CMDB Data Manager and we want to leverage the Policy Type "Archive". This works fine as long as you just want to archive records based on your definitions.
Where the systems currently breaks is, when I want to have a destroy rule for the previously archived records. Meaning:
1. Archive Policy set up via CMDB Data Manager
2. leverages the OOB archive rule "Archive Configuration Items" which respects table hierarchy
3. set destroy rule to active on "Archive Configuration Items" Archive Rule
Result:
Records are not being deleted in the respective child tables.
My assumption:
The system scheduler job "Archive Destroy" is not respecting table hierarchy, therefore looks only on cmdb_ci level to destroy records within the archive rule "Archive Configuration Items".
This means in the end, that we can not leverage CMDB Data Manager setting up archive policies IF the archived records should be deleted later (which is usually the case).
Is this issue known to the respective ServiceNow product team and if yes, when can a improvement of this situation be expected (estimation)?
Thx and greetings.
