- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-08-2017 11:48 AM
When reclassifying a CI using these procedures:
Is there a log to denote that has been performed (besides the History > List on the CI record itself?)
I am trying to answer a question for a colleague who expects there should be a record in the sys_audit_delete table from one 'table' to another 'table' but it does not work like this because there are extended tables and you can usually only downgrade or upgrade along the same set of extended tables.
The colleague is working with a data warehouse so he only sees discreet tables.
Our particular example was about CIs moved from Application Server to Application ci class.
(our version is Istanbul).
Thanks in Advance!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-08-2017 01:23 PM
You can create metric definition to report on ci reclassification changes.
Regards,
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-20-2023 01:34 AM
The History is just a table and with this filtering sys_history_line for field="sys_class_name" should do the trick.
This record would hold in Old and New Value the information about the effective class change.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-20-2023 01:34 AM
The History is just a table and with this filtering sys_history_line for field="sys_class_name" should do the trick.
This record would hold in Old and New Value the information about the effective class change.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-20-2023 08:19 AM
Thank you @Carsten Schnor1 - This was some time ago when my former employer was on Istanbul! I am guessing they are moving to Tokyo this month or in February. Anyhow, I marked it as a good solution to help others.
At the time, I was Service Owner over the Product area of SACM/CMDB and we had a huge issue with people unknowingly doing reclasses by mistake because the transform maps on the data loads were not rigid enough. (The practice was to allow CI objects to be named the same if they were under different CI classes and Companies)
If I remember correctly, we did turn to the sys_history or sys_audit for a specific user and time constraint to be able to revert all the update actions done by that user on the data load by scripting.