In this topic
The application keeps an audit history of the coding changes that users make to field values for documents for the following features: Binders, Issues, Productions (unlocked only), Populations and Samples, and Annotations.
User audit logging for coding decisions is also known as coding history.
Note: Your administrator must enable the Coding History feature, and you must have access to the features for which you want to view audit information. You can then view the coding history for selected documents in a Coding History pane in your workspace.
The Coding History pane, shown in the following figure, provides the following information for actions to documents:
●Field: The feature type, for example, Annotation, Binder, Population, Production (unlocked only), Issue, or Sample.
●Value: The name of the item that was added.
●Previous value: The previous name of the item that was modified.
●Action: Whether the item was added, updated, deleted, or converted.
●Mass coded: The mass coded icon indicates if it was a mass action to multiple documents at once.
●Date: The date and time of the action.
●User: The user name of the user who performed the action.
The following information appears in the Coding History pane for connection changes to data model entity items, as shown in the following figure:
●Field: The entity name.
●Value: The ID of the entity item it is connected to.
●Previous value: The ID of the entity item that was disconnected.
●Action: Linked or unlinked.
●Date: The date and time of the action.
●User: The user name of the user who performed the action.
●Linked: Appears in the Action column when an entity item is connected.
●Unlinked: Appears in the Action column when an entity item is disconnected.
For entities, the following icons appear in the Coding History pane:
●Linked: Appears in the Action column when an entity item is connected.
●Unlinked: Appears in the Action column when an entity item is disconnected.
Use the following procedure to view coding history.
1.Add a Coding History pane to your workspace. Or, use one of the following methods to open the Coding History pane in a standalone window:
oOn the Options menu in the List pane, click Open coding history.
oIn the Conditional Coding pane, click the Coding history button.
Note: If none of the selected documents are coded, you see the message No coding history. If coding history is not enabled for the case, you see the message Audit history is not configured for this case.
2.In the Coding History pane, you can do the following:
oTo see a list of all coding changes, click the History ungrouped button. You can sort and filter the columns in this list.
oTo see a list of coding changes grouped by field name, click the History grouped by coding field button. You can sort and filter the columns in this list.
If the Coding History pane is open in the workspace, and you edit any coding fields, then the coding history updates to reflect the newly saved coding changes.
If the Coding History is open as standalone for a document, and you edit any coding fields for that document, then the coding history updates to reflect the newly saved coding changes.
Use the following procedure to download coding history.
●In the Coding History pane, click the Download history button to download the data a spreadsheet (.csv file).
