Documentation:GIM:Library:TenantViews:8.5DRAFT

Genesys Info Mart Tenant User Schema and Tenant Views

A Genesys-provided script, named make_gim_view_for_tenant.sql, is used to create views to access data in the Genesys Info Mart fact and dimension tables.

The views are created in:

• Genesys Info Mart database schema, in both multi-tenant and single-tenant environments
• Tenant User database schema, in a multi-tenant environment

In a multi-tenant environment, the two types of views can be used in combination.

Views in the Genesys Info Mart Database Schema

The purpose of these views (referred to as tenant-specific views in the Genesys Info Mart Data Organization and Tenant Views diagram) is to provide read-only access to data in the Genesys Info Mart database schema for tenant users who are working only with the data for a particular tenant. A separate set of views is created for each particular tenant. When the tenant administrator creates these views by using the make_gim_view_for_tenant.sql script, the script generates the names for created views.

Multi-tenant deployment applications should query Genesys Info Mart data by using these read-only views, instead of querying the tables and views that reside in the Genesys Info Mart database schema.

To restrict data access in single-tenant deployments, use the same script to create a similar set of read-only views. The data organization for the Tenant User that is shown in the Genesys Info Mart Data Organization and Tenant Views diagram is applicable to single-tenant deployments in which data-access views are created.

Views in the Tenant User Database Schema

These views (shown within the Tenant User database schema in Genesys Info Mart Data Organization and Tenant Views) can be used to make data access more specific to the needs of a particular tenant user. The tenant administrator creates these views in a separate Tenant User database schema by using the same make_gim_view_for_tenant.sql script.

Writer's note: The following information was formerly on Tenant User Database Schema page, which will be deleted.

In addition to the Genesys Info Mart database schema, Genesys Info Mart supplies a script to create a separate database schema for each tenant, so that each tenant user can access only its tenant’s data. Because each tenant’s data is exposed through a different database schema, tenant administrators can control user access to tenant-specific data.

Each Tenant User database schema contains:

• Dimension views
• Fact views

End of deleted page content

The structure of the views created in the Tenant User database schema is identical to that of their underlying dimension and fact tables or views in the Genesys Info Mart database schema. For this reason, subject area diagrams and descriptions for the Tenant User views are not provided in this document.

A Tenant User database schema contains the following views, as well as additional views that are created for custom user data tables:

Writer's note: The following list was copied directly from the 8.1 PDF source when the PDM was converted to wiki, and the list was probably already out of date at that time -- e.g., shouldn't it include GROUP_ANNEX and RESOURCE_ANNEX, as well as CALLBACK, SDR, etc. tables?

• ANCHOR_FLAGS
• ATTEMPT_DISPOSITION
• CALLING_LIST_METRIC_FACT
• CALLING_LIST_TO_CAMP_FACT_
• CALL_RESULT
• CAMPAIGN_GROUP_SESSION_FACT
• CAMPAIGN_GROUP_STATE
• CAMPAIGN_GROUP_STATE_FACT
• CONTACT_ATTEMPT_FACT
• CONTACT_INFO_TYPE
• DATE_TIME
• DIALING_MODE
• GROUP_TO_CAMPAIGN_FACT_
• INTERACTION_DESCRIPTOR
• INTERACTION_FACT
• INTERACTION_RESOURCE_FACT
• INTERACTION_RESOURCE_STATE
• INTERACTION_TYPE
• IRF_USER_DATA_GEN_1
• IRF_USER_DATA_KEYS
• IXN_RESOURCE_STATE_FACT
• MEDIATION_SEGMENT_FACT
• MEDIA_TYPE
• PLACE_GROUP_FACT_
• RECORD_FIELD_GROUP_1
• RECORD_FIELD_GROUP_2
• RECORD_STATUS
• RECORD_TYPE
• REQUESTED_SKILL
• REQUESTED_SKILL_COMBINATION
• RESOURCE_
• RESOURCE_GROUP_COMBINATION
• RESOURCE_GROUP_FACT_
• RESOURCE_SKILL_FACT_
• RESOURCE_STATE
• RESOURCE_STATE_REASON
• ROUTING_TARGET
• SM_RES_SESSION_FACT
• SM_RES_STATE_FACT
• SM_RES_STATE_REASON_FACT
• STRATEGY
• TECHNICAL_DESCRIPTOR
• TIME_ZONE
• CALLING_LIST
• CALLING_LIST_TO_CAMP_FACT
• CAMPAIGN
• GROUP_
• GROUP_TO_CAMPAIGN_FACT
• PLACE
• PLACE_GROUP_FACT
• RESOURCE_GROUP_FACT
• RESOURCE_SKILL_FACT
• SKILL
• TENANT
• WORKBIN

Writer's note: The following info has basically been copied from the Dep Guide Completing Database Preparation page.

Each Tenant User schema has a view on a single DATE_TIME table, so each schema supports a single time zone. Genesys Info Mart supports creating table views for more than one tenant in the same Tenant User schema. This functionality simplifies deployment of the reporting solution.

The following Figure illustrates how the tenant-specific, read-only Genesys Info Mart Views function in a Genesys Info Mart deployment. The diagram shows a Tenant User schema that contains table views for only one tenant.

Multi-Tenant Filtered Views or Single-Tenant Read-Only View

Reports in multiple time zones

To provide reports in multiple time zones, the downstream report developer must use a separate Tenant User schema for each time zone. However, the Tenant Admin does not need to create a separate Tenant User schema for each combination of time zone and tenant. Instead, the Tenant Admin can include all tenants, or a group of tenants, in a single schema per time zone.

End of copied DG content