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.

Line 19: Line 19:
 
<li>A new column, [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-CTL_TRANSFORM_HISTORY:{{PONYDOCSVERSION}}#HWM_VALUE2|HWM_VALUE2]] has been added to the [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-CTL_TRANSFORM_HISTORY:{{PONYDOCSVERSION}}|CTL_TRANSFORM_HISTORY]] table. The [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-CTL_TRANSFORM_HISTORY:{{PONYDOCSVERSION}}#AUDIT_KEY|AUDIT_KEY]] column was added in a previous release.</li>  {{#switch:{{#explode:{{FULLPAGENAME}}|:|2}}
 
<li>A new column, [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-CTL_TRANSFORM_HISTORY:{{PONYDOCSVERSION}}#HWM_VALUE2|HWM_VALUE2]] has been added to the [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-CTL_TRANSFORM_HISTORY:{{PONYDOCSVERSION}}|CTL_TRANSFORM_HISTORY]] table. The [[Documentation:{{PONYDOCSPRODUCTSHORT}}:{{#explode:{{FULLPAGENAME}}|:|2}}:Table-CTL_TRANSFORM_HISTORY:{{PONYDOCSVERSION}}#AUDIT_KEY|AUDIT_KEY]] column was added in a previous release.</li>  {{#switch:{{#explode:{{FULLPAGENAME}}|:|2}}
 
|PDMMS|RPRT|Library=
 
|PDMMS|RPRT|Library=
−
<li>In Microsoft SQL Server deployments, data types for various columns in a number of dimensions were changed in release 8.5.010. Expand the toggle to see a table that summarizes whether the changes occurred only in single-language databases (varchar columns changed to nvarchar), only in multi-language databases (varchar columns changed to nvarchar, or the sizes of existing nvarchar columns changed), or in both. For full details, see the respective table and column descriptions.
+
<li>In Microsoft SQL Server deployments, data types for various columns in a number of dimensions were changed in release 8.5.010. Expand the toggle to see a table that summarizes whether the changes occurred only in single-language databases (<tt>varchar</tt> columns changed to <tt>nvarchar</tt>), only in multi-language databases (<tt>varchar</tt> columns changed to <tt>nvarchar</tt>, or the sizes of existing <tt>nvarchar</tt> columns changed), or in both. For full details, see the respective table and column descriptions.
  
 
{{AnchorDiv|GIM-11801}}
 
{{AnchorDiv|GIM-11801}}
Line 36: Line 36:
 
</ul></li>{{#switch:{{#explode:{{FULLPAGENAME}}|:|2}}
 
</ul></li>{{#switch:{{#explode:{{FULLPAGENAME}}|:|2}}
 
|Library|PDMMS=
 
|Library|PDMMS=
−
<li>{{Editgrn_open}}<font color=red>'''Writer's note:''' This bullet and the next will display only in the MSSQL PDM. '''Borys,''' please esp. confirm this item -- see the writer's note in the column description.</font>{{Editgrn_close}}<br/>
+
<li>In Microsoft SQL Server deployments with multi-language databases, data types for columns changed:
−
In the [[Documentation:GIM:{{PONYDOCSMANUALSHORT}}:Table-SDR_SURVEY_FACT:{{PONYDOCSVERSION}}|SDR_SURVEY_FACT table]], the data type for the [[Documentation:GIM:{{PONYDOCSMANUALSHORT}}:Table-SDR_SURVEY_FACT:{{PONYDOCSVERSION}}#INTERACTION_ID|INTERACTION_ID]] column in multi-language databases has been corrected from <tt>varchar(50)</tt> to <tt>nvarchar(50)</tt>.</li>
 
−
|#default=}} {{#switch:{{#explode:{{FULLPAGENAME}}|:|2}}
 
−
|PDMMS|RPRT|Library=
 
−
<li>In Microsoft SQL Server deployments with multi-language databases, data types for the following columns changed:
 
 
<ul>
 
<ul>
−
<li>From <tt>nvarchar(64)</tt> to <tt>varchar(64)</tt> in table CALLBACK_FACT, columns ORIGINATION_IXN_ID, FIRST_OUT_IXN_ID, LAST_OUT_IXN_ID, and ORS_SESSION_ID </li>
+
<li>From <tt>nvarchar</tt> to <tt>varchar</tt> in tables [[Documentation:GIM:{{PONYDOCSMANUALSHORT}}:Table-CALLBACK_FACT:{{PONYDOCSVERSION}}|CALLBACK_FACT]], [[Documentation:GIM:{{PONYDOCSMANUALSHORT}}:Table-GPM_FACT:{{PONYDOCSVERSION}}|GPM_FACT]], [[Documentation:GIM:{{PONYDOCSMANUALSHORT}}:Table-SDR_ACTIVITIES_FACT:{{PONYDOCSVERSION}}|SDR_ACTIVITIES_FACT]], [[Documentation:GIM:{{PONYDOCSMANUALSHORT}}:Table-SDR_SURVEY_FACT:{{PONYDOCSVERSION}}|SDR_SURVEY_FACT]], and [[Documentation:GIM:{{PONYDOCSMANUALSHORT}}:Table-SDR_SURVEY_TRANSCRIPT_FACT:{{PONYDOCSVERSION}}|SDR_SURVEY_TRANSCRIPT_FACT]]. See the table descriptions for details.</li>
−
<li>From <tt>varchar(512)</tt> to <tt>nvarchar(512)</tt> in table SDR_USER_INPUTS_FACT, columns UTTERANCE and INTERPRETATION</li>  
+
<li>From <tt>varchar</tt> to <tt>nvarchar</tt> in table [[Documentation:GIM:{{PONYDOCSMANUALSHORT}}:Table-SDR_USER_INPUTS_FACT:{{PONYDOCSVERSION}}|SDR_USER_INPUTS_FACT]], columns UTTERANCE and INTERPRETATION.</li>  
 
</ul></li>|#default=}}
 
</ul></li>|#default=}}
−
 
 
{{Editgrn_open}}<font color=red>8.5.010 updates end here</font>{{Editgrn_close}}
 
{{Editgrn_open}}<font color=red>8.5.010 updates end here</font>{{Editgrn_close}}
 
<li>To extend support for Callback reporting:
 
<li>To extend support for Callback reporting:

Revision as of 20:18, May 7, 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!