Default Value: last
Valid Values: last, first
Changes Take Effect: At the next run of Job_TransformGIM
Specifies which value of the OCS dial_sched_time field will be recorded in the DIAL_SCHED_TIME and DIAL_SCHED_TIME_KEY columns in the CONTACT_ATTEMPT_FACT (CAF) table:
- last — Genesys Info Mart will use the last value OCS recorded in the dial_sched_time field during the contact attempt. This means the CAF record will show the scheduled dial time of the next attempt. This is the default value, which preserves legacy behavior.
- first — Genesys Info Mart will use the initial value OCS recorded in the dial_sched_time field during the contact attempt. This means the CAF record will show the dial time scheduled for the attempt that is the subject of the record.
Default Value: 10
Valid Values: 1-100
Changes Take Effect: On the next ETL cycle
Modified: 22.214.171.124 (scope extended)
Specifies the number of extracted data chunks that the transformation job processes in one ETL cycle. As long as it seems practical from the performance perspective, increase the option value to transform a larger amount of data in a single cycle.
Starting with release 126.96.36.199 in deployments using the Data Export feature, the option also controls the maximum number of export chunks that can be created by the export job during each job run. In situations where the time range to be exported exceeds the export chunk size (for example, if there is a backlog because data is being re-exported), a larger number of export chunks reduces the time required to process a large export backlog.
New in Release 8.5.1
This page supplements the New in Release 8.5.1 page in the Deployment Guide, to provide information about schema-related changes introduced in Genesys Info Mart 8.5.1 releases, starting with the most recent release. See New in Release 8.5.0 for information about earlier schema-related changes introduced in Genesys Info Mart 8.5.0 releases.
For a summary you can sort to see schema-related changes by table/column and type of change, as well as by release, see Summary of Info Mart Schema Changes. See the short video on the New in the Info Mart Database page to learn how to view summary information about schema changes.
New in Release 188.8.131.52
- Data Export enhancements:
- The export job now creates multiple export chunks when the amount of data to be exported exceeds the export chunk size — for example, when there is an export backlog, such as when data is re-exported. The max-chunks-per-job configuration option enables you to specify the maximum number of export chunks. By default, the maximum number of export chunks is 10. This improvement can significantly reduce the time required to process large export backlogs. Previously, the export job exported only one chunk of data each time it ran.
- The export job now purges exported data based on the export creation time, as indicated by the created-ts value in the export metadata file. Previously, the export job purged exported data based on the data generation time, as indicated by the max-data-ts value in the metadata file.
New in Release 184.108.40.206
- Outbound Contact reporting enhancement — You can now use the ocs-dial-sched-time option to specify whether Genesys Info Mart populates the CONTACT_ATTEMPT_FACT.DIAL_SCHED_TIME and DIAL_SCHED_TIME_KEY columns with the first or the last value OCS records in the dial_sched_time field during a contact attempt.
- Schema change — Two new columns, ACTIVE_FLAG and UPDATE_AUDIT_KEY, are added to the SM_MEDIA_NEUTRAL_STATE_FACT table. These columns are reserved for future use and are not populated.
New in Release 220.127.116.11
- Data Export encryption — Genesys Info Mart now supports encrypting the .zip files in your Data Export package. For information about enabling this feature, see About Data Export Capability.
New in Release 18.104.22.168
- A new column, STEPCOUNT, in the SDR_BOTS_FACT table supports more granular tracking of bot activity.
- For reporting data that Genesys Info Mart obtains from Kafka, a new table, CTL_PRODUCER_INFO, stores information about the version of the upstream application or service that produced the Kafka data. A new column, PRODUCER_INFO_KEY, in the CTL_AUDIT_LOG table enables you to trace the Kafka data lineage and is useful for troubleshooting purposes.
- A new column, ORSSESSIONID, is added to the INTERACTION_RESOURCE_FACT (IRF) and MEDIATION_SEGMENT_FACT (MSF) tables for internal use.