Jump to: navigation, search


Section: gim-etl
Default Value: 3600
Valid Values: 0 or any positive integer
Changes Take Effect: On the next ETL cycle
Dependencies: None
Modified: 8.1.1 (behavior changed)

Specifies the maximum time, in seconds, after the end of a call, during which an agent who handled that call can send UserEvent-based key-value pair (KVP) data. If the call has ended and the UserEvent-based KVP data is sent after this timeout, the transformation job does not process the UserEvent-based KVP data.


Section: gim-etl
Default Value: 3600
Valid Values: 0 or any positive integer
Changes Take Effect: On the next ETL cycle
Dependencies: None

Specifies the maximum duration, in seconds, of voice interactions in the deployed environment, as well as a number of important timeouts for both voice and multimedia interactions.


Section: gim-etl
Default Value: false
Valid Values: true, false
Changes Take Effect: On the next ETL cycle
Introduced: 8.1.2
Related Options: link-msf-userdata-voice and link-msf-userdata-mm

Specifies whether associated user data will be stored in mediation segment facts (MSFs) for interactions that are in mediation at this DN (in other words, in this queue), including user data for interactions that are not distributed to a handling resource after the mediation.

  • true—MSFs will store associated user data.
  • false—MSFs will not store associated user data.

Genesys Info Mart Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
08/20/18 Update X X X X

Helpful Links

Releases Info

Deployment Procedure

8.5.0 Deployment Procedure

Product Documentation

Genesys Info Mart

Genesys Products

List of Release Notes

What's New

This release includes only resolved issues.

Resolved Issues

This release contains the following resolved issues:

The transformation job now correctly processes call flows where an old, expired interaction reappears in the Interaction Database (IDB) and then in Global Interaction Database (GIDB) as a new interaction. Previously in such scenarios, the transformation job might fail with the following exception:

Job step 'CORE_MM' failed. com.genesyslab.gim.etl.exceptions.TaskExecutionException: com.genesyslab.gim.etl.jobs.transform.common.InteractionTransformException: Interaction(xxxx) cannot be transformed due to ArrayIndexOutOfBoundsException.


After a failure of the transformation job, the next transformation job is no longer likely to fail because of missing temporary tables. In release, the transformation job might have failed with a log message similar to the following:

SQLException for SQL [CREATE TABLE TMP_PARTY_XSEQ(,XSEQ numeric(10))]; ORA-00904: : invalid identifier


The maintenance job now checks the content of the DATE_TIME table to ensure it is consistent with options in the [date-time] configuration section. If option values are changed and the table content becomes inconsistent with the options, the DATE_TIME table is truncated and repopulated. (GIM-12094)

Genesys Info Mart now correctly populates the CAL_LAST_DAY_IN_WEEK column in the DATE_TIME table. Previously, some values in the CAL_LAST_DAY_IN_WEEK column might have been set inconsistently. (GIM-12074)

Genesys Info Mart now correctly associates user data with the MEDIATION_SEGMENT_FACT (MSF) row for a virtual queue in the following scenario:

  • The link-msf-userdata configuration option is set to true for a virtual queue DN.
  • User data that is mapped using the PARTY propagation rule is set by the routing strategy while the call is in the virtual queue.
  • The call is later diverted from the virtual queue.

In Genesys Info Mart release deployments, the user data was not associated with the MSF row. (GIM-12073)

The transformation job now purges expired records from the STG_ACTIVE_CALL_HIST table. Previously, this staging table was not purged. If you need to purge the STG_ACTIVE_CALL_HIST table manually, contact Genesys Customer Care for instructions. (GIM-12070)

Support has been reinstated for the Linux Community Enterprise operating system (CentOS) 7. Previously, an issue with the installation package prevented Genesys Info Mart deployment on this operating system. (GIM-12011)

For General Data Protection Regulation (GDPR) compliance, Genesys Info Mart processes any "export" or "forget" JSON files that have been added or modified since the last processed JSON file. However, in some situations, the same "export" file could have been processed more than once, resulting in duplicated information in CTL_GDPR_HISTORY. Redundant processing of export files has been corrected. (GIM-12063)

On deployments with a partitioned Info Mart database, the transformation job now correctly attaches user data KVP(s) to INTERACTION_RESOURCE_FACT (IRF) records for the PARTY rule and for user data that is sent in UserEvents after the max-call-duration but before the user-event-data-timeout timeouts expire. Previously in this scenario, user data KVPs might not be attached. (GIM-12003)

Upgrade Notes

Refer to the Deployment Procedure for this release to deploy the installation package within your environment.


  • To enable all of the functionality provided in this release, Genesys Info Mart requires Interaction Concentrator release 8.1.514.06 or higher. At a minimum, Genesys Info Mart release 8.5 requires Interaction Concentrator For additional recommendations, see ICON Recommendations in the Known Issues and Recommendations section.
  • Genesys recommends that you manage jobs using Genesys Info Mart Manager, but if you continue to use Genesys Info Mart Administration Console, Genesys recommends that you use Genesys Info Mart Administration Console release 8.1.3 or higher.
  • Genesys Info Mart Manager release 8.5.010 requires Genesys Info Mart release 8.5.009 or higher. Genesys Info Mart release 8.5 is compatible with Genesys Info Mart Manager release 8.1.4 and higher.
  • Genesys Info Mart Manager and GAX interoperability requirements are reciprocal:
    • Genesys Info Mart Manager release and later requires GAX release, and vice versa.
    • Genesys Info Mart Manager 8.5 releases earlier than 8.5.010 require GAX 8.5 releases earlier than GAX, and vice versa.
This page was last edited on August 24, 2018, at 17:21.
Comments or questions about this documentation? Contact us for support!