Transaction Log - System Administration - On-Premises - English - Foundation 22.1 - OnBase - Essential - Premier - Standard - external - Essential - Standard - Premier

On-Premises System Administration
Platform
OnBase
Product
System Administration - On-Premises
Release
Foundation 22.1
License
Essential
Standard
Premier

Transaction Logs keep track of every action that occurs within the system and can provide you with an audit trail. Transaction Logs are stored in the Document Type of SYS - Transaction Logs, and can be retrieved through the Document Retrieval window.

Every time a Transaction Log is opened, you will have access to the latest information.

  1. From the Client module, select Admin | Transaction Logs.
  2. Select View All Messages and choose a Transaction Log to open. By default, the log entries are sorted in descending order, that is, the more recent entries are listed first.

    • The Action column gives a brief description of the action that took place.

    • The Subaction column gives a more detailed description of the action that took place.

    • The Detail column gives a very detailed account of everything that happened during the action. This can include the type of action, the document handle number, the document name, and the date the action happened.

    • The Transaction Log for Institutional Databases also notes the Institution number associated with the action. This number reflects the Institution as logged by the processing file itself.

    • The Log Date lists the date the action took place. Even if multiple actions occur on the same date and time to the second, they will sort properly to show which occurred first.

      Note:

      The Log Date column will always be displayed using the time zone used by the database server.

    • The Log Time lists what time of day the action took place, based on a 24 hour clock.

      Note:

      The Log Time column will always be displayed using the time zone used by the database server.

    • The User Name displays the name of the user who was logged onto the workstation when the action took place.

    Note:

    Depending on your system configuration, the real name of the user may be displayed in the User Name column instead.

    Note:

    For failed logins (incorrect user name or password), the event will be logged for the Admin user account, since no valid user can be associated with the action.

    Note:

    When OnBase is deployed in a multiple language environment, multiple languages can appear in the Transaction Log. This is because the OnBase Client uses the language locale of the workstation to log transaction messages.