IRF_USER_DATA_GEN_1 - This table is provided with the default schema to store Genesys-defined, high-cardinality KVPs, such as case ID and customer ID.
INTERACTION_DESCRIPTOR - This table is provided with the default schema to store Genesys-defined, low-cardinality KVPs, such as service type and customer segment.
The following dimension, fact, and fact extension tables store user data: Customer segment, service type, and service subtype are good examples of low-cardinality user data.
Low-cardinality user data refers to data that has a limited range of possible values there may be multiple values of a specific type for a single interaction.
A Customer ID number is an example of high-cardinality user data.
High-cardinality user data refers to data for which there can be a very large number of possible values.
The target table for storage of user data depends on whether the user-data key name is predefined or custom, and whether the value is of high or low cardinality. The following tables facilitate user-data processing: Because the same logic is used to process these two types of data, they are collectively referred to as user data.Ī customizable database schema enables you to treat each key-value pair (KVP) field as either a fact or a dimension and to store user-data KVPs in fact and dimension tables. A unified processing mechanism extracts deployment-specific business attributes from both call-based TEvents or Multimedia reporting protocol events (data that is attached by T-Server or Interaction Server, respectively) and EventUserEvents or EventCustomReporting events (data that is attached by other Genesys applications). This data allows interaction resource facts (IRFs) and, starting with release 8.1.2, mediation segment facts (MSFs) to be described by deployment-specific business attributes that characterize the interaction, such as service type and customer segment. Genesys Info Mart provides both predefined and custom tables, to store user data supplied with interactions. The fact and dimension tables are depicted in the “Info Mart Database Owner/Schema” portion of the following diagram. For more information, see Temporary Tables. For more information, see Info Mart Service and Control Tables.Īll temporary (TMP_*) tables are intended for internal purposes only. Most staging (STG_*) tables are intended for internal purposes only, with the exception of two tables that are useful for troubleshooting errors in the source data that cause ETL jobs to either generate exceptions or fail. They provide temporary storage for those interaction records that may be subject to the merge process. Merge tables within the Info Mart database are intended for internal purposes only. Genesys Info Mart further processes (transforms) GIDB data to create data representations useful for end-user reports. This part of the Info Mart database is designed to keep all records that are extracted from various IDBs and subsequently merged, so that coherent reporting data at the lowest level of detail is gathered from the entire contact center and stored within a single data warehouse for as long as customers require detailed data. GIDB stands for Global Interaction Database. For more information, see Info Mart Service and Control Tables. Whereas most control (service) tables are intended for internal purposes, certain CTL_* tables contain operational data that is helpful to system integrators and system administrators in their data validation and troubleshooting tasks. For a discussion of dimension views, see Dimension Views. ImportantGenesys Info Mart database schema includes a set of dimension views, in addition to dimension tables.