ComplianceTenantSettingHistory Table

The ComplianceTenantSettingHistory table records changes to many tenant settings. This table has a series of ID columns, any one (or sometimes more) of which may be set to associate the history with a particular item. These ID columns don’t have foreign keys to other tables. This allows us to retain history of deleted objects in order to maintain an audit trail (as yet, there is no UI around this information), and also to improve performance when deleting objects.

Note: To cater for multi-tenant mode, this table may contain data for multiple tenants. Access requires that the database TenantID has been set in the SQL Server connection context information. That setting filters an underlying table to produce this view of data for the single, selected tenant.
Table 1. Database columns for ComplianceTenantSettingHistory table

Database Column

Details

ComplianceTenant SettingHistoryID

Type: big integer. Key. Generated ID

Unique identifier for a history record.

ComplianceOperatorID

Type: integer. Nullable

ID from the ComplianceOperator table

SettingNameID

Type: integer. Nullable

The setting ID that has been updated.

AvailablePackageID

Type: integer. Nullable

The package ID that has been updated.

FieldName

Type: text (max 256 characters). Nullable

The field name that has been updated. Foreign key to the ComplianceResourceString table.

OldValue

Type: text (max 4000 characters). Nullable

Typically the value before the change, although at times, when multiple pieces of information are required to identify the action taking place, this field may store other supporting information. For example, when an operator is granted rights to access a contract, this field stores the type of access (such as “Normal” or “Administrator”) while the NewValue field stores the name of the contract.

NewValue

Type: text (max 4000 characters). Nullable

Typically the value after the change, although refer to the above definition of the OldValue column for a description of extenuating circumstances.

ValuesAreResourceStrings

Type: boolean

Set this field to True if the old and new values should be looked up as resource strings.

ComplianceHistoryTypeID

Type: integer

Foreign key to the HistoryType table.

HistoryDate

Type: datetime

The date of the change.

Comments

Type: text (max 2000 characters). Nullable

Comments recorded about the change after it was made.