stop-ixn-queues
Section: gim-transformation
Default Value: No default value
Valid Values: A comma-separated list of queue names
Changes Take Effect: At the next run of Job_TransformGIM
Dependencies: None
Introduced: 8.1.402
In multimedia deployments that use stop-interaction queues in their business processes, this option specifies the Interaction Queues that are used to handle stopping an interaction (for example, Twitter_StopIxn). When an interaction is placed into one of these queues, Genesys Info Mart considers the interaction to be terminated. The transformation job assigns the technical result/reason combination of COMPLETED/UNSPECIFIED in the IRF of the handling resource that placed the interaction in the queue, and Genesys Info Mart excludes the interaction from further processing. The agent who placed the interaction in the queue is represented as the party that stopped the interaction, and the strategy that actually stops the interaction and performs any associated post-processing is not represented in Genesys Info Mart reporting.
days-to-keep-gidb-facts
Section: gim-etl
Default Value: 14
Valid Values: Any positive integer
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None in releases 8.1.0 and 8.1.1; starting with release 8.1.2, days-to-keep-gim-facts
Modified: 8.5.015.19, 8.1.2 (behavior changed with respect to multimedia interactions)
Related Options: days-to-keep-active-facts
Starting with release 8.1.1, specifies the number of days to retain fact data in GIDB. Facts that have a start time that is earlier than the retention period are eligible to be purged.
Starting with release 8.5.015.19, the retention period for multimedia facts in GIDB is determined solely by the value of days-to-keep-gidb-facts. For releases 8.5.015.19 through 8.5.016.01, be aware that, if days-to-keep-gidb-facts is less than days-to-keep-active-facts, user data for active multimedia interactions older than days-to-keep-gidb-facts might not be transformed correctly (see the Known Issue for GIM-13320 in the Genesys Info Mart 8.5.x Release Note).
For multimedia interactions in releases earlier than 8.5.015.19, this option, together with days-to-keep-active-facts, specifies the retention period for facts in GIDB: The retention period is the greater of the days-to-keep-gidb-facts and days-to-keep-active-facts option values.
In 8.1.1 releases, days-to-keep-gidb-facts specifies the retention period for completed multimedia facts, provided that there are no active facts that have the same (or earlier) start timestamps. If there are active facts with the same (or earlier) start timestamps, the eligible completed facts will not actually be purged until these active interactions have been terminated and, therefore, also become eligible to be purged, as described in days-to-keep-active-facts.
For a list of the tables for which this option controls the purge threshold, see Info Mart Tables Purged by the Maintenance Job in the Genesys Info Mart Operations Guide.
days-to-keep-active-facts
Section: gim-etl
Default Value: 30
Valid Values: Any positive integer
Changes Take Effect: At the next run of Job_TransformGIM or Job_MaintainGIM
Dependencies: None in releases 8.1.0 and 8.1.1; starting with release 8.1.2, days-to-keep-gim-facts
Modified: 8.5.015.19 (plays no role in determining purge thresholds); 8.1.2 (dependencies introduced); 8.1.1 (behavior and default value changed)
Starting with release 8.1.1, specifies the maximum number of days to retain active multimedia interactions in GIDB and the dimensional model, including certain Staging tables, after which the interactions become eligible for artificial termination.
max-time-deviation
Section: gim-etl
Default Value: 30
Valid Values: 1-120
Changes Take Effect: On the next ETL cycle
Dependencies: None
Modified: 8.5.015.19 (scope extended); 8.1.4 (minimum valid value changed)
Specifies the maximum time deviation, in seconds, to take into account for time synchronization inaccuracy between host system clocks. Starting with release 8.5.015.19, this option also specifies the maximum acceptable delay the transformation job will accommodate in scenarios in which ICON creates delayed records in the GM_F_USERDATA table in IDB.
If the maximum time deviation or delay is exceeded, Genesys Info Mart results become unreliable.
8.5.015.19
Genesys Info Mart Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 11/12/20 | Update | X | X | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- To determine the chunk size to use for Elasticsearch data transformation, Genesys Info Mart now checks the value of both {color:#444a52}{\{Optionslink|link=Options:Genesys_Info_Mart_ETL:gim-etl:extract-data-chunk-size}}{color} and {color:#444a52}{\{Optionslink|link=Options:Genesys_Info_Mart_ETL:gim-transformation:chunk-size}}{color} options, and uses the smallest value of the two. Previously, Elasticsearch data transformation chunk size was equal to the value of [gim-etl] > extract-data-chunk-size. (GIM-12815)
- Red Hat Enterprise Linux 8 (GIM-12750)
- In preparation for future support of alternative data streams, a new column, PRODUCER_ID, is added to Info Mart fact tables. (GIM-12717)
- PostgreSQL 12.x (GIM-12694)
- Elasticsearch 7.6 (GIM-12694) (GIM-12694)
Resolved Issues
This release contains the following resolved issues:
The transformation job now correctly populates the INTERACTION_TYPE_KEY column in the Interaction Resource Fact (IRF) table in scenarios where ICON delays the creation of a record in the GM_F_USERDATA table. Previously in such scenarios, the transformation job sometimes set an incorrect value referring to INTERACTION_SUBTYPE with value "Unspecified". The max-time-deviation configuration option now specifies the maximum duration of ICON delays for records in the GM_F_USERDATA table that the transformation job accommodates. (GIM-12873) (GIM-12873)
When transforming Kafka data, Genesys Info Mart now takes into account the speed with which data is written. Previously, in deployments with slow database write performance, the transformation job could read Kafka data more quickly than it could be written, which could cause OutOfMemoryException errors. (GIM-12842)
The retention period for active multimedia facts, which is defined by the days-to-keep-active-facts configuration option, no longer affects the purge threshold for multimedia facts in GIDB, which is defined by days-to-keep-gidb-facts. Previously, if the value of days-to-keep-active-facts was greater than days-to-keep-gidb-facts, the days-to-keep-active-facts value determined the purge threshold for multimedia fact data in GIDB, potentially significantly impacting ETL performance because of the increasing size of GIDB. (GIM-12835)
Genesys Info Mart now correctly populates ASM_* metrics in the INTERACTION_RESOURCE_FACT (IRF) table in scenarios where:
- An Outbound Contact campaign is running in an Active Switching Matrix (ASM) dialing mode.
- The engaging call is routed cross-site to an agent.
- The agent is later successfully connected to a customer.
Previously in such scenarios, Genesys Info Mart sometimes incorrectly populated the ASM_COUNT and ASM_ENGAGE_DURATION metrics for the agent IRF record with values of 0, instead of populating ASM_COUNT with a value of 1, and ASM_ENGAGE_DURATION with a value indicating the amount of time that the agent spent in the engaging call. (GIM-12787)
The transformation job now correctly processes multimedia interactions in environments where the option stop-ixn-queues is set for some queues. Previously in such scenarios, duration-related metrics in the INTERACTION_RESOURCE_FACT table sometimes had incorrect values. (GIM-12745)
General Data Protection Regulation (GDPR) processing now includes the TARGET_OBJECT_SELECTED column in the ROUTING_TARGET table. (GIM-12732)
The performance of the transformation job is improved for business processes that require many long-living multimedia interactions. Previously in such environments, the transformation job sometimes delayed processing of multimedia data. (GIM-12670)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.015.19.