View Audit Trail Exports

Overview

Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Audit Trail.

Access audit trail files, which document the actions that the company's users took in TraceLink. Audit trail files provide visibility into the exact date and time that a particular user made a change, the data that was updated, and where the change occurred (e.g. which application, whether the user touched the UI or a map).

The audit trail identifies the actions that the company’s users took in TraceLink. In order to see the specific details associated with that action, review the exact business object within the system that the audit trail points to. Export the transaction details in Info Exchange or review a compliance report in the applicable compliance app to view asynchronous transaction information. Users can also export a full life cycle of a serial number in Serialized Operations Manager (SOM) Serial Number History.

Table

The table on this screen shows the audit trail data files generated in the last 2 weeks.

  • Date Generated – Date that a user generated the audit trail export.
  • Requested By – The email of the user who generated the audit trail export.
  • Audit Data On or After – The audit trail export includes data from on or after this date.
  • Audit Data on or Before – The audit trail export includes data from on or before this date.
  • File Name – Link to the audit trail export file(s).
Date Generated Requested By Audit Data on or After Audit Data On or Before File Name
07 Mar 2016 09:17 AM GMT tl_admin+kendallpha@tracelink.com 06 Mar 2016 07 Mar 2016 AuditTrail_07Mar2016968_20160306_201603071.csv
AuditTrail_07Mar2016968_20160306_201603072.csv
AuditTrail_07Mar2016968_20160306_201603073of3.csv
06 Mar 2016 05:47 PM GMT tl_admin+kendall20150615@tracelink.com 05 Mar 2016 06 Mar 2016 AuditTrail_06Mar2016542_20160305_20160306.csv

Available Actions

  • Select a File Name link in the last column of the table.

    The file downloads.

    See Export a CSV File to Excel in Troubleshooting.

The CSV file must be properly formatted or it will not be accepted by TraceLink.

When downloading a CSV file, select Save rather than Open, and:

  • View the file in MS Excel. See Export a CSV File to Excel in Troubleshooting.
  • View the CSV file in a text editor.

The following example is truncated for viewing because of the large amount of element headers. For the complete list of element headers, see the Element Headers drop-down below.

These element headers are all required in the CSV file, in order and separated by commas or columns, as shown in the formatting example below.

  • eventDate – The date and time the event occurred in GMT.
  • performedBy – The email address of the integration user, integration principal, or company user performing the action. The integration user or intergration principal allows a company to assign roles and configure an app without assigning a specific user to apply the changes. The integration user or integration principal does not exist in the TraceLink SSO, and this user cannot log into the UI.
  • performedByCompany – The company of the user performing the action or an identifier of the Company for events initiated via API or B2B exchanges using an integration user or integration principal.
  • supportAccessAccount – The email address of the TraceLink Support Representative performing an action on behalf of the performedBy user.
  • functionalArea – The app that the event occurred within.
  • businessObjectType – The part of the app that the event occurred within.
  • businessObject – The specific object within the businessObjectType that the user updated (e.g. if a user is a businessObjectType, then the user's email is the businessObjectjsmith@company.com, Location 2350014).
  • action – The action the user performed (e.g. Create, Modify, Delete).
  • modifiedData – The data field that the user updated:
    • Identifies the field name, the old value, and the new value in the following format: <FieldName>: <oldValue or -->, <newValue or --> Or
    • Text that describes the change (e.g. Login, Logout, Password Changed, Invitation Sent) Or
    • For B2B message exchange, the file name provided.
  • reasonForChange – The reason for an update if the app requires a reason for change for that update. For example, if a user adds or removes administrator access.
A B C D E F G H I J
eventDate performedBy performedByCompany supportAccessAccount functionalArea busisnessObjectType businessObject action modifiedData reasonForChange
2024-03-13T04:28:15Z tl_admin+kendallpharma@tracelink.com Kendall Pharma   Service Admin Service Member

Serialized Operations Manager -

tl_admin+kendallpharma@tracelink.com

 Modify Permission: --,Service Admin ; Service Admin: false, true  
2024-03-13T04:29:56Z rxwholesaler_admin2@tracelink.com Kendall Pharma  

Company Admin,

User Settings

 User rxwholesaler_admin2@tracelink.com Modify Action: Logout  
2024-03-13T05:15:58Z tladmin+kendallpharm@tracelink.com Kendall Pharma Sally.Goodwell@tracelink.com Serial Number Exchange Serial Number Response GTIN-14 - 04400000050023 Create Number Encoding: --,AI(01)+AI(21); Service Name: --, Serial Number Exchange; Filter Value: --, 0 ; DateTime: --, 13 Mar 2024 07:36 AM GMT; Subscriber Company Name: --, SUPRITESTUSBRADLEY; Product Code: --, 04400000050023; Product Identifier Type: --, GTIN-14; Identifier Value: --, 04400000050023  
2024-03-13T06:21:21Z tl_admin+kendall20150615@tracelink.com Kendall Pharma   Company Admin User tl_admin+kendall20150615@tracelink.com Modify Action: Login