Release Notes - Genesys Cloud Historical Adapter v2.9.1

Owned by Arielle Kaye Odeste
Jul 13, 2023
2 min read

Overview

In order to address duplicate entries in callsegment index, its keyid composition was changed to contain SessionId which makes every entry unique.

Bug Fixes

  • Duplicate records for call segments - Callsegment index contain duplicate entries caused by the SegmentCode being part of the KeyId. Segment Code is composed by participant counter (an incrementing counter of a conversation's participants) + session counter (an incrementing counter of a conversation's sessions) + segment counter (an incrementing counter of a conversaion's segments).
    Though entries have different SegmentCodes, counters mentioned are not reliable to be part of KeyId.

    A new field is being introduced, SessionId, which will be part of the new KeyId composition ie. ConversationId + SessionId + SegmentId.

To compare Genesys with eMite
Email:

Callback

  • CallSegments measures are expected to be in milliseconds but are in seconds - Reverted changes from previous version to keep measures in CallSegments as milliseconds