FAQ about Entity History

FAQ about Entity History

• Unlike the approach used for the Activity Log, Entity History only uses one form of storage and is supported by a NoSQL database technology that provides low-latency retrieval of large volumes of historical data.

• The retention period of Entity History is also configurable and is generally set to the same length as the Activity Log Cold Storage Retention Period (e.g., 1 to 7 years). It would be illogical to typically place it differently than what is set for the Activity Log.

• Export is not available for Entity History. While technically speaking, there is an API that the History tab leverages for its purposes, querying the history table directly is not positioned as a customer-facing capability nor documented in our customer-facing documentation. One simple reason is that the data within the Entity History storage is not held in a customer-usable format. It is held in a manner designed to support the ability of the History tab to synthesize the snapshots shown in the UI. 

• When a user performs a “hard delete” on an entity, the entity's Entity History within GBT is deleted. (This behavior differs from what we saw for the Activity Log Cold Storage.)

• Updates are displayed in green, and deletes are in red.

Open image-20250127-223459.png

• You can search for specific activity by looking in the history tab.

Open image-20250127-223353.png

• You can compare a historic slice to another slice by selection a compare view from the drop-down list.

Open image-20250127-223234.png