Tracking the history of user edits to objects indexed into Object Storage v2. Enable or disable this feature using the Track user edit history toggle in the Datasources tab of the Ontology Manager, as shown in the screenshot below.

To allow user edits, the Edits toggle must be enabled.
Edit history records every edit to an object, regardless of how the edit was made. To capture the decision behind an edit instead, including the parameter values a user submitted and the context at the time of submission, enable action log on the action type.
Edit history uses a UTC commit timestamp that the action captures as it prepares to submit edits to Object Storage v2. When the action type has an action log, the action log and edit history entries for the same action use the same timestamp. This timestamp does not indicate the exact time that edits become visible in queries.
The timestamp supplied by Current User/Time in action rules represents the start of action execution and stays fixed throughout execution. A timestamp property set by this rule can therefore have an earlier value than the edit history timestamp.
preserve edit history is checked during the migration if you want to retain the edit history.After enabling Track user edit history, the Edit History widget can be added to Workshop modules or Workshop-backed object views to display edit histories.
Disabling Track user edit history permanently deletes all existing edit histories for this object type. Before saving the ontology, users will receive a warning and must confirm an acknowledgment that edit history will be deleted.
