The audit consists of saving details about changes and/or actions performed on any data considered critical within the T6 solution. Critical data includes, for example, any change on the Security screen or any value alteration in form cells.
This information is audited so that, at any moment, it is possible to identify who performed a certain change or what the impact of the change was on the model, in terms of performance.
List of information audited by T6:
With the implementation of audits within T6, we can ensure data integrity, track user actions, and generate detailed reports for analysis and decision-making.
To use the Security Audit tool, the user must be added to a Global Group, with the following Manager Feature enabled:
Modifications related to the creation, editing, and deletion of users, groups, and roles are recorded. Changes to access rights for T6 functions, applications users can access, and permissions on objects are also recorded.
T6 audits any changes to the information on the Security screen.
This information, for security reasons, is not visible within the tool. To access it, access to the T6 database is required.
By default, security auditing is enabled during T6 installation.
To enable or disable security auditing, follow these steps:
and locate the parameter Enable Security Audit;To view the Security Audit, follow these steps:
In the main T6 menu, under Access Control, select the Security Audit option:
A spreadsheet will be displayed with the following columns:
| Column | Description |
|---|---|
| Occurrence | Exact date and time of the event recorded in the system, with millisecond precision. |
| Author | User who initiated the recorded action. |
| Source | System module or component where the action occurred (e.g., Login, Permission, Object). |
| Action | Type of operation performed, such as Insert, Delete, Update, or Write. |
| Description | Explanatory text with details about the executed action, such as login performed or permission modification. |
| User | User impacted by the action, which may be the same or different from the author. |
| Application | Name of the application associated with the occurrence, if applicable. |
| Group | Group related to the occurrence, if available. |
| Role | User's role association in the system. |
| Feature | System functionality or resource affected by the action. |
| Object | Specific entity that was the target of the action, such as forms, reports, or accesses. |
| Context | Complementary data in structured format (JSON), containing information such as user session, object type, identifiers, among others. |
You can perform Copy, Export, and Filter actions on the data through the ribbon.
To copy data, select the cells you want to copy and click Copy in the ribbon;
To export the data, click Export in the ribbon. The spreadsheet will be downloaded in .xlsx format;
To filter the data, click Filters in the ribbon;
Through filters, the user can use compound filters with two criteria connected by logical operators:
Each filter field includes:
| Operator | Description |
|---|---|
| is less than | Returns records with value lower than specified. |
| is less than or equal to | Includes the specified value and lower ones. |
| is greater than | Returns values greater than defined. |
| is greater than or equal to | Includes the specified value and greater ones. |
| contains | Returns records whose content includes the given expression. |
| does not contain | Returns records whose content does not include the given expression. |
| starts with | Returns records whose content starts with the given expression. |
| does not start with | Returns records whose content does not start with the given expression. |
| equals | Exact value. |
| different from | Excludes the given value. |
| is blank | Returns rows with no information in the column. |
| is filled | Returns rows with any value in the cell. |
The table that stores all security audit data is REP_LOG_SECURITY_TRAIL.
All records stored in this table are generated from Actions performed in a Source. The table below describes when each record type is generated:
| Action (dscActionType) + Source (dscInformationType) | Description |
|---|---|
| Insert: | _____________________________________________________________________________________________________________________________________________________________________________________ |
| Insert + Application | When the user creates a new application in T6. |
| Insert + Feature | When new features are enabled in a group, and when users are added to groups with features they did not previously have. |
| Insert + Impersonate | When the user impersonates another user (WF). |
| Insert + Login | When the user logs into T6 successfully, regardless of authentication method. |
| Insert + Logout | When the user logs out of T6. |
| Insert + Permission | When the user enables read and/or write permissions on objects, through groups or directly on the user. |
| Insert + Permissions | When the user performs actions related to permissions and features, such as changing object permissions for a specific user and actions that add features to a user. (WF) |
| Insert + Role | When roles are added, either directly to a user or to a group. |
| Insert + user | When a user creates another user or group in T6. |
| Enter: | _____________________________________________________________________________________________________________________________________________________________________________________ |
| Enter + Impersonate | When the user impersonates another user within T6. |
| Enter + Login | When the user attempts to log into T6 but the credentials are incorrect (username or password). |
| Block: | _____________________________________________________________________________________________________________________________________________________________________________________ |
| Block + User | When a blocked user attempts to access T6. |
| Update: | _____________________________________________________________________________________________________________________________________________________________________________________ |
| Update + Object | When a user creates a new object in Explorer. |
| Update + Application | When a user changes the user profile type in an application. |
| Update + User | When a user changes information of another existing user; a record is also generated when a role is assigned to a user. |
| Update + Permissions | When a user changes permissions of another user (WF). |
| Update + OwnerShip | When a user transfers ownership of an object in T6. |
| Update + Role | When a user makes changes to an existing role in T6. |
| Leave: | _____________________________________________________________________________________________________________________________________________________________________________________ |
| Leave + Impersonate | When an impersonated user logs out and returns to the original user. |
| Create: | _____________________________________________________________________________________________________________________________________________________________________________________ |
| Create + Permission | When permissions are enabled for a user through an application. |
| Create + Object | When a Shortcut object is created. |
| Create + User | - |
| Delete: | _____________________________________________________________________________________________________________________________________________________________________________________ |
| Delete + XML | When the user deletes an XML object (WF). |
| Delete + User | When the user deletes another user in T6 (also generates a record with dscInformationType Object). |
| Delete + Role | When the user deletes a role in T6 (also generates a record with dscInformationType Object). |
| Delete + Object | When the user deletes an object, whether a form, user, group, role, etc. |
| Delete + Application | When the user deletes an application in T6. |
| Remove: | _____________________________________________________________________________________________________________________________________________________________________________________ |
| Remove + User | When a user is removed from a group in T6. |
| Remove + Role | When a role is removed from a user. |
| Remove + Permission | When a user's object permissions are removed. |
| Remove + Feature | When the user removes features from users or groups. |
| Remove + Application | When a user's access to an application is removed. |
| Execute: | _____________________________________________________________________________________________________________________________________________________________________________________ |
| Execute + Service | When a user calls an API using a Service token without needing to be logged in. |
| Send: | _____________________________________________________________________________________________________________________________________________________________________________________ |
| Send + Email | When a password reset email is sent to a user. |
For additional information, visit Log Retention
The Audit Trail functions as a history of changes made to any cell in T6 forms. The audited values refer to the difference between the new value and the old value.
For example:
In a T6 form we have a cell with the value 220, the user changes the cell value to 200 and saves the form. The audited value will be -20.
To view the audit trail, follow these steps:
Within T6, with a form open, select a cell that contains a saved value;
Go to the Tools tab in the ribbon and in the Cells section select
;
A side panel named Audit Trail will open;
The following will be displayed: Date, User, Type, Value, and Sub-Total;
For the tool to function correctly, the audit must be performed on leaf members. If it is performed on an intermediate-level member, only one row will be displayed, showing only the last change made to the cell value.
To view the cell detail audit, follow these steps:
;
again, you will be able to see the current detail of the cell;
;
When adding details, the cell display in the form will be changed, showing a blue icon in the upper-left corner, as shown in the image below:
Through Cell Details, you can mention users using the
@usernamesyntax. When a user is mentioned, they will receive a notification informing them that they were mentioned in a cell detail, and by clicking View in the notification, the user will be redirected to the form and cell where they were mentioned.
If the mentioned user does not have permission to access the form where they were mentioned, when clicking View in the notification, an error message will be displayed.
When clicking Cell Breakdown, a side panel will open, where the selected context is displayed, and just below, a table with the fields Description, Operation, and Value.
Click Save to apply the value changes and close the panel;
When changing the value of a cell using the Cell Breakdown tool, it becomes a calculated cell, preventing changes via the form.
When adding values to a cell via Cell Breakdown, the display will be changed, showing a red icon in the upper-left corner, as shown in the image below:
To view the Data Table Audit, follow these steps:
;
;Only data entered after the Enable Audit flag has been activated in the data table will be shown in the audit. If the selected form contains data entered before the flag was enabled, it will not be possible to view the audit for this data.
Within T6, we also have a history of changes to the structure of an object.
To view it, follow these steps:
As in any large-scale system, sometimes unexpected errors can occur. T6 audits and saves the information that caused these errors, facilitating communication between the client and the support team.
To view the error log page, follow these steps:
In the T6 main menu, go to Settings and select the Log option;
A new page will open in T6 displaying the list of errors;
The listing will show Date, User, Layer, Message;
To view the details, simply double-click on a specific row;
A side panel named Log Administration will open;
It will display the following information:
Allows all changes regarding the structure of the model in T6 to be recorded. Thus, when creating a new dimension or adding a new member to a dimension, these changes are stored.
The entire model structure is saved in XML format.
To access the model history, we will follow these steps:
1. In the main T6 menu, go to Modeling and select the option Model History;
2. A side panel will open named Model History;
3. By default, no record will be displayed until an application is selected;
We will select the desired application through a dropdown, as well as the type of record, which by default shows All Records;
4. If you want only a specific type of records from an application to be displayed, it is possible to select through the Application and Type dropdowns;
5. The listing displays:
Code: Code generated when performing an insertion;
Type: In type we have the name of the dimension, or Cube;
User: Displays the user who performed the insertion;
Application: The T6 application;
Creation: Displays the Date and Time when the insertion occurred;
Status: Displays the status of the insertion, there are 3 possible statuses:
next to its name in the listing; We can also delete all historical records at once by clicking
located above the listing;
to undo the changes;
We can download a specific record by clicking
next to its name in the listing. When clicking export, a file in .XML format will be downloaded;
Auditing consists of storing details about changes and/or actions performed on any data considered critical within the T6 solution, such as changes on the Security screen or value changes in form cells.
To access the security audit, the user must belong to a Global Group with the Security Audit feature enabled.
T6 provides 9 audit types:
To enable security auditing, follow these steps:
To view security audit logs:
A new window will open with a spreadsheet containing the records.
To view a cell change history:
In the audit trail, the displayed value represents the difference between the old value and the new cell value.
For example, if a cell changed from 220 to 200, the audited value will be -20.
For auditing to work correctly, it must be performed on leaf members.
In some cases, auditing can be used on intermediate-level members, but only the last change will be displayed.
Yes. In the Cell Details panel, click the history icon to view all detail changes.
To enable auditing for data tables, during data table creation or editing, enable the Enable Audit flag.
No. You must open the data table edit screen and enable auditing before inserting data. Only data inserted after enabling the "Enable Audit" flag will be audited.
To view object history:
A side panel will open showing the change date and the user responsible for the change.
To access system error logs:
A new window will open with the error list, including date, user, layer, and message details.
To access model history:
A side panel will open showing the history of model structural changes, such as dimension and member creation.
Yes, you can copy selected data or export the whole spreadsheet in .xlsx format from the ribbon by clicking Export.
After clicking export, the download starts automatically.
To apply filters to audit data:
Available logical operators:
Available comparison types: