This page was last edited on September 8, 2022, at 18:28.
Comments or questions about this documentation? Contact us for support!
Interaction Concentrator
Also known as ICON. A Genesys product that collects and stores detailed data from various sources in a contact center that is empowered by using Genesys software. Downstream reporting systems can access Interaction Concentrator data in near–real time.
Operating on top of Genesys Framework, the product consists of a server application that is called ICON and a database that is called Interaction Database (IDB). The server receives data from data sources such as Configuration Server, T-Server, or particular Genesys solutions; it then stores this data in IDB by using Genesys DB Server.
Genesys Info Mart Release Notes
Release Date | Release Type | Restrictions | AIX | Linux | Mac | Solaris | Windows |
---|---|---|---|---|---|---|---|
09/08/22 | Update | X | X |
This release contains the following new features and enhancements:
password = ***
sasl.jaas.config =
org.apache.kafka.common.security.scram.ScramLoginModule required username="<USERNAME>" password="${password}";
This release contains the following resolved issues:
Genesys Info Mart now supports up to 128 characters for the following ORSSESSIONID / SESSION_ID fields:
Previously, these fields were limited to 50 characters, but ORS sometimes creates values for digital interactions that exceed 50 characters. For more information, see the Genesys Info Mart Physical Data Model documentation for your RDBMS (Microsoft SQL Server, PostgreSQL, Oracle). (GIM-14306)
The transformation job now correctly processes multimedia outbound interactions where an agent pulls an interaction from a queue (no strategy is involved in routing the interaction to the agent) and places it in another queue. Previously in such scenarios, the INTERACTION_RESOURCE_FACT.ROUTING_POINT_DURATION field might have been populated with an incorrect value. (GIM-14255)
In scenarios where the export job is not running behind the transformation job, the export job now correctly exports a single chunk. Previously in such scenarios, if the concurrent transformation job completed while the export job was still exporting the first chunk, the export job might export a second chunk. (GIM-14253)
Refer to the Deployment Procedure for this release to deploy the installation package within your environment.