With the Audit trail feature, you can find out a certain configured number of Context Store operations performed on a context during the lifecycle of the context.

Audit trail records all successful interactions with a context and stores the information inside the context object as an extra field. If you enable the Audit trail feature, you can find out which application created or updated the context. You can also track the operation types, such as Create, Read, Update, and Delete that were performed on the context. The audit entry of a context also provides information such as the time at which the operations were performed and the version of the context.

The ContextStoreRest API accepts touchpoint, which is any application that can interact with ContextStoreRest APIs, as a parameter for each interaction. The touchpoint parameter is an alphanumeric ID.

If you add or modify a context without providing the touchpoint parameter, the touchpoint value of the audit entry is set as undefined.

The versionId of a context increases with each interaction, such as UPDATE, GET, PUT, and DELETE, with a context.

For more information about the touchpoint parameter, see Avaya Context Store Snap-in Developer Guide.

If you enable persistence to an EDM and set Persistence Type to Audit, then the full context for each audit entry is written to the EDM. You can then query and retrieve these audits through the ContextStoreQuery service. For more information about persistence types, see External Data Mart persistence.

In Context Store with Avaya Oceana® deployments, GET operations without a specified touchpoint do not get replicated to EDM.