CMDB Data Manager Task to CI Association

[PG2]

Hi All, we are currently operationalising CMDB Data Manager and have learnt that the association between the data manager task and CI gets deleted when the task is completed. This seems dumb. It becomes difficult to identify what retired a CI because there is no association back to the policy that retired it?

Ideally, there is some form of audit trail where a user can easily see that a CI was retired by a CMDB Data Manager retirement policy.

Am I missing something here? 

[PG2]

Closing the loop on this one, with a potential solution option for others in the community to consider.

I learnt that you can set a 'Run As' user against each policy in the following table: 

cmdb_data_management_policy_runtime_attributes

Not sure if this is the intended purpose for setting a value here, but we have created a dedicated system user and set that as the 'Run As' user.

The outcome is that CIs updated by the policy are updated with the system user. Making it easy to identify that a data manager policy has performed the update.