link-msf-userdata
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.
8.5.014.14
Genesys Info Mart Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 08/27/19 | 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:
- The transformation job no longer fails when Genesys Predictive Routing reporting events are missing the mandatory START_TS attribute.
Previously in such scenarios, the transformation job failed with an error similar to the following:
java.sql.SQLIntegrityConstraintViolationException: ORA-01400: cannot insert NULL into ("GIM"."GPM_FACT"."START_DATE_TIME_KEY")(GIM-12427) (GIM-12427)
- Logging enhancement — To improve the readability of logs, Genesys Info Mart no longer logs Genesys Info Mart Manager (GIM Manager) requests or responses by default. (GIM-12400)
(GIM-12400)
- When the migration job is running, GIM Manager does not permit any other job to run. Previously during migration, it was possible to schedule another job to run. (GIM-10042)
Resolved Issues
This release contains the following resolved issues:
Genesys Info Mart now correctly associates user data with the INTERACTION_RESOURCE_FACT (IRF) and MEDIATION_SEGMENT_FACT (MSF) rows created for a mediation resource — such as an Interaction Queue or Strategy — in multimedia scenarios where:
- The link-msf-userdata configuration option is set to true for the mediation resource.
- User data is updated after the MSF row has been initially created.
- The interaction later ends in the mediation resource.
Previously in such scenarios, the updated user data may have not been associated with the IRF and MSF rows for the mediation resource.
(GIM-12416) (GIM-12416)
The transformation job now correctly populates the TARGET_IXN_RESOURCE_ID column in the MSF table in scenarios where an interaction is revoked from agents more than once. Previously in such scenarios, the transformation job sometimes populated the TARGET_IXN_RESOURCE_ID column in the MSF table with incorrect values. (GIM-12415) (GIM-12415)
The transformation job now correctly populates the ENTRY_ORDINAL column in the MSF table in scenarios where a multimedia interaction passes through two queues in a given second. Previously in such scenarios, the transformation job sometimes populated the ENTRY_ORDINAL column with values that did not correctly reflect the order in which the interaction passed through queues.
(GIM-12405) (GIM-12405)
- Outbound Contact processing improvement — A new configuration option, ocs-chain-history-limit in the [gim-transformation] section, combined with a new log message, 55-20176, improves Genesys Info Mart handling of scenarios that result in excessive numbers of GO_FIELD_HIST and GO_CHAINREC_HIST records, by limiting the number of GIDB_GO_FIELDHIST and GIDB_GO_CHAINREC_HIST records that can be associated with a particular CHAINGUID. Previously in such scenarios, an OutOfMemory error could occur.
Section: gim-transformation
Default Value: 5000
Valid Values: 0 or any positive integer, where 0 means there is no limit imposed
Changes Take Effect: At the next run of Job_TransformGIM
Dependencies: None
Introduced: 8.5.014.14
If positive, the value imposes a limit on the number of GIDB_GO_FIELDHIST or GIDB_GO_CHAINREC_HIST records that can be associated with a particular CHAINGUID. If the actual number of records exceeds the configured limit, error message 55-20176 is logged, and the chain is ignored.
The option was introduced to prevent OutOfMemory errors during transformation in scenarios where suboptimal SCXML logic results in an excessive number of redial attempts. For example, when an internal case gets reopened from the closed state and the result of the dialed call to the customer is NO_ANSWER, if SCXML keeps adding a record to the calling list and Outbound Contact Server (OCS) keeps dialing the number until the customer answers the call, there can be a very large number of GIDB_GO_FIELDHIST and GIDB_GO_CHAINREC_HIST records for this one CHAINGUID.
Consider setting an alarm on log message 55-20176, so that you can correct problematic scenario logic if necessary.
(GIM-12395) (GIM-12395)
In chat scenarios where a transfer or conference takes place from a consultation chat, Chat Server provides limited information to downstream components, including Genesys Info Mart. As a result, there are various scenarios in which the INTERACTION_RESOURCE_FACT table reflects each agent’s _total_ participation in a chat interaction, but does not reflect the fact that agents changed from one VisibilityMode to another (from Consult mode to Conference mode, for example). (GIM-12202)
- The Genesys Info Mart Manager (GIM Manager) Installation Package (IP) is updated to simplify deployment in Windows Server 2016 environments. (GIM-12121) (GIM-12121)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.014.14.