Transaction Logging and Audit

Activity on the VOSS-4-UC system results in transactions that are recorded. The Transaction menu provides auditing information for each transaction.

The recorded information includes:

  • Transaction ID - identifier of the transaction.
  • Detail - A brief description of the processed transaction.
  • Username - Of the user who initiated the transaction.
  • Action - The type of action recorded in the transaction, for instance Execute, Create, Modify, Data Import and so on.
  • Status - for running transactions, this is In Progress; for completed transactions it is Fail or Success.
  • Submitter Host Name - The host name of the application node that scheduled the transaction. On a clustered system, this can differ from the Processor Host Name.
  • Processor Host Name - The host name of the application node that processed the transaction (this value will only be set once the transaction is processed). On a clustered system, this can differ from the Submitter Host Name.
  • Rolled Back - Indicates whether the transaction was rolled back or not.
  • Priority - The priority of the transaction, for example Normal.
  • Submitted Time, Started Time and Completed Time - The date and time of the progress of the transaction.
  • Duration - The duration of the selected transaction. If there are sub-transactions, this parent transaction duration is the total duration of the transaction. This includes the total duration of import transactions that carry out provisioning workflows asynchronously.

On the GUI, details of a specific transaction are displayed when the transaction is selected from the list view. Refer to Bulk Load Transactions.

When a transaction is selected, the Base tab shows details of the columns of the transaction list view. The button bar on the detail list view shows Help and Refresh buttons if the transaction is still running. If the transaction is running, click the Refresh button to update the Progress field.

Lists of transactions can also be filtered. Refer to Filtering Lists for details.

If you want to cancel a transaction while it is still running, click the Cancel button. If a transaction, with sub-transactions, is canceled, the sub-transaction currently in progress will complete. This sub-transaction as well as all preceding sub-transactions will then roll back to their previous states. Note that bulk load transactions do not follow this behavior. Each bulk load sub-transaction is seen as a main transaction, and only the ‘in progress’ sub-transaction will roll back to its previous state.

A Replay button is available if the transaction is complete. A transaction can be replayed if required, for example if a transaction failed because a target system service was not running. The replay of the transaction can then be used instead of re-entering data on a GUI form.

An Edit and Replay button is also available for completed transactions. This is similar to the Replay button, but allows you to first make changes to the previously submitted form before the transaction is resubmitted.

The button is available for transactions that did not originate from bulk loads, wizards or pop-up forms.

Replay and Edit and Replay functionality are not supported by the bulk loader, because the bulk load files are not stored by default. The bulk loader extracts data from the spreadsheets and then performs the necessary action(s). The only time a bulk load file is stored in the database is when the bulk load is scheduled. In this case, the bulk loader keeps the file until it is triggered by the scheduler to execute the actions in the file. When the data is extracted from the file, it is deleted.

When using Edit and Replay for a failed Quick Add Subscriber transaction, the user information fields will not automatically update when changing the Username field:

  • Entitlement Profile
  • Firstname
  • LastName
  • Email
  • Jabber Device

These need to be edited manually.

Selecting the button opens the original input form that resulted in the transaction. The form also contains the original data that was posted. This data can be edited and the form can be submitted to replay the transaction. This functionality can therefore be used to for example edit a failed transaction or to modify data of a successful transaction.

Since GUI Rules apply to a form from a specific hierarchy, the Edit and Replay functionality should only be used from the same hierarchy as the original transaction was executed.

If a transaction has sub-transactions, a sub-transaction list is available on the form, with links to their details. The sub-transaction form displays a link to a parent transaction. On the transaction list view, sub-transactions are identified by a child preceding the Id number.

Failed transactions show a Message of the error. However, a sub-transaction with a Create action that has a “fail on error” workflow condition for duplicates, may show its Status as Fail when not creating a duplicate, while the parent transaction then shows its Status as Success.

For asynchronous transactions and sub-transactions, refer to Parent and Sub-transactions for Asynchronous Transactions.

The Log section on the Transaction base tab displays Message and Severity details of transactions performed by VOSS-4-UC. For example, if the Severity has the status of error, the Message section can be expanded to inspect the error, and optionally copy it send it to Support. If a workflow is inspected, a separate log entry provides details of each step with a log message as Step n, starting with Step 0. For more details, refer to Transaction Log Example.

The Resource tab, which has content for transaction types where a resource changed, displays the additional information, depending on the transaction type:

  • Hierarchy - The point in the hierarchy at which the transaction occurred.
  • Model Type - For example data/User.
  • Current State - if available, click the Entity link to inspect the instance on the GUI form.

The Back button on the button bar can be used to navigate to the previous screen, for example from the parent transaction screen to the list view of all transactions.