Skip to content

Releases: amazon-connect/amazon-connect-streams

2.3.1

26 Aug 14:56
e59f62f
Compare
Choose a tag to compare
  • Update CCP initial retry Logic - Skips initial refresh interval delay (~5s) for first attempt and continues exponential delay for subsequent attempts
  • Adding MD5 hashing for VoiceID keys
  • Redact VoiceID speaker ID from logs

2.3.0

12 Aug 17:26
84d9092
Compare
Choose a tag to compare
  • Fix an issue in Streams’ Voice ID APIs that may have led to incorrect values being set against the generatedSpeakerID field in the VoiceIdResult segment of Connect Contact Trace Records (CTRs).
  • Make StreamsJS compatible with strict mode
  • Fix an issue that connect.ValueError and connect.StateError don't print error message properly

2.2.0

08 Jun 16:51
4000972
Compare
Choose a tag to compare

Task Template APIs support and other improvements

2.1.1

19 Apr 19:42
09f0343
Compare
Choose a tag to compare
  • Fixed build time behavior so "STREAMS_VERSION" string in core.js will be replaced with the NPM package version in the release artifacts, as expected
  • Bumping version of minimist package in package-lock.json to 1.2.6

2.1.0

19 Apr 19:09
1bc7ac0
Compare
Choose a tag to compare
v2.1.0

Update package version

2.0.0

04 Jan 16:55
d136b26
Compare
Choose a tag to compare

2.0.0

Removed Functions:

  • agent.onContactPending has been removed. Please use contact.onPending instead.

New build system:

  • Make and gulp have been removed and Webpack has been added as the new build system.
  • Running npm run release will continue to produce both release/connect-streams.js and release/connect-streams-min.js and run tests.
  • npm run build-streams will now produce the same files without running any tests.
  • npm run test-mocha will just run tests and relies on the release files.
  • Every command that runs a gulp script has been removed.
  • See the README for more details

Bugs Fixed:

  • connect.onError now triggers. Previously, this api did not work at all. Please be aware that, if you have application logic within this function, its behavior has changed. See its entry in documentation.md for more details.
  • initCCP will no longer append additional embedded CCPs to the window when called multiple times. Please note that the use-case of initializing multiple CCPs with initCCP has never been supported by Streams, and this change has been added to prevent unpredictable behavior arising from such cases.

New Features:

    1. connect.core.onIframeRetriesExhausted: Streams now performs backoff while attempting to reload the iframed CCP. Previously, it would endlessly retry on each ACK TIMEOUT event (connect.EventType.ACK_TIMEOUT). Now, there are six retries, performed with exponential backoff. Once these six retries to load the embedded CCP are exhausted, no more retries will be attempted. You can subscribe a callback via the api: connect.core.onIframeRetriesExhausted to understand when the retries are exhausted, and take some action.

1.7.5

12 Nov 15:48
33b723a
Compare
Choose a tag to compare
  • Added multi-party conferencing capabilities

1.7.4

12 Oct 21:29
fabb2df
Compare
Choose a tag to compare

A bug fix for updateVoiceIdSpeakerId API

1.7.3

06 Oct 22:50
1cf68fe
Compare
Choose a tag to compare

Fix a voiceId issue that getVoiceIdSpeakerId() doesn't return the updated speakerId after calling updateVoiceIdSpeakerId("XXX").

1.7.2

01 Oct 14:39
Compare
Choose a tag to compare

Bug version bump to bring version in line with npm version.