Jump to: navigation, search

partitioning-interval-size-gidb-ocs

Section: gim-etl
Default Value: 86400 or partitioning-interval-size-gidb
Valid Values: Any positive integer
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Introduced: 8.1.402.07

Specifies the size of partitions, in seconds, for partitioned GIDB tables that store Outbound Contact–related data. When this option is set, Job_MaintainGIM creates partitions of the specified size in the Info Mart database in preparation for future ETL cycles. If the option is not specified, the value of partitioning-interval-size-gidb, which has a default value of 24 hours (86400 seconds), is used.

In PostgreSQL deployments, Genesys recommends setting the size of GIDB table partitions to one week (604800 seconds).

partitioning-interval-size-gidb-mm

Section: gim-etl
Default Value: 86400 or partitioning-interval-size-gidb
Valid Values: Any positive integer
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Introduced: 8.1.402.07

Specifies the size of partitions, in seconds, for partitioned GIDB tables that store multimedia interaction data. When this option is set, Job_MaintainGIM creates partitions of the specified size in the Info Mart database in preparation for future ETL cycles. If the option is not specified, the value of partitioning-interval-size-gidb, which has a default value of 24 hours (86400 seconds), is used. Genesys recommends increasing the size of GIDB partitions for multimedia interactions, which typically live longer than voice interactions but generate a smaller volume of data.

In PostgreSQL deployments, Genesys recommends setting the size of GIDB table partitions to one week (604800 seconds).

Active Switching Matrix

Also known as ASM. An active component of switching hubs that rapidly switch packets from port to port by allocating memory.



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

populate-mm-ixnqueue-facts

Section: gim-etl-populate
Default Value: false
Valid Values: true, false
Changes Take Effect: On the next ETL cycle
Dependencies: None

Enables or disables the population of eServices/Multimedia Interaction Queue activity to the MSF table. Genesys Info Mart uses this value for all configured eServices/Multimedia Interaction Queues, unless you configure an option that has the same name on an individual Script object for a specific Interaction Queue in the interface you use for configuration.

  • false—The placement of an interaction in an Interaction Queue will not be represented in the MSF table.
  • true—The placement of an interaction in an Interaction Queue will be represented in the MSF table.

Starting with release 8.5.003, Genesys Info Mart always creates an MSF record for the first Interaction Queue that an inbound interaction enters, regardless of the setting of this option.

populate-thread-facts

Section: gim-etl-populate
Default Value: false
Valid Values: true, false
Changes Take Effect: At the next run of Job_TransformGIM
Dependencies: None
Introduced: 8.5.001

Enables or disables the population of thread-related metrics in the ANCHOR_FLAGS dimension in multimedia deployments.

(Cleaning up for GIM Iteration 11)
Line 21: Line 21:
 
* [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-BGS_BOT_NAME_DIM:{{PONYDOCSVERSION}}|BGS_ BOT_NAME_DIM]]}}</li>
 
* [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-BGS_BOT_NAME_DIM:{{PONYDOCSVERSION}}|BGS_ BOT_NAME_DIM]]}}</li>
 
<li>The START_DATE_TIME_KEY in the [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-GPM_FACT:{{PONYDOCSVERSION}}#START_DATE_TIME_KEY|GPM_FACT]] table was made part of the composite primary key, even in nonpartitioned databases.</li>
 
<li>The START_DATE_TIME_KEY in the [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-GPM_FACT:{{PONYDOCSVERSION}}#START_DATE_TIME_KEY|GPM_FACT]] table was made part of the composite primary key, even in nonpartitioned databases.</li>
−
<li>To cover support for employee GDPR requests introduced in release 8.5.010.16, the descriptions of the [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-CTL_GDPR_HISTORY:{{PONYDOCSVERSION}}|CTL_GDPR_HISTORY]] table and columns have been extended.</li>
+
<li>To cover support for employee General Data Protection Regulation (GDPR) requests introduced in release 8.5.010.16, the descriptions of the [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-CTL_GDPR_HISTORY:{{PONYDOCSVERSION}}|CTL_GDPR_HISTORY]] table and columns have been extended.</li>
 
<li>The UPDATE_AUDIT_KEY column was added to the following tables in release 8.5.010.16:
 
<li>The UPDATE_AUDIT_KEY column was added to the following tables in release 8.5.010.16:
 
{{ColumnFormat|cols=3|content=
 
{{ColumnFormat|cols=3|content=
Line 34: Line 34:
 
}}
 
}}
 
}}</li>
 
}}</li>
−
<li>To support General Data Protection Regulation (GDPR) compliance, a description of the [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-CTL_GDPR_HISTORY:{{PONYDOCSVERSION}}|CTL_GDPR_HISTORY]] table has been added.</li>
+
<li>To support GDPR compliance, a description of the [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-CTL_GDPR_HISTORY:{{PONYDOCSVERSION}}|CTL_GDPR_HISTORY]] table has been added.</li>
 
<li>For support of alternative data streams:
 
<li>For support of alternative data streams:
 
<ul>
 
<ul>

Revision as of 13:15, June 11, 2018

What's New in the Documentation

The following information is new or has changed significantly since earlier versions of this document. The most recent changes appear first.

Comments or questions about this documentation? Contact us for support!