Allows facts to be described based on attributes of a tenant. The TENANT dimension is used in a multi-tenant deployment to filter facts and dimensions into tenant-specific views--allowing each tenant to see only their own data. In a single-tenant deployment, the Resources tenant is considered a tenant. In a multi-tenant deployment, the Environment tenant and the configured tenants are considered tenants.
Each row describes one tenant. A new row is issued for each configured tenant, identified by its ID in the contact center configuration. Changing a tenant's name causes an update to the existing row. Deleting a tenant and re-creating it under the same name causes a new row to be issued.
This view is based on the GIDB_GC_TENANT table.
|TENANT_KEY||The primary key of this view and the surrogate key that is used to join the TENANT dimension to the fact tables.|
|TENANT_NAME||The tenant name.|
|TENANT_CFG_DBID||The tenant object identifier in the contact center configuration.|
|START_TS||The UTC-equivalent value of the date and time when the tenant was added to IDB, which may differ from when the tenant was actually added to contact center configuration.|
|END_TS||The UTC-equivalent value of the date and time when the tenant was removed from contact center configuration.|
|CREATE_AUDIT_KEY||The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify newly added data.|
|UPDATE_AUDIT_KEY||The surrogate key used to join to the CTL_AUDIT_LOG dimension. Specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools — that is, applications that need to identify recently modified data.|