tiCrypt

System Settings History

Prerequisites

User Role:

Super-admin

System Settings History is the Management table that records every change saved in System Settings: who changed which setting, when, and the value before and after. It is a record only; you cannot undo a change from here. To restore an earlier value, read it from the history and save it again in System Settings.

Who can use it. The System Settings History item appears only for Super-admins, and the backend returns the history only to Super-admins. No permission changes that.

What it records. One entry for each successful save in System Settings, made by the backend when it stores the value. It does not record:

• saves the backend refused. Those, like successful saves, appear in Audit Logs with the type GIWR;
• changes to Custom Fields, which are stored apart from system settings. Their saves appear in Audit Logs with the type GSEW;
• changes made by editing the deployment file.

The following table describes the columns of the System Settings History table. The table opens sorted by Timestamp, oldest first. Click the Timestamp header to list the newest change first.

Column	Description
User	The user who saved the change.
Timestamp	When the change was saved.
Field	The deployment file key of the setting, such as lockSessionTimeout. See Deployment File Keys for the setting behind each key.
Old Value	The value before the change, with a copy button. A setting made of several values shows as JSON.
New Value	The value after the change, shown the same way.

The table has no actions on the selected rows other than View and the exports.

Reading the values

• The first save of a setting shows {} as the old value: nothing had been saved in System Settings before, and the value in use came from the deployment file or the default.
• An empty value in the table, shown as "No previous value (null)" or "No new value (null)" in the detail pane, means the setting was saved with no value. The deployment file's value, or the default, applied after that change (see Saved Values and the Deployment File).
• Login Message stores its expiration as a number of milliseconds since 1 January 1970, and Terms of Service stores its frequency (interval) in seconds and its last text change (updated) in milliseconds.
• The copy buttons copy the full value, as valid JSON for a setting made of several values.

Access System Settings History

1. Go to the Management icon in the top left taskbar.
2. Navigate to the Settings section.
3. Click the System Settings History in the left panel.

View Deployment History of a System Setting

1. Go to the Management icon in the top left taskbar.
2. Navigate to the Settings section.
3. Click the System Settings History in the left panel.
4. Select the change to view.
5. Click the View button in the top right panel.
6. In the detail pane header, view "<setting> change" and "Changed by <user> on <date>".
7. Under Change Information, view the Field, Changed by (click it to open the user), Timestamp and Record ID.
8. Under Previous Value, view the value before the change. A setting saved with no value shows "No previous value (null)".
9. Under New Value, view the value after the change. A setting saved with no value shows "No new value (null)". A setting made of several values shows in a JSON viewer.
10. Once done, click Close in the top panel.

Result: The detail pane shows one saved change of a system setting.

note

The detail pane names the setting as System Settings does, such as Session Timeout, where the table shows its key, such as lockSessionTimeout. A key that System Settings no longer offers, such as externalView (External File Preview), still shows under its old name.

Restore an Earlier Value of a System Setting

1. Go to the Management icon in the top left taskbar.
2. Navigate to the Settings section.
3. Click the System Settings History in the left panel.
4. In the Field column, filter for the key of the setting, such as lockSessionTimeout.
5. Select the change that set the value you want back, and click the View button in the top right panel.
6. Read the value under New Value.
7. Open System Settings, select the setting, enter that value and click Save.

Result: The setting has its earlier value again, and the restore appears as a new entry in the history.

tip

• To find which value was in use at a given time, look for the last change of that key before that time. If there is none, the value came from the deployment file or the default.
• An old value of {} means the deployment file or the default was in use. To go back to it, save the setting with no value where System Settings allows it (see Saved Values and the Deployment File); otherwise enter the deployment file's value.
• Saving requires the permission Change system settings.

Refresh System Setting(s) History

bulk-action

1. Go to the Management icon in the top left taskbar.
2. Navigate to the Settings section.
3. Click the System Settings History in the left panel.
4. Click the Refresh button in the top right panel.

Result: The table shows the changes saved since it last loaded, including changes other administrators saved.

Export System Setting(s) History in CSV Format

bulk-action

1. Go to the Management icon in the top left taskbar.
2. Navigate to the Settings section.
3. Click the System Settings History in the left panel.
4. Select the system setting(s) to export in CSV format.
5. Click the Export CSV button in the top right panel.
6. Select Selected items.
7. In the local window, click Save.

Export System Setting(s) History in JSON Format

bulk-action

1. Go to the Management icon in the top left taskbar.
2. Navigate to the Settings section.
3. Click the System Settings History in the left panel.
4. Select the system setting(s) to export in JSON format.
5. Click the Export JSON button in the top right panel.
6. Select Export selected items.
7. In the local window, click Save.

tip

Click View Selected Items before exporting to view the system settings as a table in JSON format.

Related

• System Settings: where the changes listed here are saved, and what each setting does.
• Deployment File Keys: the setting behind each key in the Field column.
• Audit Logs: every save attempt, including refused ones, as GIWR lines.