Contents Now Platform Administration Previous Topic Next Topic History sets ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Other Share History sets The system generates history set records when a user requests to view an audited record's history. Each record's History Set will be generated when the record is inserted, if the record is on an audited table. A user must view a record for the system to create or update a history set for that record.Note: Do not use history sets to generate reports. Several fields of information are captured in the History Set record, displayed in the list view.Table 1. List View Record Fields Field Input Value ID A Document ID for the record whose history is being recorded. Table The audited table for the record whose history is being recorded. Load Time The amount of time it took to generate the history set. Table 2. Audit History Record Fields Field Input Value Label The label of the field which was changed. Old The value before the change. New The value after the change. Type Indicates if the entry is for a normal field, an email record, or a relationship change record. Update Number The number of times this field has been changed. A value of -1 indicates when the record was created or deleted. Update Time The date and time of the change User Name The name of the user who created the change. History Sets in a Calendar View Once History Sets are active, the context menu choice History will populate using information from the History Set, rather than from the sys_audit table. From the user's perspective, the same historical data is available in the same user interface, but the way the information is stored is different. The History view includes a calendar view, but does not use the normal list interface to filter and interact with the history records. This allows: Searching and filtering historic data. Exporting historic data. Viewing history sets There are two ways of viewing the history set, accessible through the Context Menu action History. Differences Between Audit and History SetsThe Audit [sys_audit], History Sets [sys_history_set], and History [sys_history_line] tables store the same data, but they serve different purposes and manage data differently.Control access to historyYou can give a role access to view audit history by setting a system property.Change the number of history entriesBy default, the history displays a maximum of 250 history entries, but you can change this value.History ListThe history list displays each change as its own row in the change list. History CalendarThe history calendar shows you the days where the record was changed, who made the change, and when.History TimelineYou can view a timeline of changes for a CI and for its related records, relationships, baselines, and proposed changes for the CI. Timelines are available for CIs in the Configuration Item [cmdb_ci] table or a descendant of this table, if auditing is enabled for the tables.Tracking changes to reference fieldsAdministrators can track changes to reference field display values.Tracking insertsBy default, the system does not create Audit records for inserts because in a typical instance, inserts can account for over 80% of the size of the Audit table.Tracking CI RelationshipsChanges to a CI relationship (CI Relations, CI/User Relations, or CI/Group Relations) appear in the history of the items on both sides of the changed relationship regardless of whether the change was manual or a result of Discovery. On this page Send Feedback Previous Topic Next Topic
History sets The system generates history set records when a user requests to view an audited record's history. Each record's History Set will be generated when the record is inserted, if the record is on an audited table. A user must view a record for the system to create or update a history set for that record.Note: Do not use history sets to generate reports. Several fields of information are captured in the History Set record, displayed in the list view.Table 1. List View Record Fields Field Input Value ID A Document ID for the record whose history is being recorded. Table The audited table for the record whose history is being recorded. Load Time The amount of time it took to generate the history set. Table 2. Audit History Record Fields Field Input Value Label The label of the field which was changed. Old The value before the change. New The value after the change. Type Indicates if the entry is for a normal field, an email record, or a relationship change record. Update Number The number of times this field has been changed. A value of -1 indicates when the record was created or deleted. Update Time The date and time of the change User Name The name of the user who created the change. History Sets in a Calendar View Once History Sets are active, the context menu choice History will populate using information from the History Set, rather than from the sys_audit table. From the user's perspective, the same historical data is available in the same user interface, but the way the information is stored is different. The History view includes a calendar view, but does not use the normal list interface to filter and interact with the history records. This allows: Searching and filtering historic data. Exporting historic data. Viewing history sets There are two ways of viewing the history set, accessible through the Context Menu action History. Differences Between Audit and History SetsThe Audit [sys_audit], History Sets [sys_history_set], and History [sys_history_line] tables store the same data, but they serve different purposes and manage data differently.Control access to historyYou can give a role access to view audit history by setting a system property.Change the number of history entriesBy default, the history displays a maximum of 250 history entries, but you can change this value.History ListThe history list displays each change as its own row in the change list. History CalendarThe history calendar shows you the days where the record was changed, who made the change, and when.History TimelineYou can view a timeline of changes for a CI and for its related records, relationships, baselines, and proposed changes for the CI. Timelines are available for CIs in the Configuration Item [cmdb_ci] table or a descendant of this table, if auditing is enabled for the tables.Tracking changes to reference fieldsAdministrators can track changes to reference field display values.Tracking insertsBy default, the system does not create Audit records for inserts because in a typical instance, inserts can account for over 80% of the size of the Audit table.Tracking CI RelationshipsChanges to a CI relationship (CI Relations, CI/User Relations, or CI/Group Relations) appear in the history of the items on both sides of the changed relationship regardless of whether the change was manual or a result of Discovery.
History sets The system generates history set records when a user requests to view an audited record's history. Each record's History Set will be generated when the record is inserted, if the record is on an audited table. A user must view a record for the system to create or update a history set for that record.Note: Do not use history sets to generate reports. Several fields of information are captured in the History Set record, displayed in the list view.Table 1. List View Record Fields Field Input Value ID A Document ID for the record whose history is being recorded. Table The audited table for the record whose history is being recorded. Load Time The amount of time it took to generate the history set. Table 2. Audit History Record Fields Field Input Value Label The label of the field which was changed. Old The value before the change. New The value after the change. Type Indicates if the entry is for a normal field, an email record, or a relationship change record. Update Number The number of times this field has been changed. A value of -1 indicates when the record was created or deleted. Update Time The date and time of the change User Name The name of the user who created the change. History Sets in a Calendar View Once History Sets are active, the context menu choice History will populate using information from the History Set, rather than from the sys_audit table. From the user's perspective, the same historical data is available in the same user interface, but the way the information is stored is different. The History view includes a calendar view, but does not use the normal list interface to filter and interact with the history records. This allows: Searching and filtering historic data. Exporting historic data. Viewing history sets There are two ways of viewing the history set, accessible through the Context Menu action History. Differences Between Audit and History SetsThe Audit [sys_audit], History Sets [sys_history_set], and History [sys_history_line] tables store the same data, but they serve different purposes and manage data differently.Control access to historyYou can give a role access to view audit history by setting a system property.Change the number of history entriesBy default, the history displays a maximum of 250 history entries, but you can change this value.History ListThe history list displays each change as its own row in the change list. History CalendarThe history calendar shows you the days where the record was changed, who made the change, and when.History TimelineYou can view a timeline of changes for a CI and for its related records, relationships, baselines, and proposed changes for the CI. Timelines are available for CIs in the Configuration Item [cmdb_ci] table or a descendant of this table, if auditing is enabled for the tables.Tracking changes to reference fieldsAdministrators can track changes to reference field display values.Tracking insertsBy default, the system does not create Audit records for inserts because in a typical instance, inserts can account for over 80% of the size of the Audit table.Tracking CI RelationshipsChanges to a CI relationship (CI Relations, CI/User Relations, or CI/Group Relations) appear in the history of the items on both sides of the changed relationship regardless of whether the change was manual or a result of Discovery.
