(Created target blank page For Version: PSAAS:Public) |
(Update with the copy of version: 8.5.0) |
||
Line 1: | Line 1: | ||
− | < | + | = View TENANT = |
+ | |||
+ | <onlyinclude> | ||
+ | |||
+ | |||
+ | {{PDMView | ||
+ | |viewName = TENANT | ||
+ | |shortDesc = 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. | ||
+ | |viewDesc = 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. | ||
+ | |introduced = | ||
+ | |SQL = <source lang="xml" enclose="div">select | ||
+ | ID as TENANT_KEY, | ||
+ | NAME as TENANT_NAME, | ||
+ | ID as TENANT_CFG_DBID, | ||
+ | CREATED_TS as START_TS, | ||
+ | DELETED_TS as END_TS, | ||
+ | CREATE_AUDIT_KEY as CREATE_AUDIT_KEY, | ||
+ | UPDATE_AUDIT_KEY as UPDATE_AUDIT_KEY | ||
+ | from | ||
+ | GIDB_GC_TENANT | ||
+ | UNION ALL | ||
+ | SELECT - 1 AS TENANT_KEY, | ||
+ | 'UNKNOWN' AS TENANT_NAME, | ||
+ | - 1 AS TENANT_CFG_DBID, | ||
+ | -1 AS START_TS, | ||
+ | -1 AS END_TS, | ||
+ | -1 AS CREATE_AUDIT_KEY, | ||
+ | -1 AS UPDATE_AUDIT_KEY | ||
+ | FROM dual | ||
+ | UNION ALL | ||
+ | SELECT - 2 AS TENANT_KEY, | ||
+ | 'NO_VALUE' AS TENANT_NAME, | ||
+ | - 1 AS TENANT_CFG_DBID, | ||
+ | -1 AS START_TS, | ||
+ | -1 AS END_TS, | ||
+ | -1 AS CREATE_AUDIT_KEY, | ||
+ | -1 AS UPDATE_AUDIT_KEY | ||
+ | FROM dual | ||
+ | |||
+ | </source> | ||
+ | }} | ||
+ | |||
+ | {{PDMViewColumn | ||
+ | |colName = TENANT_KEY | ||
+ | |colDesc = The primary key of this view and the surrogate key that is used to join the TENANT dimension to the fact tables. | ||
+ | }} | ||
+ | |||
+ | {{PDMViewColumn | ||
+ | |colName = TENANT_NAME | ||
+ | |colDesc = The tenant name. | ||
+ | }} | ||
+ | |||
+ | {{PDMViewColumn | ||
+ | |colName = TENANT_CFG_DBID | ||
+ | |colDesc = The tenant object identifier in the contact center configuration. | ||
+ | }} | ||
+ | |||
+ | {{PDMViewColumn | ||
+ | |colName = START_TS | ||
+ | |colDesc = 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. | ||
+ | }} | ||
+ | |||
+ | {{PDMViewColumn | ||
+ | |colName = END_TS | ||
+ | |colDesc = The UTC-equivalent value of the date and time when the tenant was removed from contact center configuration. | ||
+ | }} | ||
+ | |||
+ | {{PDMViewColumn | ||
+ | |colName = CREATE_AUDIT_KEY | ||
+ | |colDesc = 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. | ||
+ | }} | ||
+ | |||
+ | {{PDMViewColumn | ||
+ | |colName = UPDATE_AUDIT_KEY | ||
+ | |colDesc = 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. | ||
+ | }} | ||
+ | |||
+ | {{PDMRef | ||
+ | |parentView = TENANT | ||
+ | |foreignKey = TENANT_KEY | ||
+ | }} | ||
+ | |||
+ | {{PDMRef | ||
+ | |parentTable = CTL_AUDIT_LOG | ||
+ | |foreignKey = CREATE_AUDIT_KEY | ||
+ | }} | ||
+ | |||
+ | {{PDMRef | ||
+ | |parentTable = CTL_AUDIT_LOG | ||
+ | |foreignKey = UPDATE_AUDIT_KEY | ||
+ | }} | ||
+ | |||
+ | |||
+ | </onlyinclude> | ||
+ | |||
+ | [[Category:V:PSAAS:Public]] |
Revision as of 13:44, August 10, 2017
View TENANT
Description
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.
Column List
Column | Description |
---|---|
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. |
Comments or questions about this documentation? Contact us for support!