Releases: amazon-connect/amazon-connect-streams
Releases · amazon-connect/amazon-connect-streams
2.3.1
2.3.0
- 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
2.1.1
- 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
v2.1.0 Update package version
2.0.0
2.0.0
Removed Functions:
agent.onContactPending
has been removed. Please usecontact.onPending
instead.
New build system:
Make
andgulp
have been removed andWebpack
has been added as the new build system.- Running
npm run release
will continue to produce bothrelease/connect-streams.js
andrelease/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 withinitCCP
has never been supported by Streams, and this change has been added to prevent unpredictable behavior arising from such cases.
New Features:
-
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
1.7.4
1.7.3
1.7.2
Bug version bump to bring version in line with npm version.