Every change to cards and relationships is kept: you always know who changed what and what things looked like in the past.
Who changed the status of this server, and when? What did the inventory look like on December 31 last year? CMDBuild automatically keeps the history of every card and relationship, with nothing to configure.
What you can do
Past situations
Rebuild how part of the CMDB looked at an earlier date, for example to analyze the context in which a failure occurred.
Know who made the change
For every change you know which operator made it and when, without piecing it together from emails, notes or colleagues' memories.
Inventories at a given date
Produce an inventory as of an earlier date, for example the state of your assets at the close of last year's fiscal year.
Be ready for audits
Show auditors how and when data changed, thanks to a complete timeline that CMDBuild records automatically.
What gets recorded
Every change saves a complete version of the card, along with the period during which it was valid and the name of the user who changed it.
In practice
How to browse the history
From the card
Open the list of all its versions, with the data that changed since the previous version highlighted.
With views and reports
They show the situation at a date of your choice, for example the inventory or the tickets still open at year end.
To create custom reports, including on historical data, see Reporting.
Learn more in the online documentation