25.1 Release Table of Contents
25.1 Region Release Timetable
The following region update dates are in local time for each region.
Region | Release Date |
Australia |
January 19th, 2025 |
United Kingdom |
January 20th, 2025 |
United States |
January 20th, 2025 |
The standard Cyara Support timetable applies to this release. Cyara will offer technical support for 1 calendar year after this release is live, and this release will be marked as end of life after 2 years.
Note: Future Cyara Releases will contain all features delivered in this release.
25.1 Platform Features
-
CP-49233 - Feature: Cyara Virtual Agent for Amazon Connect with Salesforce
-
Cyara Virtual Agent for Amazon Connect can now be integrated into Salesforce, this integration enables automated testing of Salesforce Service Cloud Voice and Salesforce Amazon Connect CTI adaptor agent workspaces.
The adaptor enables functional and load testing of Amazon and Salesforce deployments from taking calls, validating CTI attached data, release. Agents also can perform a hold, retrieve to simulate a period of consultation.
-
25.1 Platform Updates
-
CP-49236 - Changed: Cyara Virtual Attributes now support secure strings
-
Agent / Server Attributes now can be encrypted in the Cyara Platform UI and in transit by adding a "Secure." prefix.
Example: Secure.MyAppAccessKey=mysecret - this marks MyAppAccessKey being secure and it will be encrypted and password never displayed again.The functionality is useful for Nice CXone Virtual Agent to store access key/secret combo for an agent. As well as Salesforce CTI Adapter parameters when an additional Amazon Connect username and password has to be stored for an in addition to the Salesforce credentials.
-
-
CP-49602 - Changed: V3 API includes message body for 403 responses
- Some 403 (Forbidden) responses were trying to use the status message header to return the reason for the 403 result. This was incorrectly being stripped, so the message is now returned in the response body as a standard message response.
- Some 403 (Forbidden) responses were trying to use the status message header to return the reason for the 403 result. This was incorrectly being stripped, so the message is now returned in the response body as a standard message response.
-
CP-49880 - Changed: SSO Provider ID now allows the use of the dash "-" character
- Prior to this update, only Alphanumeric characters were allowed for the SSO Provider ID. Now the dash - character can be used for a SSO Provider ID. e.g Demo-Staging
25.1 Platform Issue Fixes
-
CP-49741 - Fixed: Cruncher export data limit
- The Cyara Platform 24.12 release unintentionally introduced an issue which limited the exported data in a Cruncher Campaign to 1000 rows. This limit has now been removed.