Jdruker/GIM DG NITR
populate-thread-facts
Section: gim-etl-populate
Default Value: false
Valid Values: true, false
Changes Take Effect: At the next run of Job_TransformGIM
Dependencies: None
Introduced: 8.5.001
Enables or disables the population of thread-related metrics in the ANCHOR_FLAGS dimension in multimedia deployments.
introduced-transfer-threshold
Section: gim-transformation
Default Value: 0
Valid Values: Any nonnegative integer
Changes Take Effect: At the next run of Job_TransformGIM
Dependencies: None
Introduced: 8.5.001
Specifies a time threshold, in seconds, for Genesys Info Mart to treat a conference as an introduced transfer. If the conference initiator's participation is less than the threshold, while the receiving agent continues on the call, Genesys Info Mart treats this call flow as a special case of transfer. The option applies only to voice calls.
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
expand-mediation-time-for-gapless
Section: gim-transformation
Default Value: true
Valid Values: true, false
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.002
Modified: 8.5.003 (default value changed from false to true)
Discontinued: 8.5.007 (replaced by show-non-queue-mediation-mm)
In eServices deployments in which routing activities are performed without the use of virtual queues, enables or disables reporting of the time that a multimedia interaction spends in a routing strategy as mediation time. To prevent a reporting gap between the end of mediation at the Interaction Queue and the start of handling by the agent, set this option to true. If routing involves more than one Interaction Queue, this configuration also removes a reporting gap between the end of the MSF for one Interaction Queue and the start of the MSF for another Interaction Queue.
- false—The time that an interaction spends in a routing strategy will not be reflected in the MSF record for the Interaction Queue.
- true—The time that an interaction spends in a routing strategy will be included in the MSF record for the Interaction Queue. If virtual queues are configured to route certain interactions, an additional, separate MSF record represents the interaction's placement in a virtual queue, and the duration of the virtual-queue MSF might also be adjusted.
populate-media-neutral-sm-facts
Section: gim-etl-populate
Default Value: false
Valid Values: true, false
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.002
Enables or disables population of the summarized resource states across all media (including voice, e-mail, chat, and 3rd Party Media media types) in the SM_MEDIA_NEUTRAL_STATE_FACT table. The value of the applicable populate-sm-*-resource-activity option must be set to true for agent states on those media to be reflected in the media-neutral agent states. The media-neutral state is the highest-priority state in effect for any of the agent's media, where the priority is determined by the sm-resource-state-priority option.
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
days-to-keep-cfg-facts
Section: gim-etl
Default Value: 400 or days-to-keep-gim-facts
Valid Values: Greater than, or equal to, days-to-keep-gim-facts
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: days-to-keep-gim-facts
Introduced: 8.5.003
Specifies the number of days to retain deleted configuration fact data in GIDB and relevant fact tables. Facts that have an end time that is earlier than the retention period are eligible to be purged. The value of the days-to-keep-cfg-facts configuration options must always be greater than, or equal to, days-to-keep-gim-facts.
For a list of the tables for which this option controls the purge threshold, see Info Mart Tables Purged by the Maintenance Job in the Genesys Info Mart Operations Guide.
link-msf-userdata-mm
Section: gim-etl
Default Value: false
Valid Values: true, false
Changes Take Effect: On the next ETL cycle
Introduced: 8.5.003
Related Options: link-msf-userdata (DN) and link-msf-userdata (Script)
Specifies whether associated user data will be stored in mediation segment facts (MSFs) for multimedia interactions that are in mediation.
- true—MSFs for multimedia interactions will store associated user data.
- false—MSFs for multimedia interactions will not store associated user data.
link-msf-userdata-voice
Section: gim-etl
Default Value: false
Valid Values: true, false
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.003
Related Options: link-msf-userdata (DN)
Specifies whether associated user data will be stored in mediation segment facts (MSFs) for voice interactions that are in mediation.
- true—MSFs for voice interactions will store associated user data.
- false—MSFs for voice interactions will not store associated user data.
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
populate-sip-im-facts
Section: gim-etl-populate
Default Value: false
Valid Values: true, false
Changes Take Effect: On the next ETL cycle
Introduced: 8.5.003.16
Enables or disables the population of both interaction data and agent activity data from SIP Instant Messaging (IM) interactions. The default value of this option is false, indicating that Genesys Info Mart will not transform SIP IM data.
populate-irf-asm-engage-duration
Section: gim-etl-populate
Default Value: false
Valid Values: true, false
Changes Take Effect: At the next run of Job_TransformGIM
Dependencies: None
Introduced: 8.5.004
Enables or disables reporting on Active Switching Matrix (ASM) engage duration (for voice interactions only). Applies only to deployments with Outbound Contact in a VoIP environment where campaigns are running in an ASM dialing mode.
- false—Genesys Info Mart does not differentiate between ASM engage duration and regular talk time.
- true—Genesys Info Mart populates the ASM_COUNT and ASM_ENGAGE_DURATION columns in the INTERACTION_RESOURCE_FACT (IRF) table as follows:
- ASM_COUNT is set to 1 to indicate that an attempt was made to engage an agent. If no attempt was made, then the column shows a value of 0.
- ASM_ENGAGE_DURATION indicates the amount of time that a successfully-engaged agent waited to be connected to a customer. This duration will be excluded from regular talk time.
Active Switching Matrix
Also known as ASM. An active component of switching hubs that rapidly switch packets from port to port by allocating memory.
Glossary
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
link-vrp-vq-msf-to-irf
Section: gim-transformation
Default Value: false
Valid Values: true, false
Changes Take Effect: At the next run of Job_TransformGIM
Dependencies: None
Introduced: 8.5.004.09
Enables linking of the MSF record for a virtual queue to the IRF record for the target agent, with a technical result of Diverted/AnsweredByAgent, in scenarios where a nonself-service IVR port uses a virtual routing point for routing operations, and the strategy includes a virtual queue.
The default value of false preserves the existing behavior of not linking the MSF record to the agent's IRF record, and assigning a technical result of Diverted/Unspecified.
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
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
expand-mediation-time-for-gapless
Section: gim-transformation
Default Value: true
Valid Values: true, false
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.002
Modified: 8.5.003 (default value changed from false to true)
Discontinued: 8.5.007 (replaced by show-non-queue-mediation-mm)
In eServices deployments in which routing activities are performed without the use of virtual queues, enables or disables reporting of the time that a multimedia interaction spends in a routing strategy as mediation time. To prevent a reporting gap between the end of mediation at the Interaction Queue and the start of handling by the agent, set this option to true. If routing involves more than one Interaction Queue, this configuration also removes a reporting gap between the end of the MSF for one Interaction Queue and the start of the MSF for another Interaction Queue.
- false—The time that an interaction spends in a routing strategy will not be reflected in the MSF record for the Interaction Queue.
- true—The time that an interaction spends in a routing strategy will be included in the MSF record for the Interaction Queue. If virtual queues are configured to route certain interactions, an additional, separate MSF record represents the interaction's placement in a virtual queue, and the duration of the virtual-queue MSF might also be adjusted.
show-non-queue-mediation-mm
Section: gim-transformation
Default Value: false
Valid Values: true, false
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.007 (replaces expand-mediation-time-for-gapless)
In eServices deployments, controls whether all mediation time for multimedia interactions, even mediation time that does not occur within a queue, is represented by an MSF.
- false — MSFs for multimedia interactions are focused only on the portion of the mediation time that occurs in a queue, whether it is an Interaction Queue or a virtual queue. There may be gaps in time between MSFs, because the multimedia interaction may not be in a queue, or may not be in a queue that is represented in Genesys Info Mart with an MSF.
- true — Provided that there is an MSF for the first Interaction Queue in a mediation (which is true for mediation time of unhandled interactions), all mediation time for multimedia interactions that occurs after the first Interaction Queue, even mediation time that does not occur within a queue, is represented by one or more MSFs. Additional, non-queue MSFs are created for multimedia interactions to represent mediation time that occurs outside an Interaction Queue MSF — for example, mediation time that occurs after an MSF for an Interaction Queue, when a routing strategy is attempting to find a routing target without the use of a virtual queue.
max-userdata-length
Section: callconcentrator
Default Value: 255
Valid Values: Any integer between 255 - 1024
Changes Take Effect: Immediately
Introduced: 8.1.512.08
Modified: 8.1.514.06 (default value changed)
Specifies the maximum length of data stored in the following columns in IDB:
- The G_SUBJECT field in the GM_F_USERDATA table.
- The VALUE field in the G_USERDATA_HISTORY and G_SECURE_USERDATA_HISTORY tables.
If ICON receives userdata values longer than the specified value, they are truncated and ICON generates the Standard-level log message 09-25109.
on-demand-migration
Section: schedule
Default Value: false
Valid Values: true, false
Changes Take Effect: When Genesys Info Mart next enters the migration state
Dependencies: None
Introduced: 8.5.007
Controls whether Genesys Info Mart will run Job_MigrateGIM automatically if the Info Mart database schema is not up to date following migration of the Info Mart server.
- true — Genesys Info Mart will launch Job_MigrateGIM automatically if the schema is not up to date.
- false — Genesys Info Mart will not launch Job_MigrateGIM automatically if the schema is not up to date and Genesys Info Mart enters the migration state.
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
routing-target-regular-dn-fold-external
Section: gim-transformation
Default Value: true
Valid Values: true, false
Changes Take Effect: At the next run of Job_TransformGIM
Dependencies: None
Introduced: 8.5.008.25
Controls whether Genesys Info Mart populates ROUTING_TARGET records for each distinct regular external DN, or folds them into a single record.
- true — Genesys Info Mart creates a single ROUTING_TARGET record with TARGET_OBJECT_SELECTED = EXTERNAL, to represent the routing target dimension for all regular external DNs used as routing targets.
- false — Genesys Info Mart creates separate ROUTING_TARGET records for each distinct regular external DN used as a routing target. (This is the legacy behavior.)
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
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
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
client
Section: elasticsearch-<data-source-id>
Default Value: off
Valid Values: off or any valid location of the cluster node(s) of the Elasticsearch cluster, properly formatted
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.009.20
This option specifies one or more nodes in the Elasticsearch cluster that Genesys Info Mart uses to retrieve data from an Elasticsearch database version 5.0 or higher. Genesys Info Mart uses the REST API client to communicate with the Elasticsearch cluster. You must specify the REST API URL address(es) for the REST client in the following format:
- rest(http://<es-node>:<port>[,http://<es-node>:<port>]*)
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
days-to-keep-gdpr-history
Section: gim-etl
Default Value: 15
Valid Values: An integer in the range 0-30
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Introduced: 8.5.010
Specifies the number of days to retain data in the CTL_GDPR_HISTORY table.
The table stores the actual personally identifiable information (PII) that relates to a General Data Protection Regulation (GDPR) request. For Right of Access (export) requests, the table stores the data that was requested for export. For Right of Erasure ("forget me") requests, the table stores the data that was redacted.
To ensure that this data is ephemeral, the retention period for records in the CTL_GDPR_HISTORY table is restricted to a maximum of 30 days.
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
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
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
sources:extra
Section: elasticsearch-<data-source-id>
Default Value: None
Valid Values: A comma-separated list of any valid identifiers (IDs) of the data sources for the Elasticsearch database
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.011.14
In an environment where a single Elasticsearch database stores data from multiple sources, this option enables you to configure a number of data sources in a single section. Specify the ID of the main data source as the suffix in the section name, such as sdr1 in elasticsearch-sdr1. Specify IDs of any additional data sources as a comma-separated list in the option value. Do not list an ID for the same data source more than once, whether explicitly or implicitly. For example, for Genesys Info Mart to retrieve the data that sdr1, ocs1, and ocs2 data sources store on node1 of the ElasticSearch cluster, add the following configuration:
Example:
- [elasticsearch-sdr1]
- sources:extra=ocs1,ocs2
- client=rest(http://node1:9200)
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
g:tenant-prefix
Section: elasticsearch-<data-source-id>
Default Value: No default value
Valid Values: A string identifying the tenant on a shared Elasticsearch cluster
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.011.15
In Genesys Engage cloud deployments, the option defines a cloud tenant prefix for Elasticsearch indexes on an Elasticsearch cluster shared across multiple cloud tenants. The tenant prefix enables Genesys Info Mart to identify Elasticsearch indexes related to the particular cloud tenant.
If specified, the option value overrides the index-pattern and index-regexp values from the XML source metadata, and the tenant prefix is included in index pattern and regexp strings.
Example
The following table illustrates the effect of specifying a tenant prefix, where the source type is sdr and the source ID is sdr0.
| [elasticsearch-sdr0].g:tenant-prefix | index-pattern | index-regexp |
|---|---|---|
| Not defined | ‘sdr’-yyyy.MM.dd | sdr-* |
| -my-tenant | ’sdr-my-tenant’-yyyy.MM.dd | sdr-my-tenant-* |
g:topic:<topic-name>
Section: kafka-<cluster-name>
Default Value: No default value
Valid Values: Any Genesys Info Mart–defined <mapping-id>, as listed in the option description
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.011.18
Specifies a Kafka topic to consume and how messages in this topic will be mapped. The <topic-name> in the option name identifies the topic Genesys Info Mart will look for in Kafka message headers and matches the topic name configured in the producer application. The option value identifies the ID in the CTL_XML_CONFIG table that Genesys Info Mart will use to map that topic into the database schema.
Configure a separate g:topic:<topic-name> option for each topic to which the Kafka producers publish reporting data. A particular kafka-<cluster-name> section might contain multiple g:topic:* options, some of which might have the same <mapping-id> value, depending on the data source.
Genesys Info Mart supports the following <mapping-id> values:
| Producer application | <mapping-id> | Supported since Genesys Info Mart release |
|---|---|---|
| Bot Gateway Server (BGS) | BGS_K | 8.5.011.18 |
| Genesys Co-browse (GCB) | COBROWSE | 8.5.011.18 |
bootstrap.servers
Section: kafka-<cluster-name>
Default Value: No default value
Valid Values: Any valid host:port combination that identifies a Kafka server in the cluster
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.011.18
Specifies the location of the Kafka broker(s) in the cluster, in the form of host:port. If there are multiple servers, use a comma-separated list.
bootstrap.servers is a standard Kafka consumer option. The option is mandatory for Genesys Info Mart, as a Kafka consumer, to know where to connect for the initial connection to the Kafka cluster. In high availability (HA) deployments, Genesys recommends that you list all the brokers in the cluster.
For more information about the bootstrap.servers option, see the Apache Kafka documentation (https://kafka.apache.org/documentation#consumerapi).
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
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
kafka-idle-timeout
Section: gim-transformation
Default Value: 10 (seconds)
Valid Values: A number (of seconds) or duration in ISO 8601 format
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.011.23
Specifies the idle timeout for polling Kafka records. If polling does not return any records within the timeout, Genesys Info Mart stops polling Kafka until the next ETL cycle.
In releases earlier than 8.5.011.23, the timeout was hard-coded, with a value of 2 seconds. In high-latency networks, the hard-coded value sometimes caused Genesys Info Mart to skip transformation of Kafka records, even if data was available.
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
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
g:index-interval
Section: elasticsearch-<data-source-id>
Default Value: No default value
Valid Values: Duration in days or ISO8601 duration format
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.013.06
Specifies the maximum expected interval, or range of data, stored in a single Elasticsearch index. The option enables you to override the default Elasticsearch index interval.
If the data source uses indices that can have different intervals, set the value of this option to the largest possible interval. For example, if the data source uses an index that sometimes contains three days of data and sometimes contains five days of data, set g:index-interval=5.
chunk-size
Section: gim-transformation
Default Value: 7200
Valid Values: Any nonnegative integer
Changes Take Effect: At the next run of Job_TransformGIM
Dependencies: None
Introduced: 8.5.013.06
Modified: .5.015.19 (behavior changed with respect to Elasticsearch data)
Specifies the maximum size of the time interval, in seconds, for which transformed data is committed in one transaction.
- For data that comes through ICON and IDB, the option applies to transformation of Multimedia and Outbound Contact details.
- A value of 0 means that the transformation job takes chunks from GIDB based on extraction high-water marks (HWMs) and audit keys generated by the extraction job. In this case, the transformation chunk size does not exceed the chunk size for extraction, as specified by the extract-data-chunk-size option.
- A value greater than 0 means that the transformation job takes chunks from GIDB based on the value of chunk-size and the previous transformation HWM, without regard to audit keys set by the extraction job.
- For data that comes through Elasticsearch:
- In releases earlier than 8.5.015.19, the transformation job always uses the value of extract-data-chunk-size to set the chunk size for transformation.
- Starting with release 8.5.015.19, the transformation job uses the smaller of extract-data-chunk-size and chunk-size to determine the chunk size to use for Elasticsearch data transformation.
- For data that comes through Kafka, starting with release 8.5.015.19 the chunk size logic is similar to the logic applied to Elasticsearch data.
For data that comes from IDB, Genesys expects that the value of chunk-size (default value 2 hours) will usually be greater than the value of extract-data-chunk-size (default value 15 minutes). When Genesys Info Mart extraction and transformation are running normally with frequent ETL cycles, the amount of data available for transformation is smaller than the chunk-size option, and all available data is transformed. In cases where there is a transformation backlog, a chunk-size value greater than extract-data-chunk-size will enable transformation to catch up with extraction quickly.
However, attempting to transform a large amount of data in one chunk can lead to performance issues or OutOfMemory errors. In cases where there is a very large backlog or where a very large quantity of data has been extracted (for example, because extract-data-chunk-size has been set to a large value and/or "runaway strategy" scenarios have occurred), temporarily reducing the value of the chunk-size option, even to a value smaller than extract-data-chunk-size, enables Genesys Info Mart to process abnormally large amounts of data more efficiently, eventually catching up with extraction.
ocs-chain-history-limit
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.
ixn-data-limit
Section: gim-transformation
Default Value: 10000
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.19
If positive, the value imposes a limit on the number of input records—such as calls, links, virtual queues, or party histories—that can be associated with a particular interaction. If the actual number of records exceeds the configured limit, error message 55-20106 is logged, and the interaction is discarded. The option currently applies only to voice interactions.
Consider setting an alarm on log message 55-20106, so that you can correct problematic scenarios that result in excessive numbers of records.
error-policy-cfg-check-backup-data-source
Section: error-policy
Default Value: error
Valid Values: error, warning
Changes Take Effect: At the next configuration check
Dependencies: None
Introduced: 8.5.014.26
Specifies the severity level of the error Genesys Info Mart generates in high availability (HA) deployments if it detects that ICON connections to the HA pair(s) of data sources (T-Server, Outbound Contact Server, or Interaction Server) have not been configured correctly. Misconfiguration occurs when the primary data-source application is not specified for both ICON connections in the HA pair.
When misconfiguration is detected, Genesys Info Mart behavior depends on the defined severity level:
- warning — Error message 55-20162 (GIM_ETL_CFG_OBJ_INVALID) is logged, describing the illegal connection.
- error — The configuration check fails, preventing the ETL from running. Two error messages are logged: 55-20162 (GIM_ETL_CFG_OBJ_INVALID), which describes the illegal connection, and 55-20037 (GIM_ETL_CONFIG_CHECK_FAILED), which indicates that the configuration check failed.
rest:max-content-length
Section: elasticsearch-<data-source-id>
Default Value: 100 MB
Valid Values: A positive integer, with or without a suffix specifying the unit of measure (B|KB|MB|GB)
Changes Take Effect: At the next run of Job_TransformGIM
Dependencies: None
Introduced: 8.5.014.26
Specifies the maximum size of the buffer holding the response to an Elasticsearch REST request. If the body of the response exceeds max-content-length, the HTTP Client throws org.apache.http.ContentTooLongException.
When you define the buffer size, use one of the following suffixes to specify the unit of measure:
- B = bytes
- KB = kilobytes
- MB = megabytes
- GB = gigabytes
- If you do not specify a unit suffix, bytes are used.
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
Starting with release 8.5.014.14 on August 30, 2019, Genesys Info Mart is part of 9.0.
This page highlights new or changed functionality that was introduced in Genesys Info Mart since release 8.5.001. Each release section indicates the minimum Interaction Concentrator (ICON) release required in order for Genesys Info Mart to function at all, as well as the minimum ICON release required to enable all of the functionality introduced in the particular release.
New in Release 8.5.014
Genesys Info Mart introduced new features and functionality in the following 8.5.014 releases.
Release 8.5.014.34
Minimum ICON release: 8.1.100.36
Minimum ICON release to enable all functionality: 8.1.514.27
New features and functionality
- Enhanced support for Unicode in Microsoft SQL Server — In Microsoft SQL Server deployments with single-language databases, the data types of some columns in certain dimension tables have been changed from varchar to nvarchar, to extend support of Unicode characters in single-language databases. For consistency, the size of some existing nvarchar columns in multi-language databases has also been modified.
- Data Export enhancements — Modifications to the update_target_*.sql scripts for creating or updating a Microsoft SQL Server target database improve support for scenarios where data is exported from a PostgreSQL or Oracle Info Mart database and subsequently imported into a Microsoft SQL Server target database.
For more information about the schema changes and data export enhancements in this release, see the "New in This Release" page in the Physical Data Model for a Microsoft SQL Server Database.
For information about additional fixes and updates introduced in this release, see the 8.5.014.34 Release Note.
Release 8.5.014.26
Minimum ICON release: 8.1.100.36
Minimum ICON release to enable all functionality: 8.1.514.27
This release introduces the following new features and functionality:
- Support for Asynchronous interactions in Advanced Chat deployments — In Cloud deployments with Advanced Chat, Genesys Info Mart supports reporting on Asynchronous interactions that are placed into a parking queue. Two new columns, PARKING_QUEUE_COUNT and PARKING_QUEUE_DURATION, have been added to the CHAT_SESSION_FACT table. The ICON attached-data specification file (ccon_adata_spec_GIM_Example.xml) included in the 8.5.014.26 Info Mart database scripts IP has been updated to include the additional KVPs ICON is required to store for reporting on asynchronous Advanced Chat interactions.
- Elasticsearch enhancement — A new configuration option, rest:max-content-length in the [elasticsearch-<data-source-id>] section, specifies the maximum permitted size for responses to Elasticsearch REST requests.
- Configuration verification enhancement — During startup and at various times during runtime in high availability (HA) deployments, Genesys Info Mart now checks that connections to the data sources are correctly specified. As described on the Enabling High Availability page, the primary application (T-Server, Outbound Contact Server, or Interaction Server) must be specified for both ICON connections in the HA pair. If an ICON connection points to a backup application in the HA pair of data sources, Genesys Info Mart generates an error.
- A new configuration option, error-policy-cfg-check-backup-data-source in the [error-policy] section enables you to define the severity level for misconfiguration of ICON connections to highly available (HA) data sources.
Release 8.5.014.19
Minimum ICON release: 8.1.100.36
Minimum ICON release to enable all functionality: 8.1.514.27
- Reporting on agent location — A new dimension table, AGENT_LOCATION, and a new column, AGENT_LOCATION_KEY, in the SM_RES_SESSION_FACT table enable you to record the locations of agents for both voice and multimedia login sessions. Interaction Concentrator release 8.1.514.27 is required to provide the location data from SIP Server and Interaction Server releases that support this functionality.
- Configuration for secure connection to Kafka — In deployments that rely on obtaining reporting data from Kafka, you can set native Kafka configuration options in the kafka-<cluster-name> configuration section to enable a secure client connection from Genesys Info Mart to the Kafka instance. For more details about security options you should consider if your Kafka cluster uses SASL_SSL authentication of if you are using SSL connections with a self-signed certificate, see kafka-<cluster-name> Section in the Genesys Info Mart Options Reference.
- Miscellaneous enhancements:
- A new configuration option, ixn-data-limit in the [gim-transformation] section, improves Genesys Info Mart handling of scenarios with excessive numbers of input records, by limiting the number of such records per INTERACTION_FACT record. If the actual number of records exceeds the configured limit, error message 55-20106 is logged, and the interaction is discarded. The option applies only to voice interactions. Previously in such scenarios, an OutOfMemory error could occur.
- To enhance reporting on Genesys Predictive Routing, two new columns in the GPM_FACT table -- VQ_GUID and VQ_RESOURCE_KEY -- enable you to join GPM_FACT to MEDIATION_SEGMENT_FACT. Use this join to make information about virtual queues (VQs) that participate in Predictive Routing interactions available in reports.
- Two new dimension tables, USER_DATA_GEN_DIM_1 and USER_DATA_GEN_DIM_2, have been added to the Info Mart schema to store out-of-box user data for internal use. Corresponding keys, USER_DATA_GEN_DIM_KEY_1 and USER_DATA_GEN_DIM_KEY_2, have been added to the IRF_USER_DATA_KEYS table, accordingly.
- Enhanced operating environment support — See the Genesys Info Mart page in the Genesys Supported Operating Environment Reference Guide for more detailed information and a list of all supported environments and databases. This release adds support for:
- Java SE 9, including support for all updates
- Kernel Virtual Machine (KVM), embedded as part of the Linux Kernel Package
- Microsoft SQL Server 2017
- PostgreSQL 9.4
Release 8.5.014.14
Minimum ICON release: 8.1.100.36
Minimum ICON release to enable all functionality: 8.1.514.11
- 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.
- 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.
Release 8.5.014.09
Minimum ICON release: 8.1.100.36
Minimum ICON release to enable all functionality: 8.1.514.11
- Predictive Routing enhancements — Genesys Info Mart now supports enhanced reporting on Genesys Predictive Routing (GPR) usage, including more detailed reporting about scores, thresholds, predictors, and routing. To enable the enhanced reporting, new KVPs from Predictive Routing - URS Strategy Subroutines release 9.0.015.00 or higher populate a new Info Mart dimension table, GPM_DIM1, and new columns in the GPM_FACT table. In addition, the values provided in some existing KVPs have been modified.
- For more information about:
- The Info Mart database schema changes, see the Physical Data Model reference for your RDBMS.
- The reporting KVPs sent by GPR, see Genesys Predictive Routing (GPR) in this document and Integrate with Genesys Reporting in the GPR Deployment and Operations Guide.
- Support for Chat Thread reporting — In Cloud deployments with Advanced Chat, Genesys Info Mart supports reporting on chat threads:
- New tables, CHAT_THREAD_FACT and MEDIA_ORIGIN, store data for chat thread statistics. A new column in the CHAT_SESSION_FACT table, THREAD_ID, has been included for future use, to associate chat session with chat thread reporting.
- A new Genesys CX Insights (GCXI) report, Chat Thread Report, is populated from the summarized thread data now available in Genesys Info Mart in Cloud deployments. (Chat Thread reporting in GCXI requires Reporting and Analytics Aggregates [RAA] release 8.5.009.04 or higher and GCXI release 9.0.011.00 or higher.) For more information, see the Chat Thread Report in the Reporting in the cloud guide.
- The ICON attached-data specification file (ccon_adata_spec_GIM_Example.xml) included in the 8.5.014.09 Info Mart database scripts IP has been updated to include the additional KVPs ICON is required to store for chat thread reporting.
- Operating environment support — Support for the following operating system and third-party prerequisites was added. See the Genesys Info Mart page in the Supported Operating Environment Reference for more detailed information.
- Oracle Linux 7 operating system
- OpenJDK 11
- Logging Enhancements — A new log event, 55-20175, supports improved handling of Outbound Contact scenarios where CONTACT_ATTEMPT_FACT records contain unsupported values. For more information, see Genesys Info Mart 8.5 Log Events Help.
8.5.013 Releases
Genesys Info Mart released the following 8.5.013 versions:
New in Release 8.5.013.06
Minimum ICON release: 8.1.100.36
Minimum ICON release to enable all functionality: 8.1.514.11
This release introduces the following new features and functionality:
- Enhanced omnichannel reporting — Two new columns in the SM_MEDIA_NEUTRAL_STATE_FACT table, END_DATE_TIME_KEY and RESOURCE_GROUP_COMBINATION_KEY, enhance support for reporting across all media channels.
- Multimedia and Outbound Contact transformation enhancement — A new configuration option, chunk-size in the [gim-transformation] section, enables you to decouple the chunk size for transformation of Multimedia and Outbound Contact details from the chunk size for data extraction. You can use this option to temporarily reduce transformation chunk size, to improve transformation performance and help avoid OutOfMemory errors in situations where there is an unusually large quantity of data to be transformed (for example, because "runaway strategy" scenarios have occurred).
- Support for variable-sized Elasticsearch indices — A new configuration option, g:index-interval in the [elasticsearch-<data-source-id>] section(s), enables you to override the default Elasticsearch index interval, so that Genesys Info Mart correctly processes Elasticsearch indices where the size of the index interval is not fixed.
- Support for Call Detail Records (CDRs) — In preparation for future support of CDRs for billing or other monitoring purposes, new CDR_* tables have been added to the Info Mart database schema. The make_gim SQL scripts have been modified to include the new table definitions and KVP mappings. Although the CDR_* tables are populated in Cloud deployments, they are considered reserved for internal use.
- Logging enhanement for Outbound Contact — A new log event, 55-20174, supports improved handling of Outbound Contact scenarios where Campaign Group dialing modes are configured with unsupported values. For more information, see the Resolved Issue for GIM-12305 in the Release Notes for this release.
New in Release 8.5.012.15
Release 8.5.012.15 introduces the following new features and functionality:
- Support for reporting on Co-browse sessions — In Genesys Engage cloud deployments with Co-browse Server 9.0.003.02 or higher, Genesys Info Mart now supports reporting on Co-browse sessions. Co-browse data is populated in the COBROWSE_* tables that were originally added to the Info Mart schema in release 8.5.011.14.
- Outbound Contact reporting extended to unattempted records — In Outbound Contact deployments with CX Contact release 9.0.000.09 or higher, Genesys Info Mart now supports reporting on contact list records that were suppressed from an outbound campaign. New LDR_* tables in the Info Mart database are populated with data that Genesys Info Mart obtains from CX Contact through Elasticsearch. The new tables supplement existing reporting about campaign activity and calling list usage sourced from Outbound Contact Server (OCS) through ICON.
- Genesys Info Mart support for CX Contact reporting on unattempted records is defined out-of-box and cannot be customized.
- For more information about:
- CX Contact support for this feature, including a definition of what constitutes an unattempted record in this context, see Integrating CX Contact with Genesys Historical Reporting in the CX Contact Deployment Guide
- The new LDR_* tables, see the Genesys Info Mart Physical Data Model for your RDBMS
New in Release 8.5.011.23
Release 8.5.011.23 introduces the following new features and functionality:
- Enhancement for data extracted from Kafka—A new configuration option, kafka-idle-timeout in the [gim-transformation] section, enables you to define the idle timeout for polling Kafka records. If polling does not return any records within the timeout, Genesys Info Mart stops polling Kafka until the next ETL cycle.
- Support for Elasticsearch 6.x—Genesys Info Mart now extracts data from indices created in Elasticsearch 6.x or later, without considering the mapping type assigned to the document. Genesys Info Mart continues to support indices created in Elasticsearch 5.x, potentially with multiple mapping types.
New in Release 8.5.011.22
Release 8.5.011.22 introduces the following new features and functionality:
- Data Export supported in on-premises deployments—Data Export functionality, introduced previously for Genesys Engage cloud customers, is now supported in on-premises deployments as well. For full information, see the "About Data Export" page in the Genesys Info Mart Physical Data Model for your RDBMS:
New in Release 8.5.011.18
Release 8.5.011.18 introduces the following new features and functionality:
- Support for obtaining reporting data from Kafka — As further preparation for future support of alternative data streams, Genesys Info Mart now supports obtaining reporting data from Genesys applications via Apache Kafka. Genesys Info Mart support for reporting data from Kafka-enabled applications is predefined and cannot be customized.
- A new configuration section, kafka-<cluster-name>, and two new options, bootstrap.servers and g:topic:<topic-name>, provide the connection and topic information that enables Genesys Info Mart to consume data from Apache Kafka.
- The make_gim SQL scripts have been modified to include Avro schema definitions and CTL_XML_CONFIG mappings for data from the first two producer applications that plan to use Kafka, namely, Bot Gateway Server (BGS) and Genesys Co-browse (GCB). Once Kafka-enabled BGS and GCB releases are available and the Kafka-related Genesys Info Mart configuration options (above) have been set, the BGS and COBROWSE tables in the Info Mart database will be populated with data from Kafka.
- ImportantBGS is currently available only in restricted release, and Genesys Info Mart currently supports BGS reporting via Elasticsearch. Existing customers can continue to use Elasticsearch.
- Miscellaneous enhancements
- Genesys Info Mart now supports reporting on outbound call flows in SIP Cluster deployments where SIP Server can disable recording and monitoring.
- A new GIM_ETL_GDPR_SUCCESS log message, STANDARD-level message 55-20173, replaces the previous TRACE-level message, 55-31406. The message indicates that "export" and "forget" requests submitted in accordance with the European Union's General Data Protection Regulation (GDPR) were processed successfully.
- Genesys Info Mart now supports Secure Socket Layer (SSL) connections to encrypt database client/server communications on PostgreSQL deployments, as well as on Microsoft SQL Server and Oracle deployments. For more information, see Enabling Secure Connections.
- For additional schema changes, see the "New in Release 8.5.011.18" section in the Genesys Info Mart Physical Data Model for your RDBMS.
- (Introduced in release 8.5.011.15) A new configuration option, g:tenant-prefix in the [elasticsearch-<data-source-id>] section(s), supports SDR and other reporting where Genesys Info Mart obtains the data from an Elasticsearch cluster shared across multiple tenants.
New in Release 8.5.011.14
Release 8.5.011.14 introduces the following new features and functionality:
- Support for async chat reporting — In eServices deployments with Chat Server release 8.5.302.03 or higher, Genesys Info Mart extends support for chat session reporting to include detailed reporting on asynchronous (async) chat sessions. New columns in the CHAT_SESSION_FACT and CHAT_SESSION_DIM tables store async chat statistics in the Info Mart dimensional model database schema.
- In deployments that include Reporting and Analytics Aggregates (RAA) release 8.5.005 or higher and Genesys CX Insights (GCXI) release 9.0.007 or higher, new aggregate (AGT_CHAT_) tables in the Info Mart database provide the summarized session data required to populate out-of-box async chat dashboards. For more information, see the RAA Release Notes, as well as the information about async chat dashboards in the GCXI 9.0 User's Guide.
- The ICON attached-data specification file (ccon_adata_spec_GIM_Example.xml) included in the 8.5.011.14 Info Mart database scripts IP has been updated to include the additional KVPs ICON is required to store for async chat reporting. For more information and related links about enabling chat reporting in your deployment, see Chat Server on the User Data Sources and KVPs page.
- In deployments that include Reporting and Analytics Aggregates (RAA) release 8.5.005 or higher and Genesys CX Insights (GCXI) release 9.0.007 or higher, new aggregate (AGT_CHAT_) tables in the Info Mart database provide the summarized session data required to populate out-of-box async chat dashboards. For more information, see the RAA Release Notes, as well as the information about async chat dashboards in the GCXI 9.0 User's Guide.
- Support for Transport Layer Security (TLS) 1.2 — Genesys Info Mart supports TLS 1.2 to secure connections with other Genesys applications at the host, port, or application level. For full information, see the pages starting from Secure Connections (TLS) in the Genesys Security Deployment Guide and Secure connections using TLS in the Platform SDK Developer's Guide. For a summary of the configuration steps to secure Genesys Info Mart connections to other Genesys applications, see Enabling Secure Connections in this deployment guide.
- Miscellaneous
- This release includes additional schema-related changes to improve user-data processing and to prepare support for new areas of reporting. For more information, see the "New in Release 8.5.011.14" section in the Genesys Info Mart Physical Data Model for your RDBMS.
- In further preparation for future support (on premises deployments) for reporting on applications that do not send data to Genesys Info Mart through ICON, a new configuration option, sources:extra in the elasticsearch-<data-source-id> configuration section, enables you to configure multiple data sources in a single configuration section, for data stored in a single Elasticsearch database.
- Recommendations on partition sizes for GIDB and fact tables in PostgreSQL deployments have been refined. For more information, see Database Partitioning.
New in Release 8.5.011
Release 8.5.011 introduces the following new features and functionality:
Support for chat reporting — In eServices deployments with Chat Server release 8.5.203.09 or later, Genesys Info Mart supports detailed reporting on Genesys Chat sessions. Two new tables, CHAT_SESSION_FACT and CHAT_SESSION_DIM, store session statistics in the Info Mart dimensional model database schema, and a control table, CTL_XML_CONFIG, is used internally to map Chat Server KVPs to the chat session tables during transformation.
In deployments that include Bot Gateway Server (BGS) release 9.0.002 or later, Genesys Info Mart also supports reporting on chat bot activity. A new fact table, BGS_SESSION_FACT, and three new BGS_* dimension tables store BGS-related data in the Info Mart dimensional model. (BGS is currently available only in restricted release. For more information about including chat bot functionality in your eServices deployment, contact your Genesys account representative.)
In deployments that include Reporting and Analytics Aggregates (RAA) release 8.5.003 or later and Genesys CX Insights (GCXI) release 9.0.005 or later, new aggregate (AGT_*) tables in the Info Mart database provide the summarized session data required to populate new chat session reports and a dashboard, which are available out-of-box. For more information, see the RAA Release Notes, as well as the information about Chat Reports and Chat Bot reports and dashboards in the GCXI 9.0 User's Guide. (GCXI is currently available only in restricted release. For more information about including GCXI reports in your deployment, contact your Genesys account representative.)
For more information and related links about enabling chat reporting in your deployment, see Chat Server on the User Data Sources and KVPs page.
- Schema changes — For full information about the new CHAT_* and BGS_* tables, as well as other schema changes in release 8.5.011, see the Genesys Info Mart Physical Data Model for your RDBMS.
New in Release 8.5.010.16
Release 8.5.010.16 introduces the following new features and functionality:
- Enhanced support for General Data Protection Regulation (GDPR) compliance — Support for GDPR compliance has been extended to employee requests. The scope of the CTL_GDPR_HISTORY history table has been similarly extended. Additionally, the UPDATE_AUDIT_KEY column was added to the CALLBACK_FACT, GPM_FACT, and SDR_* fact tables. For tables that might contain personally identifiable information (PII), the presence of the audit key enables enhanced GDPR support in deployments that include the Data Export feature.
- For more information about the CTL_GDPR_HISTORY history table and other schema changes in release 8.5.010.16, see the “New in This Release” page in the Genesys Info Mart Physical Data Model for your RDBMS. For more information about Genesys Info Mart support for GDPR compliance, see Genesys Info Mart Support for GDPR in the Genesys Security Deployment Guide.
New in Release 8.5.010
Release 8.5.010 introduces the following new features and functionality:
- Support for General Data Protection Regulation (GDPR) compliance -- To enable customers to comply with Right to Access ("export") or Right of Erasure ("forget") requests from their customers ("consumers"), Genesys Info Mart reports or redacts customer-specified personally identifiable information (PII) stored in Info Mart fact tables. The daily Info Mart database maintenance job, Job_MaintainGIM, automatically processes new GDPR requests, which customers provide in tenant-specific JSON files. To enable GDPR support:
- The CTL_GDPR_HISTORY table and a number of other new control and temporary tables have been added to the Info Mart database schema. The CTL_GDPR_HISTORY table reports the actual PII data that was requested for export or was redacted by a "forget" request. For more details, see the "New in This Release" information in the Physical Data Model for your RDBMS.
- A new configuration option in the [gim-etl] section, days-to-keep-gdpr-history, enables you to control how long data will be retained in the CTL_GDPR_HISTORY table; the maximum retention period is 30 days.
- Two new log events, 55-20172 (GIM_ETL_GDPR_ERROR) and 55-31406 (GIM_ETL_GDPR_SUCCESS) report the status of GDPR request processing, by tenant. You can set an alarm on the GIM_ETL_GDPR_ERROR message, to alert you to problems that are preventing completion of GDPR processing.
- For more information about Genesys Info Mart support for GDPR compliance, see General Data Protection Regulation (GDPR) and Genesys Info Mart and GDPR in the Genesys Security Deployment Guide. For more information about the maintenance job, see Job_MaintainGIM in the Genesys Info Mart Operations Guide.
- Preparing support for alternative data streams — In future releases, Genesys Info Mart will support obtaining data from data streams that do not go through Interaction Concentrator. Info Mart database schema changes have been made to prepare support for these alternative data channels. For full details, see the "New in This Release" information in the Physical Data Model for your RDBMS.
- Support for upgraded GIM Manager — Genesys Info Mart supports GIM Manager 8.5.010, which is the minimum release required for Genesys Administrator Extension (GAX) 8.5.270.06 and higher (see the system requirements for GIM Manager).
- Further relaxation of database privileges for PostgreSQL — To enable tenant views to be recreated as required by Genesys Info Mart and Reporting & Analytics Aggregates (RAA) when the Info Mart and RAA database users are not the same, the Info Mart database user now needs to be granted the Tenant User role, instead of schema owner permissions (see Required Database Privileges). The PostgreSQL make_gim_view_for_tenant.sql script has been modified accordingly.
New in Release 8.5.009.20
Release 8.5.009.20 introduces the following new features and functionality:
Enhanced Callback reporting — Two new dimension tables (CALLBACK_DIAL_RESULTS and CALLBACK_DIM_4) and a number of new CALLBACK_FACT table columns extend support for Callback reporting by providing more data about dialing attempts and dial results. For detailed information about the schema changes, see the Physical Data Model for your RDBMS.
The CALLBACK_* table columns are populated with actual data when you use a Genesys Mobile Services (GMS) release that provides the required user data KVPs. GMS 8.5.200.07 or later provides the KVPs that are used to populate the new tables and columns. For more information about the Callback-related KVPs that GMS supports, see Genesys Mobile Services (GMS) — for Callback.
- Enhanced query performance — The index I_GPM_FACT_SDT, on the START_DATE_TIME_KEY in the GPM_FACT table, is now defined for partitioned databases. The index improves the performance of queries that are bounded by time. Previously, the index was added to the GPM_FACT table in the schema-creation script for nonpartitioned databases (make_gim.sql), but not in the script for partitioned databases (make_gim_partitioned.sql).
- Support for Elasticsearch version 5.0+ via RESTful API — In preparation for future support (on premises deployments), for reporting on applications that do not send data to Genesys Info Mart through ICON, Genesys Info Mart now supports use of the Elasticsearch REST API client to retrieve data from an Elasticsearch 5.0 or later database. A new configuration section in the Info Mart application, [elasticsearch-<data-source-id>], and a new configuration option, client, enable you to specify the Elasticsearch cluster that Genesys Info Mart will use to retrieve data from the data source identified by <data-source-id>.
New in Release 8.5.009
Release 8.5.009 introduces the following new features and functionality:
- Support for Genesys Predictive Routing (GPR) reporting — Genesys Info Mart now supports reporting on GPR usage and the impact of predictive routing on agent and interaction-handling KPIs for voice, web, and mobile channels. Genesys Info Mart support for GPR reporting is provided out-of-box, provided that GPR has been configured to send the required KVPs in UserEvents and that ICON has been configured to store those KVPs. New GPM_* tables in the Info Mart schema store GPR-related data:
- GPM_FACT
- GPM_RESULT
- GPM_PREDICTOR
- GPM_MODEL
For more information about:
- The new tables for GPR reporting, see the Physical Data Model for your RDBMS
- The KVPs that Genesys Info Mart requires, see Genesys Predictive Routing (GPR)
- Setting up the data flow between GPR and Genesys Info Mart, see Deploying: Integrating with Genesys Info Mart in the Genesys Predictive Routing (formerly Predictive Matching) Deployment and Operations Guide
- Relaxed database permissions for PostgreSQL — In PostgreSQL deployments that use read-only tenant views, the name of the Tenant User no longer needs to be the same as the name of the Tenant User schema. On the other hand, the Info Mart user (the user account used to run Info Mart jobs) requires access to the tenant user schemas and the tenant views. The make_gim_view_for_tenant.sql script has been modified so that you now separately specify the names of the Tenant User schema and the Tenant User, as well as the Info Mart user, when you create the tenant views. For information about the database permissions required for PostgreSQL, see Required Database Privileges. For information about creating the tenant views, see Creating Read-Only Views – PostgreSQL.
- Performance improvements — Various internal enhancements improve Genesys Info Mart ETL performance. The improvements include changes to the way the extraction job handles connections to IDBs, using pooled connections that do not close until extraction is complete. As a result, your DBAs might notice a large increase in the number of open connections, many of them idle, during extraction. For more information, see Database Connections.
New in Release 8.5.008.29
Release 8.5.008.29 introduces the following new features and functionality:
- Genesys Designer reporting enhancements — New SDR_SURVEY_* tables (SDR_SURVEY_FACT, SDR_SURVEY_QUESTIONS, SDR_SURVEY_ANSWERS) support reporting on post-call surveys for interaction flows that involve applications developed with Genesys Designer. (Genesys Designer is supported in certain Cloud deployments.) For more information, see the Genesys Info Mart Physical Data Model for your RDBMS.
New in Release 8.5.008
Release 8.5.008 introduces the following new features and functionality:
- Genesys Designer reporting enhancements — Additional schema changes support reporting on interaction flows that involve applications developed with Genesys Designer. (Support for Genesys Designer is available in certain Genesys Engage cloud implementations.) For more information, see the Physical Data Model for your RDBMS.
- Logging Enhancements — Various logging enhancements enable improved management of Genesys Info Mart.
- Log message 20110 now identifies the ICONs that are delaying extraction. Furthermore, log message 20171 has been added as a cancel message for 20110. Previously, log message 20110 logged information about delayed data sources, but it was not easy to determine which ICONs were delayed.
- Genesys Info Mart now logs information to link the database connection ID and the DAP name. This link can help in finding the root cause of an issue. Previously, the logs showed only the connection ID.
- When the system property UseDbLinks=false, the extraction job no longer shows misleading database link information when logging DAPs ("-> DbLink=").
- Miscellaneous improvements
- Various internal enhancements, in some cases with associated schema changes, improve Genesys Info Mart performance. For information about the schema changes, see the Physical Data Model for your RDBMS.
- In deployments that include aggregation, the transformation job now includes media-neutral agent states in notifications sent to the aggregation engine about new or changed data.
- A new configuration option, routing-target-regular-dn-fold-external was introduced in a hot fix (8.5.008.25) subsequent to the initial 8.5.008 release. The option controls whether Genesys Info Mart populates ROUTING_TARGET records for each distinct regular external DN, or folds them into a single record with the TARGET_OBJECT_SELECTED value set to EXTERNAL.
- Operating system support — Support for the Microsoft Windows Server 2016 operating system has been added. See the Genesys Info Mart page in the Supported Operating Environment Reference for more detailed information and a list of all supported operating systems.
New in Release 8.5.007
Release 8.5.007 introduces the following new features and functionality:
- Deployment simplification and maintenance improvements — The following enhancements reduce resource requirements and effort for deployment and maintenance.
- The restrictions that each ICON application must populate its own IDB and that there must be separate IDBs for Voice and Multimedia has been relaxed. The topologies that Genesys Info Mart supports now include one ICON and one IDB for all data domains. For more information, see Supported Topologies and the new topology diagram, Multiple Data Sources per ICON: Combined Data Domains.
- To supplement IDB maintenance improvements introduced in release 8.5.006, Job_InitializeGIM, Job_ExtractICON, and Job_MigrateGIM now automatically create missing IDB views as well as indexes required for the applicable DAP role(s). In addition to streamlining and expediting execution of the initialization and migration jobs, the maintenance improvements mean that missing indexes or views will not interrupt Job_ExtractICON by causing Genesys Info Mart to go into the migration state until IDB is updated.
However, while it is no longer strictly necessary for users to run update_idb_* scripts manually, in any circumstances, there are some situations in which you might consider doing so; for more information, see Preparing IDBs.
- A new configuration option, on-demand-migration in the [schedule] section, enables you to configure Genesys Info Mart to run Job_MigrateGIM automatically when required. Previously, Genesys Info Mart entered the migration state if the Info Mart database schema needed to be upgraded following Genesys Info Mart Server migration, and manual intervention was required in order to run Job_MigrateGIM to migrate the database, before ETL functioning would resume.
- User data enhancement — In deployments that use ICON 8.1.512.08 or higher, Genesys Info Mart now supports storage of e-mail subjects up to 1024 characters. You can also store up to 1024 characters in fields with character data types in custom user data fact tables, provided that you defined these fields correctly in the user-data template script (make_gim_UDE_template.sql or make_gim_UDE_template_partitioned.sql). Previously, the limit was 255 characters. TipIf you need to store e-mail subjects or custom user data values with a length greater than 255 characters, Genesys recommends that you use ICON 8.1.514.06 or later and set the ICON max-userdata-length option accordingly.
- Unicode characters support on Microsoft SQL Server — Genesys Info Mart support for data storage in multiple languages has been extended to Microsoft SQL Server. A new database-creation script (make_gim_multilang.sql or make_gim_multilang_partitioned.sql) uses nvarchar instead of varchar data types to enable you to take advantage of Unicode characters in Microsoft SQL Server deployments, provided that ICON and Genesys Configuration Layer components have been configured as required. For more information, see Multi-Language Support.
ImportantThere is no migration path from an existing Info Mart database to a Unicode one. Contact Genesys Customer Care if you need assistance with data transfer.
- Gapless mediation reporting improvement — In eServices deployments, instead of adjusting the durations of Interaction Queue and virtual queue MSFs to eliminate gaps in mediation reporting, Genesys Info Mart now provides additional MSFs to cover the time that a multimedia interaction is in mediation but is not in an Interaction Queue for which there is an MSF. A new configuration option, show-non-queue-mediation-mm, which replaces expand-mediation-time-for-gapless, controls whether non-queue MSFs will be created and whether all mediation time will be reported, without gaps. For more information, see the discussion about MEDIATION_DURATION on the Populating Mediation Segments page in the Genesys Info Mart User's Guide, as well as the extended description of the show-non-queue-mediation-mm option.
- Management enhancements — The following features enhance management of Genesys Info Mart operations:
- Genesys Info Mart now supports the -V command-line parameter. Use this parameter to display the software version and related information, without starting Genesys Info Mart Server. You can use either an uppercase letter (V) or lowercase letter (v). For more information, see Command-Line Parameters.
- GIM Manager now automatically refreshes the data in list views. Through GIM Manager settings, you can configure the way this feature operates, such as the auto-refresh frequency and idle timeout. For more information, see Using Genesys Info Mart Manager in the Genesys Info Mart Operations Guide.
- If GIM Manager has no connection to the Genesys Info Mart Server, certain buttons in the interface are disabled.
New in Release 8.5.006
Release 8.5.006 introduces the following new features and functionality:
- New user-data propagation rule — A new user-data propagation rule, IRF_ROUTE, enhances the flexibility of user-data reporting with the capability to store the final KVP value that is present during mediation, regardless of whether the call is abandoned in mediation or delivered to a handling resource (where additional changes might be made to the key’s value). For more information about the IRF_ROUTE propagation rule, including propagation rule examples, see Propagation Rules.
- Enhanced outbound fact reporting — In eServices outbound scenarios where an outbound interaction is created outside the scope of eServices (for example, by OCS) and placed into an Interaction Queue, and then is handled and sent by a strategy without agent involvement, an IRF record is now created to record the strategy's handling of the interaction.
- Enhanced dialing target reporting — For voice interactions, if the IRF row represents a resource initiating an interaction or consultation, a new column, TARGET_ADDRESS, contains the target media address that received the interaction or consultation.
- Decreased IDB maintenance effort — Genesys Info Mart now automatically creates missing IDB indexes during extraction, without running the update_idb_* scripts. For more information, see Preparing IDBs.
New in Release 8.5.005
Release 8.5.005 introduces the following new features and functionality:
Genesys Callback reporting — This release introduces support for reporting on Genesys Callback activity on voice, web, or mobile channels, in deployments with Genesys Mobile Services (GMS). Genesys Info Mart support for Genesys Callback reporting is provided out-of-box.
Callback applications provide Callback-related data that Genesys Info Mart processes and stores in dedicated CALLBACK_* tables, which were initially introduced in an earlier Genesys Info Mart release.
Genesys Callback reporting requires Interaction Concentrator 8.1.506.07 or higher and GMS 8.5.105.12 or higher, with Genesys Callback properly configured.
For more information about configuring GMS and ICON to enable Genesys Info Mart reporting on Callback, see Genesys Mobile Services (GMS) — for Callback.
For information about Genesys Info Mart Callback-related tables, as well as information about changes to existing tables to support reporting on Callback, see the Genesys Info Mart Physical Data Model (formerly called Reference Manual) for your RDBMS.
For information about how callbacks are represented in Info Mart interaction data, see Special handling for Genesys Callback in the User's Guide, on the page about populating interaction resource data.
Data export — A new job, Job_ExportGIM, enables you to incrementally export data from the Info Mart database into .csv files. The job exports data from the dimensional model fact and dimension tables, including custom user data extension tables, and creates a .zip archive containing individual .csv files for each table. This Data Export functionality is available for Genesys Engage cloud deployments; contact your Genesys representative for more information.
- Miscellaneous:
This release includes additional schema changes to support reporting on interaction flows that involve applications developed with Genesys Designer. (Support for Genesys Designer is available in certain Genesys Engage cloud implementations.) In addition to the preparatory schema and configuration changes made in various earlier releases of Genesys Info Mart, the following observable changes in the 8.5.005.09 installation package are added to support functionality in a future release:
- Additional new SDR_* dimension tables, which are defined in the make_gim.sql and make_gim_partitioned.sql scripts.
A new configuration option, link-vrp-vq-msf-to-irf, was added to the Genesys Info Mart application template after the initial 8.5.004 release (in release 8.5.004.09). The link-vrp-vq-msf-to-irf option, in the [gim-transformation] section, enables reporting on virtual queue data in scenarios where a nonself-service IVR port uses a virtual routing point for routing operations, and the strategy includes a virtual queue.
New in Release 8.5.004
Release 8.5.004 introduces the following new features and functionality:
- Focus time reporting — Genesys Info Mart now supports reporting of agent focus time. Focus time is calculated by Genesys Workspace Desktop Edition (WDE).
Multiple interactions can be active on an agent desktop, but only one interaction has the agent's focus at any given moment. For each of an agent's active interactions, the focus time indicates the total amount of time the agent was focused on that particular interaction.
Genesys Info Mart populates two new columns in the IRF table with focus time data: FOCUS_TIME_COUNT and FOCUS_TIME_DURATION.
To enable this functionality, you require WDE release 8.5.112.08 or higher and Interaction Concentrator release 8.1.507.06 or higher.
There are no Genesys Info Mart configuration options related to reporting the time that an interaction is in focus on an agent desktop, but you must configure settings for the following two options in other Genesys applications:
- store-event-data (configured in ICON)
- reporting.case.report-case-in-focus-duration (configured in WDE)
- ASM engage duration reporting — In Outbound VoIP environments, with Outbound Campaigns running in an Active Switching Matrix (ASM) dialing mode, the time that the engaged agent is waiting to be connected to the customer (ASM engage duration) is now reported separately from agent talk time, if so configured. Two new columns, ASM_COUNT and ASM_ENGAGE_DURATION, that have been added to the INTERACTION_RESOURCE_FACT (IRF) table, are populated based on the setting for the new configuration option, populate-irf-asm-engage-duration. (The default option value is false.) Genesys Info Mart requires that OCS attaches a special KVP, GSW_CALL_TYPE="ENGAGING", to identify engaging calls. The attached data specification sample, ccon_adata_spec_GIM_example.xml, that is provided with Genesys Info Mart release 8.5.004 enables ICON to capture KVPs with the GSW_CALL_TYPE key.
-
Indicating which party ended chat — Genesys Info Mart now stores data that enables you to determine who ended a chat session. If a customer leaves the chat session before the agent, a new flag, CUSTOMER_LEFT_FIRST, is set in the ANCHOR_FLAGS dimension. The time when the customer left the chat, or the time when the agent stopped the chat session is stored in the IRF.IRF_ANCHOR_TS column. (IRF_ANCHOR_TS is the new name for the column that was called IRF_ANCHOR_SENT_TS in release 8.5.003 and IRF_ANCHOR_DATE_TIME_KEY prior to that.)
To support this functionality, Interaction Concentrator release 8.1.507.06 is required. For other prerequisites, refer to Chat Session Attributes that Indicate Who Ended the Session in the Interaction Concentrator User's Guide.
-
Reporting on multiple routing attempts — In deployments with the SIP Server configuration option divert-on-ringing set to false, Genesys Info Mart now associates multiple routing attempts with the same mediation in scenarios when multiple attempts are made to route a call from a virtual queue. The same MEDIATION_SEGMENT_ID value is used in the IRF records for all routing attempts. The technical result of Redirected/RouteOnNoAnswer is reported for all but the last routing attempt, if the attempts were unsuccessful.
To support this functionality, you require SIP Server release 8.1.102.13 and Interaction Concentrator release 8.1.509.07. While no changes are required in Genesys Info Mart configuration, you must set the following Interaction Concentrator configuration options:
- use-server-partyuuid to the value of 1 (configured in either ICON Application or Switch object)
- ring-divert to the value of 1 (configured in either Switch or the DN object for a Routing Point)
- Miscellaneous improvements:
- To minimize switchovers between IDBs and improve data quality, the extraction job now waits for more reliable data to arrive from the second ICON in an HA pair, if the available data from the first ICON is determined to be not very reliable.
- To improve processing of user data that is attached during mediation, a new column, USERDATA_FLAG, has been added to the MEDIATION_SEGMENT_FACT table (MSF). This flag facilitates an unambiguous join between the MSF and fact extension tables to retrieve correct user data that is attached during mediation.
- The field INTERACTION_RESOURCE_FACT.LAST_INTERACTION_RESOURCE is now supported for all media types. Previously, this field was supported only for voice interactions.
- A new configuration option, populate-sip-im-facts, is added to the [gim-etl-populate] section to control the transformation of SIP Instant Messaging (IM) data.
- In scenarios where a call is abandoned while queued in multiple parallel virtual queues, Genesys Info Mart now reports only the last-entered virtual queue as Abandoned. Other parallel virtual queues are reported as Cleared/Unspecified. Previously in such scenarios, MSF records for all virtual queues were reported as Abandoned.
- Genesys Info Mart now stores data to distinguish an agent from other persons in a contact center. A newly introduced value, Person, is set in the RESOURCE_.RESOURCE_SUBTYPE column for any persons who are not agents. The previously existing value, Agent, is now used in the RESOURCE_.RESOURCE_SUBTYPE column only to identify Agents (that is, the resources for whom the IsAgent flag is set in the Person configuration object). Both subtypes are associated with the Agent resource type that is stored in the RESOURCE_.RESOURCE_TYPE column.
New in Release 8.5.003
Release 8.5.003 introduces the following new features and functionality:
- Tenant metric enhancements — This release introduces a number of enhancements that allow Tenant metrics to include active multimedia interactions that have not yet been handled:
- Two new columns, ANCHOR_ID and ANCHOR_SDT_KEY, are added to the INTERACTION_FACT table. Values in these columns are derived as follows:
- For interactions that have been completed or handled, Genesys Info Mart populates the value of ANCHOR_ID based on the INTERACTION_RESOURCE_ID of the INTERACTION_RESOURCE_FACT (IRF) record with IRF_ANCHOR = 1. The ANCHOR_SDT_KEY value in this case equals the START_DATE_TIME_KEY of the same IRF record.
- For active multimedia interactions that have not yet reached a handling resource (that is, are still in mediation), Genesys Info Mart populates the value of ANCHOR_ID based on the MEDIATION_SEGMENT_ID of the MEDIATION_SEGMENT_FACT (MSF) record for the most recent mediation DN. The ANCHOR_SDT_KEY value in this case equals the START_DATE_TIME_KEY of the same MSF record.
- Starting with this release, Genesys Info Mart creates an MSF record for the first Interaction Queue that an inbound interaction enters, even if the populate-mm-ixnqueue-facts configuration option is set to false (which is the default value). Because the MSF record for the first Interaction Queue is now always populated, Genesys Info Mart is able to specify an ANCHOR_ID for active multimedia interactions that have not yet been handled, which in turn, allows Genesys Info Mart to associate the current user data values with this active interaction while it is in mediation. Because of this change in MSF population, at least one record in either IRF or MSF table now represents an active multimedia interaction. Note: In deployments with populate-mm-ixnqueue-facts = false, custom reports might need to be modified to exclude the first Interaction Queue activity.
- The following changes simplify configuration steps needed to take advantage of active interactions reporting in Tenant metrics:
- Two new configuration options are added to the [gim-etl] section of the Genesys Info Mart Application to enable user data storage for all mediation resources. To simplify configuration, instead of configuring link-msf-userdata for each individual queue, it is possible to specify:
- link-msf-userdata-voice = true to see the user data associated with all voice mediations.
- link-msf-userdata-mm = true to see the user data associated with all multimedia mediations.
The default value for these two options is false.
Note: Because storing extra user data can have performance implications, Genesys recommends that you use these options only when absolutely required. In many deployments you can instead specify link-msf-userdata for the desired queues.
- The default value of the expand-mediation-time-for-gapless option, in the [gim-transformation] section, has been changed from false to true. This change ensures there is no gap during user data collection for mediations of active multimedia interactions that have not yet been handled.
- Two new configuration options are added to the [gim-etl] section of the Genesys Info Mart Application to enable user data storage for all mediation resources. To simplify configuration, instead of configuring link-msf-userdata for each individual queue, it is possible to specify:
- Two new columns, ANCHOR_ID and ANCHOR_SDT_KEY, are added to the INTERACTION_FACT table. Values in these columns are derived as follows:
- Multimedia processing improvement—Genesys Info Mart now correctly processes scenarios that include a late reply to an e-mail interaction. When a multimedia interaction that represents the reply is created after the parent interaction has already been terminated, the transformation job now processes the child interaction as a separate interaction. In this scenario, the transformation job creates a new record in the INTERACTION_FACT table with a new INTERACTION_ID value. If the parent interaction has not been terminated, the child interaction uses the same INTERACTION_ID value as the parent interaction. Previously, the metrics related to a late reply could be lost because the transformation job might have discarded the child interactions during processing.
- Unicode characters support—For deployments with Oracle and PostgreSQL RDBMS, this release of Genesys Info Mart adds supports for data storage in multiple languages. To take advantage of Unicode characters, the Info Mart database must be created with UTF-8 encoding. To enable this functionality on Oracle, the fields with the varchar data types now use the explicit CHAR character length semantics.
- Reporting on Hunt Group Call Distribution—Genesys Info Mart now supports reporting on Genesys SIP Server calls that are distributed through Hunt Groups with parallel or sequential distribution strategy. For accurate data representation, Interaction Concentrator release 8.1.504.04 or later is required.
- Logging enhancements:
- Genesys Info Mart configuration check can generate two new log messages:
- 55-20037 Configuration check failed.
Alarm Advisory: Indicates an abnormal condition. You might consider setting an Alarm Condition for this event. Cancel event: 55-20169 - 55-20169 Configuration check passed.
Description: Configuration check passed, no severe issues were found
- 55-20037 Configuration check failed.
- Genesys Info Mart configuration check can generate two new log messages:
- Purging enhancement—The maintenance job now purges configuration fact data from GIDB and relevant fact tables. A new configuration option, days-to-keep-cfg-facts, sets the retention policy for configuration fact data.
- Visibility of Aggregation status — For deployments that include Reporting and Analytics Aggregates (RAA), Genesys Info Mart Manager (GIM Manager) now displays Aggregation latency in the ETL status view.
Note: This feature requires the new type of data storage available in RAA release 8.1.400.23 or later (aggregate data formerly stored in tables with the prefix AG2_*, is now stored in tables with the prefix AGT_*, and presented through views with the prefix AG2_*). - Miscellaneous:
- Extraction job performance has been improved in the area of merge for voice interactions.
- New combinations in the TECHNICAL_DESCRIPTOR table are added for multimedia online interactions that are placed into archive queues.
- For the deployments that rely on Genesys Info Mart for reporting on Post-Call Survey user data, two new scripts are added to the Genesys Info Mart installation package:
- make_gim_post_call_survey.sql —for use with nonpartitioned databases
- make_gim_post_call_survey_partitioned.sql—for use with partitioned databases
Run the appropriate script manually if your deployment uses Post-Call Survey functionality.
- The Application object settings for the following configuration options can now be overridden at the level of individual supported objects:
- q-short-abandoned-threshold-voice—You can now set this value at the Switch or DN (for Virtual Queues or ACD Queues) object level.
- q-short-abandoned-threshold—You can now set this value at the Switch, DN (for Virtual Queues), or Script (for Interaction Queues or Workbin) object level.
- A new column, CREATE_AUDIT_KEY, has been added to the SM_MEDIA_NEUTRAL_STATE_FACT table.
- To accommodate additional custom record fields with high cardinality values, 20 new columns (RECORD_FIELD_41 through RECORD_FIELD_60) of the varchar data type are added to the CONTACT_ATTEMPT_FACT table.
- In the INTERACTION_RESOURCE_FACT table, the name of the IRF_ANCHOR_DATE_TIME_KEY column is changed to IRF_ANCHOR_SENT_TS. This field is now populated with the time when the first response left the contact center (the TERMINATED_TS value of the first successful reply). This field is populated only if IRF.IRF_ANCHOR has a value of 2; otherwise the field has a value of NULL.
- Subsequent to the changes that were originally introduced in release 8.1.402, this release includes additional schema changes to prepare for support of additional interaction flows, such as the Voice Callback feature of Genesys Mobile Services.
- PUSH_DELIVERY_CONFIRMED_TS field has been added to the CALLBACK_FACT table.
- CUSTOMER_READY_TO_START_IXN_TS field has been added to the CALLBACK_FACT table.
- DESIRED_TIME field in the CALLBACK_FACT table has been renamed to DESIRED_TIME_TS.
- A constraint, NOT NULL, has been added for the DESIRED_TIME_TS field (with a default value of 0).
- Supported Environments:
- This release adds support for Java version 8.0.
- This release adds support for Red Hat Enterprise Linux AP 64 bit x86 7.
New in Release 8.5.002
Release 8.5.002 introduces the following new features and functionality:
- Reporting on media-neutral agent states — Genesys Info Mart now optionally reports the summarized states for each agent across all media—referred to as media-neutral agent states. To populate media-neutral agent states, Genesys Info Mart takes already transformed summarized states for each media as the source data. The highest-priority state in effect for any of the agent's media is reported as the media-neutral state for the agent. An existing configuration option, sm-resource-state-priority, controls priority of agent states relative to each other. A new configuration option, populate-media-neutral-sm-facts in the [gim-etl-populate] configuration section, which is set to false by default, controls reporting on media-neutral agent states. A new fact table, SM_MEDIA_NEUTRAL_STATE_FACT, stores the media-neutral agent states.
- Gapless mediation reporting — In eServices deployments in which routing activities are performed without the use of Virtual Queues, an optional capability allows you to report on routing activities without gaps in mediation time. For Genesys Info Mart to include the time at a Routing Strategy into the mediation duration of the appropriate MEDIATION_SEGMENT_FACT record, you must set the new expand-mediation-time-for-gapless option, in the [gim-transformation] section, and the previously available populate-mm-ixnqueue-facts option, in the [gim-etl-populate] section, to true.
- Enhanced visibility of ETL status — Genesys Info Mart now provides information about latency for each functional area. Latency, which is expressed in the hh:mm:ss format, reflects the time elapsed since the occurrence of the last contact center event for which reporting data has been successfully stored in the Info Mart database. Use Genesys Info Mart Manager release 8.5.0 to view these details.
- Call Detail Record data reporting — Genesys Info Mart now provides Call Detail Record (CDR) data. You can access CDR data using a new database view, CDR, which is created within the Info Mart database schema, to conveniently research the call volume or look for specific records by ID. In a multi-tenant configuration environment, you can also create tenant views on top of the CDR view.
- New user-data propagation rule — A new user-data propagation rule, IRF_INITIAL, enhances the flexibility of user-data reporting with the capability to store the KVP value that is associated with the interaction when the interaction enters the resource that is the subject of the IRF or MSF record.
- Miscellaneous:
- New configuration options, expand-mediation-time-for-gapless and populate-media-neutral-sm-facts have been added to the Genesys Info Mart application template, in the [gim-etl-populate] and [gim-transformation] sections, respectively.
- New CDR and CDR_DATE_TIME views have been added to the make_gim.sql and make_gim_partitioned.sql scripts.
New in Release 8.5.001
The initial 8.5.001 release introduces the following new features and functionality:
- Support for reporting on additional interaction scenarios:
- Introduced Transfer — In voice deployments with business processes that require a transferring agent to introduce the customer to another agent before transferring the call, a new configuration option, introduced-transfer-threshold in the [gim-transformation] section, enables you to specify a time threshold for a conference. If the conference initiator's participation in the conference is less than the threshold, while the receiving agent continues on the call, Genesys Info Mart treats this call flow as a special case of transfer. [+] Tell me more
- Chat Consultation — In eServices deployments with agent desktop applications, such as Workspace Desktop Edition (formerly Interaction Workspace [IWS]), that offer a chat consultation feature by setting a visibility mode on the conference request, Genesys Info Mart can now distinguish whether an agent is being invited into a chat interaction for a conference (visibility mode = 1) or for a consultation (visibility mode = 3). [+] Show resulting reporting changes
To report on chat consultation, Genesys Info Mart requires a minimum ICON release of 8.1.500.04, which introduced support for visibility mode.
Chat Conference or Consultation through a Queue — In eServices deployments with agent desktop applications, such as Workspace Desktop Edition, that use subordinate auxiliary interactions to implement a chat conference or consultation through a queue, Genesys Info Mart blends the main and auxiliary interactions to present a simplified reporting result. Previously, Genesys Info Mart reported fully on the internal handshaking and other subordinate interactions, which are not significant for reporting.
A new interaction subtype, InternalConferenceInvite, which the agent desktop application uses to identify the subordinate interactions, supports this functionality.
Support for reporting on chat consultation through a queue requires ICON 8.1.500.04 or higher.
- Multimedia performance improvements — To improve performance in multimedia deployments that do not need to track interaction threads, a new configuration option, populate-thread-facts in the [gim-etl-populate] section, controls whether thread-related metrics will be populated. The default value (false) is a change in behavior compared with releases since Genesys Info Mart 8.1.101.04.
When populate-thread-facts = false, the FIRST_*_THRD fields in the ANCHOR_FLAG dimension will be ignored for the purposes of populating the IRF.ANCHOR_FLAGS_KEY metric. In deployments that use Reporting and Analytics Aggregates (RAA) or Genesys CX Insights (GCXI)/Genesys Interactive Insights (GI2), related agent thread metrics (for example, AG2_ID_*.ACCEPTED_THREAD) are also not populated.
- Operating system changes — Support for the following operating systems has been discontinued:
- HP-UX (all versions)
- IBM AIX 5.3
- RedHat Enterprise Linux 4
- Solaris/SPARC version 9
- Windows Server 2003
- Miscellaneous:
- Schema changes — Schema changes related to user-data fact and dimension tables support improved performance by downstream reporting applications and assist in exporting and archiving data. For more information, see the “New in Release 8.5.001” information in the Genesys Info Mart 8.5.0 Reference Manual for your RDBMS (for example, New in Release 8.5.001 in the Microsoft SQL Server document).
- This release includes schema and configuration changes to prepare Genesys Info Mart to support reporting on interaction flows that involve applications developed with Genesys Designer. In addition to the preparatory schema and configuration changes for additional interaction flows that were described in the release note for Genesys Info Mart 8.1.402.07, the following observable changes in the 8.5.001 installation package are added to support functionality in a future release:
- New SDR_* fact and dimension tables, which are defined in the make_gim.sql and make_gim_partitioned.sql scripts.
- A new configuration section, [elasticsearch-sdr0], with a new configuration option, client, in the Genesys Info Mart application template.
- A new configuration file, EsConfiguration.xml, to map rules for transformation.