---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Knowing about History sets

# Knowing about History sets {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

The system automatically generates History Set records as needed from the Audit table
when a user either creates a record or views its history.  
If a record is in an audited table, its history set is generated when the record is inserted or when a user views the record.  
Hinweis:  
Don't use history sets to generate reports.
Several fields of information are captured in the History Set record, displayed in the list view.{#c_HistorySets__table_nrt_myd_wq__entry__2}

| Field | Input Value |
|-|-|
| ID | Document ID for the record whose history is being recorded. |
| Table | Audited table for the record whose history is being recorded. |
| Load Time | Amount of time it took to generate the history set. |
[Tabelle : 1. List View Record Fields]

{#c_HistorySets__table_nrt_myd_wq} {#c_HistorySets__table_yym_ryd_wq__entry__2}

| Field | Input Value |
|-|-|
| Label | The label of the field that was changed. |
| Old | Value before the change. |
| New | 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 | Date and time of the change. Hinweis: The Update time for auto-generated history lines doesn't match the Created or the Updated time for a record in a specific processing situation. When you view a history set of a record for the first time, an initial set of history line records is auto-generated. Since file changes in an upgrade aren't audited, this date mismatch occurs when: * You view a history set after a change is made to a record, but * Before another change is made to it in a future upgrade. {#c_HistorySets__ul_hwz_hx5_kmb} |
| User Name | Name of the user who created the change. |
[Tabelle : 2. Audit History Record Fields]

{#c_HistorySets__table_yym_ryd_wq}

## History Sets in a Calendar View

After History Sets are active, the History context menu choice populates 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 how the information is stored is different.

Since the History view includes a calendar view, but doesn't use the normal list interface to filter and interact with the history records, it enables:

* Searching and filtering historic data.
* Exporting historic data.
{#c_HistorySets__ul_lsh_rjd_rw}

## Viewing history sets

There are two ways of viewing the history set, accessible through the Context Menu action
History.