Documentation Index

Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt

Use this file to discover all available pages before exploring further.

Auditing

Prev Next

Overview

The Auditing feature provides comprehensive auditing capabilities to track and manage row-level data changes. The Auditing configuration page allows Administrators to enable row-level changes tracking for datasets (table or view) used in a WebApp’s grid or form container.

Once enabled, users can open Audit History for a record to see who changed it, when it changed, what action occurred, and which field values changed.

Note

You must be an Administrator to access the Auditing configuration page.

When auditing is enabled for a dataset:

  • Each row in the related grid displays an Audit icon.

  • The related form container also displays an Audit icon for the current record.

Note

If a grid and a form use the same dataset, both can display the audit history for that dataset’s records.

Enable Auditing

To enable Auditing for a grid or form container dataset:

  1. From the Cloud Construct menu, select Auditing. The Auditing configuration page is displayed.

  2. Click Add Audit Configuration. The Enable Table Audit dialog box is displayed.

  3. From the Datastore list, select the datastore associated with the required WebApp. Note that this datastore will be used to store row-level audit data.

  4. From the Dataset list, select the dataset associated with the grid or form container for which you want to enable row-level change tracking.

  5. The History Table schema and name are optional. Cloud Construct automatically creates a history table for the selected datastore. However, if you have already created a history table, specify its schema and table name.

  6. Click Enable.

A new history table appears in the Auditing page list as an audited table.

Manage Auditing

The Auditing page helps Administrators manage which datasets are currently tracked.

Field Name

Description

Datastore

Specifies the datastore in which the history table is created to store audit data.

Dataset

Specifies the dataset used by a grid or form container for which row-level audit tracking is enabled.

Audit Enabled

Denotes whether auditing is enabled.

History Schema

Specifies the schema in which the history table is created.

History Table

Specifies the name of the history table used to store the following details:

  • User who made the change

  • Date and time of the change

  • Action taken, such as insert, update, or delete

  • Field-level changes with before and after values

Actions

Allows you to disable or enable auditing.

Field-specific filtering options are available through filter icons. Sorting and multi-field sorting can also be applied, but only on supported columns.

Disable Auditing

  1. On the Auditing page, identify the required dataset for which you want to disable auditing.

  2. Click Disable Audit in the Actions column. The Disable Audit dialog box is displayed.

  3. Click Confirm.

After auditing is disabled, the Audit  icon no longer appears in related grids and forms. Disabling auditing stops future tracking for that dataset, but previously captured audit history is preserved.

To re-enable auditing on the disabled dataset, click Enable Audit .