Release Notes - Amazon Connect Real-Time Adapter v2.4

Overview

Version 2.4 of Amazon Connect Real-time Adapter includes new features, enhancements, and bug fixes.

Contact Trace Events and Agent Events onboard - The real-time adapter can now onboard Contact Trace Events (CTR) and Agent Events from the same Kinesis stream if the customer decides to push both types of events to the same Kinesis stream. Earlier, the adapter was able to onboard only one type of events from a stream. If customer required both types of events, then the data had to be made available in two different Kinesis streams.

Date time fields custom attribute - The adapter configuration for custom attributes has been enhanced now to support custom attributes that are date time fields and is provided by Amazon Connect in a non-UTC timezone. The timezone and date time format of the custom attribute can be specified in the configuration page so that the adapter will convert the value into corresponding UTC value and store in ElasticSearch. This will ensure that all date time fields are in UTC.
Region endpoints - The adapter can now access region endpoints corresponding to the AWS region that is configured in the adapter configuration page. This enhancement adds to the existing capability of being able to access the global endpoint. The requirement varies depending on specific deployments.

Fixed a bug that was leading to previous status of agent being shown as “UNKNOWN” in some cases in AgentEventHistory index. The appropriate status as provided from Amazon Connect will be displayed.
Fixed a bug that was causing records to be missed in AgentStateDuration index in rare cases where the agent status was “UNKNOWN”.
Fixed a bug that was reported on the data in AgentStateDuration index being behind by a day.
Fixed a bug that displayed AbandonedCall field as “False” for conversations that were abandoned. The field will now display “True” for abandoned calls.
Fixed a bug identified in Daily Restart functionality of the adapter.