This page was last edited on April 5, 2022, at 13:02.
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 |
---|---|---|---|---|---|---|---|
04/04/22 | Update | X | X |
This release includes only resolved issues.
This release contains the following resolved issues:
Genesys Info Mart now correctly reports a resource role of InConference in the INTERACTION_RESOURCE_FACT table in scenarios where a single-step conference is performed at the same second that the conference initiating party was created.
Previously in such scenarios, the IRF for the conference target may have had an incorrect resource role of RECEIVED or ROUTEDTO and may not have been linked back to the conference initiator IRF by the PREV_IRF_ID and RECEIVED_FROM_IXN_RESOURCE_ID fields. (GIM-13965)
Genesys Info Mart now correctly reports a value of ANSWER (33) in the CONTACT_ATTEMPT_FACT.CALL_RESULT_KEY field in scenarios where:
Previously in such a scenario, Genesys Info Mart reported CALL_RESULT as UNKNOWN_CALL_RESULT (28) for the second record. (GIM-13988)
The extraction job now processes all expected data in scenarios where ICON temporarily loses the data source connection at or near the time when extraction takes place. Previously in such scenarios, the extraction job sometimes skipped data. (GIM-13992)
On Oracle deployments, when a value is specified in the CONVERT_EXPRESSION column, the transformation job now correctly attaches KVP data for columns having DATE data type. Previously in such scenarios, the transformation job sometimes failed. For additional information, see the GIM-14014 Known Issue. (GIM-14014)
Refer to the Deployment Procedure for this release to deploy the installation package within your environment.