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.
Glossary
encrypt-certificate
Section: gim-export
Default Value: No default value
Valid Values: Valid path and file name.
Changes Take Effect:
Dependencies: None
Introduced: 8.5.116.20
Specifies the full path and file name of the certificate Genesys Info Mart uses to encrypt exported ZIP files.
If the option is not specified (the default value), Genesys Info Mart does not encrypt the exported files.
ocs-allowed-lateness
Section: gim-transformation
Default Value: PT0S
Valid Values: ISO 8601 duration format
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.116.20
Specifies how long Genesys Info Mart waits for late-arriving Outbound Contact data. Outbound Contact data (such as GO_METRICS) that arrives late, but within the specified limit, is processed during transformation.
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.
Glossary
ocs-dial-sched-time
Section: gim-transformation
Default Value: last
Valid Values: last, first
Changes Take Effect: At the next run of Job_TransformGIM
Dependencies: None
Introduced: 8.5.116.26
Specifies which value of the OCS dial_sched_time field will be recorded in the DIAL_SCHED_TIME and DIAL_SCHED_TIME_KEY columns in the CONTACT_ATTEMPT_FACT (CAF) table:
- last — Genesys Info Mart will use the last value OCS recorded in the dial_sched_time field during the contact attempt. This means the CAF record will show the scheduled dial time of the next attempt. This is the default value, which preserves legacy behavior.
- first — Genesys Info Mart will use the initial value OCS recorded in the dial_sched_time field during the contact attempt. This means the CAF record will show the dial time scheduled for the attempt that is the subject of the record.
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.
Glossary
max-chunks-per-job
Section: gim-etl
Default Value: 10
Valid Values: 1-100
Changes Take Effect: On the next ETL cycle
Dependencies: None
Modified: 8.5.116.29 (scope extended)
Specifies the number of extracted data chunks that the transformation job processes in one ETL cycle. As long as it seems practical from the performance perspective, increase the option value to transform a larger amount of data in a single cycle.
Starting with release 8.5.116.29 in deployments using the Data Export feature, the option also controls the maximum number of export chunks that can be created by the export job during each job run. In situations where the time range to be exported exceeds the export chunk size (for example, if there is a backlog because data is being re-exported), a larger number of export chunks reduces the time required to process a large export backlog.
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.
Glossary
New in Release 8.5.1
Genesys Info Mart 8.5.1 is part of 9.0.
This page highlights new or changed functionality that was introduced in Genesys Info Mart 8.5.1. See New in Release 8.5.0 for information about changes introduced in earlier Genesys Info Mart 8.5.0 releases.
For related information about Info Mart database schema changes, see the "New in Release 8.5.1" and "Summary of Info Mart Schema Changes" pages in the Genesys Info Mart Physical Data Model (for Microsoft SQL Server, Oracle, or PostgreSQL, respectively). See the short video on New in 8.5.x Releases to learn how to view summary information about schema changes.
New in Release 8.5.116.29
Release 8.5.116.29 introduces the following new features and functionality:
- Data Export enhancements:
- The export job now creates multiple export chunks when the amount of data to be exported exceeds the export chunk size — for example, when there is an export backlog, such as when data is re-exported. The max-chunks-per-job configuration option enables you to specify the maximum number of export chunks. This improvement can significantly reduce the time required to process large export backlogs. Previously, the export job exported only one chunk of data each time it ran.
- The export job now purges exported data based on the export creation time, as indicated by the created-ts value in the export metadata file. Previously, the export job purged exported data based on the data generation time, as indicated by the max-data-ts value in the metadata file.
- Support for PostgreSQL 13 — See the Genesys Info Mart page in the Genesys Supported Operating Environment Reference for more detailed information and a list of all supported databases.
New in Release 8.5.116.26
Release 8.5.116.26 introduces the following new features and functionality:
- Log4j 2 support — The Apache Log4j library included with Genesys Info Mart has been upgraded to 2.17.1. To maintain backward compatibility, Genesys Info Mart configures Log4j 2 using the existing properties created for Log4j 1, as specified in the log4j.properties file in the Genesys Info Mart installation package. You can modify the Log4j 1 configuration by setting options in the [log4j] configuration section. For information about how you can switch to using Log4j 2 configuration, see the Upgrade Notes section in the Genesys Info Mart 8.5.116.26 Release Note.
- Security enhancements — Various 3rd party libraries are updated for security reasons.
- Outbound Contact reporting enhancement — A new configuration option, ocs-dial-sched-time in the [gim-transformation] section, enables you to specify whether Genesys Info Mart populates the CONTACT_ATTEMPT_FACT.DIAL_SCHED_TIME column with the first or the last value OCS records in the dial_sched_time field during a contact attempt. The default value, which preserves legacy behavior, is to use the last value.
- For additional schema-related changes, see "New in Release 8.5.116.26" in the Genesys Info Mart Physical Data Model (for Microsoft SQL Server, Oracle, or PostgreSQL, respectively).
New in Release 8.5.116.20
Release 8.5.116.20 introduces the following new features and functionality:
- Outbound Contact enhancement — A new configuration option, ocs-allowed-lateness, enables you to specify how long Genesys Info Mart waits for late-arriving outbound data. Outbound data (such as GO_METRICS) that arrives late but within the specified limit, is processed during transformation.
- Data Export encryption — Genesys Info Mart now supports encrypting the .zip files in your Data Export package. A new configuration option in the [gim-export] section, encrypt-certificate, enables you to specify the path to the certificate Genesys Info Mart uses when encrypting the exported .zip files. If the option is not specified (the default value), Genesys Info Mart does not encrypt the exported files.
New in Release 8.5.116.12
Release 8.5.116.12 introduces the following new features and functionality:
- Data Export enhancements:
- Two SQL scripts that support use of the Data Export feature are now made available in the output folder that contains the data export:
- update_target_gim_db*.sql — Enables you to create or update the target database schema into which you import the exported Info Mart data. The version of the script matches the Genesys Info Mart release in effect when the data export was performed.
- make_export_views<db-schema>.sql — Enables you to restore or troubleshoot the export views used for your data export (for example, if your views get corrupted or you want to restore an earlier version).
- Scripts are provided for all the RDBMSs that Genesys Info Mart supports, stored in RDBMS-specific sql_scripts/<dbms> folders in the Data Export output package. Previously, the scripts were available only in the sql_scripts folder in the installation directory.
- For more information about using the update_target script and export views, see the "About Data Export" page in the Genesys Info Mart Physical Data Model for your RDBMS (for Microsoft SQL Server, Oracle, or PostgreSQL, respectively).
- The GIDB_GC_ANNEX table, which stores information about the configuration of contact center objects such as persons and DNs, is now included in Data Export.
- Two SQL scripts that support use of the Data Export feature are now made available in the output folder that contains the data export:
- Reporting data enhancements:
- A new column, STEPCOUNT, in the SDR_BOTS_FACT table supports more granular tracking of bot activity.
- For reporting data that Genesys Info Mart obtains from Kafka, a new table, CTL_PRODUCER_INFO, stores information about the version of the upstream application or service that produced the Kafka data. A new column, PRODUCER_INFO_KEY, in the CTL_AUDIT_LOG table enables you to trace the Kafka data lineage and is useful for troubleshooting purposes.
- A new column, ORSSESSIONID, is added to the INTERACTION_RESOURCE_FACT (IRF) and MEDIATION_SEGMENT_FACT (MSF) tables for internal use.
- For more details about the schema-related changes, see the Genesys Info Mart Physical Data Model for your RDBMS (for Microsoft SQL Server, Oracle, or PostgreSQL, respectively).