Jump to: navigation, search

In the Column List:

  • P = Primary key
  • M = Mandatory field
  • F = Foreign key (where the term is used loosely to indicate a surrogate key reference to a field in another table, not a formal constraint)
  • DV = Default value
  • In the Data Type column, varchar/nvarchar means that the data type is varchar except in multi-language databases that use Unicode, in which case the data type is nvarchar. (The Info Mart database in Cloud deployments is not multi-language.)

Table INTERACTION_DESCRIPTOR

Description

Modified: 8.5.010 (in Microsoft SQL Server, data type for the following columns modified in single- and multi-language databases: CUSTOMER_SEGMENT, SERVICE_TYPE, SERVICE_SUBTYPE, BUSINESS_RESULT); 8.5.003 (in Oracle, fields with VARCHAR data types use explicit CHAR character-length semantics)

In partitioned databases, this table is not partitioned.


This table allows interaction facts to be described by deployment-specific business attributes that characterize the interaction, such as service type, service subtype, customer segment, and business result. Because the business attribute values may change over the lifetime of an interaction, each interaction resource fact has an interaction descriptor that snapshots the current value of the attributes.

Each row in this table describes a distinct combination of business attributes that characterize the interaction. A new row is issued for each distinct combination of business attributes. The values are populated from the user data (attached data or UserEvent-based KVP data) according to a propagation rule, configurable for each column.

Important
Although the maximum length of the underlying IDB fields is 255 characters, Genesys Info Mart restricts the maximum length of the fields related to user data KVPs in this dimension table to 170 for RDBMSs other than Oracle. Refer to the RDBMS Considerations on the User Data Mapping page in the Genesys Info Mart Deployment Guide for more information.
Tip
To assist you in preparing supplementary documentation, click the following link to download a comma-separated text file containing information such as the data types and descriptions for all columns in this table: Download a CSV file.

Hint: For easiest viewing, open the downloaded CSV file in Excel and adjust settings for column widths, text wrapping, and so on as desired. Depending on your browser and other system settings, you might need to save the file to your desktop first.

Column List

Legend

Column Data Type P M F DV

INTERACTION_DESCRIPTOR_KEY

int X X

TENANT_KEY

int X X

CREATE_AUDIT_KEY

numeric(19) X X

CUSTOMER_SEGMENT

nvarchar(170) X DEFAULT_CUSTOMER_SEGMENT

SERVICE_TYPE

nvarchar(170) X DEFAULT_SERVICE_TYPE

SERVICE_SUBTYPE

nvarchar(170) X DEFAULT_SERVICE_SUBTYPE

BUSINESS_RESULT

nvarchar(170) X DEFAULT_BUSINESS_RESULT

PURGE_FLAG

numeric(1)

INTERACTION_DESCRIPTOR_KEY

The primary key of this table and the surrogate key that is used to join this dimension table to the fact tables.

TENANT_KEY

The surrogate key that is used to join the TENANT dimension to the fact tables, to indicate the tenant of the IRF resource. The value of this field is identical to the value in the corresponding INTERACTION_RESOURCE_FACT record. This value can be used to restrict data access.

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.

CUSTOMER_SEGMENT

Modified: 8.5.010 (in Microsoft SQL Server, data type modified in single- and multi-language databases)
The value of a customer, relative to a business line. For example, customers can be categorized according to maximum spending limit, such as platinum, gold, and silver; similarly, for service-related transactions, they could be categorized according to the service package that they have bought. The default value, DEFAULT_CUSTOMER_SEGMENT, is the same as the default value populated for the CUSTOMER_SEGMENT KVP in the CTL_UD_TO_UDE_MAPPING table.

SERVICE_TYPE

Modified: 8.5.010 (in Microsoft SQL Server, data type modified in single- and multi-language databases)
The service that is being requested by the customer. It can be used to categorize interactions according to their product or service offering. The default value, DEFAULT_SERVICE_TYPE, is the same as the default value populated for the SERVICE_TYPE KVP in the CTL_UD_TO_UDE_MAPPING table.

SERVICE_SUBTYPE

Modified: 8.5.010 (in Microsoft SQL Server, data type modified in single- and multi-language databases)
The detailed type of service that is being requested by the customer. It can be used to categorize interactions according to particular product or service requests. The default value, DEFAULT_SERVICE_SUBTYPE, is the same as the default value populated for the SERVICE_SUBTYPE KVP in the CTL_UD_TO_UDE_MAPPING table.

BUSINESS_RESULT

Modified: 8.5.010 (in Microsoft SQL Server, data type modified in single- and multi-language databases)
The result of the interaction, from a business perspective; for example, the interaction resulted in a sale or in a new customer account being opened. The default value, DEFAULT_BUSINESS_RESULT, is the same as the default value populated for the BUSINESS_RESULT KVP in the CTL_UD_TO_UDE_MAPPING table.

PURGE_FLAG

This field is reserved.


Index List

CODE U C Description

I_INTERACTION_DESCRIPTOR

X Ensures that the combinations of values that are stored in the dimension table for each tenant are unique.

Index I_INTERACTION_DESCRIPTOR

Field Sort Comment
TENANT_KEY Ascending
CUSTOMER_SEGMENT Ascending
SERVICE_TYPE Ascending
SERVICE_SUBTYPE Ascending
BUSINESS_RESULT Ascending

Subject Areas

  • Interaction - Represents interactions from the perspective of a customer experience.
  • Interaction_Resource - Represents a summary of each attempt to handle an interaction. It encompasses the mediation process that is required to offer the interaction to a target handling resource, as well as the activities of that target handling resource.

 

 

 

 

 

 

 

 

 

 

 

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on August 10, 2017, at 05:42.