22.7 Release & Support Timetable
Release Date | End of Life | End of Support |
14th November, 2022 | 14th November, 2023 | 14th November, 2024 |
22.7 Release Table of Contents
22.7 Region Release Availability
Region | Availability |
Australia |
✔️ |
United Kingdom |
✔️ |
United States |
❌ |
Note: Future Cyara Releases will contain all features delivered in this release.
22.7 Platform Features
CP-29372 - Feature: Virtual Agent: Genesys Multicloud CX - Hold/Retrieve/Transfer support
Genesys Multicloud CX (Genesys 9) now supports call transfer scenarios, as well as hold and retrieve activities. This will allow validating Genesys Multicloud CX contact centers with more accuracy.
CP-29817 - Feature: Virtual Agent performance improvements to validate 50k Agents
Previously during large load tests (50k+), Cyara Virtual Agent (CVA) could experience several-minute delays in recording results. This has now been resolved to keep behavior results up to date. Under high load, the Agent Real-Time report can now have a few seconds and up to 1-minute delay.
CP-27999 - Feature: Pulse Dashboard: Enhanced retry and alarm threshold configuration
Previously it was possible to set up additional pulse calls to retry a failed connection. Now a service group has a configurable retry count setting to increase resolution in the event of a suspected issue as well a configurable threshold per category.
The enhancement allows dealing with occasional response time or audio issues that do not warrant a major incident. A user can choose to have 2 retries and a threshold of 3 to raise an alarm if a prompt recognition has failed 3 times.
The retries operate as before - additional calls are made out of sequence to improve optics for a suspect issue. Retries do not replace/override the original pulse result.
Note: Retries will utilise your purchased ports, please ensure you have enough to run the pulse and additional retries in case of a failure.
22.7 Platform Updates
CP-30512 - Changed: Service Groups - Outbound Retries Warning
When creating a Service Group that monitors an outbound Test Case, users will now correctly be informed that retries do not get triggered by outbound calls.
CP-30587 - Changed: Collect user feedback on Pulse false negatives
When a user uses the "Force Success" function in a Pulse Dashboard, an option to fill out a survey will be supplied. The intent of this survey is to collect feedback on false negatives and improve the accuracy of Cyara Pulse Dashboards over time.
CP-31049 - Changed: Cyara Storage maximum upload size
Cyara Storage can be configured with maximum upload size in bytes. The default limit was 30,000,000 bytes. Now it is increased to 50MB. This can be further configured using the configuration file.
CP-31194 - Changed: Data Driven scenarios restriction
When executing Test Cases, Cyara will restrict number of Data Driven scenarios available per single Test Case. Default limit is 220,000. If this limit is exceeded, Test Case will not be expanded and result will be flagged with Internal Error.
CP-31356 - Changed: Limit Testcase Scenarios in API
New Platform configuration setting "Data Driven Scenarios Limit per Test Case Limit" has been added for limiting data driven scenarios for Test Cases. Default value for that limit is 220,000. This is configurable by Platform Administrators.
Following API endpoints are enforcing this limit.
- API: POST: /v3.0/accounts/{accountId}/testcases/import
This API is used for importing one or more Test Cases. While importing Test Cases using the API, Cyara will check if any of the Test Cases being imported have limit greater than our configured value. The Cyara Platform will discard only those Test Cases that exceed the limit with following message.
"Data driven scenarios (xx) exceeded the limit of (x) for the Test Case: TEST_CASE_NAME" - API: POST: /v3.0/accounts/{accountId}/testcases/{testCaseId}/testcaseparameter
This API endpoint is used to import Test Case parameter scenarios for a given Test Case ID. If number parameters scenarios is greater than our limit, imports are discarded with following error message.
"Test Case Parameter Creation Failed. The number of scenarios has exceeded the limit"
22.7 Issue Fixes
CP-30995 - Fixed: Restrict Scenario count for Test Cases and Datasets
Scenario count for Test Cases and Datasets are now restricted based on a configuration value set by the Platform Administrator. Exceeding this limit results in an error returned in the Test Case Scenario or Dataset editors when upon creating or updating the Test Case/Dataset. API 3.0 endpoints for Test Cases and Datasets have also been updated to enforce these limits.
CP-29949 - Fixed: Cyara Call Engine Service Restart
Resolved a situation potentially triggered in a scenario when Cyara Call Engine service is started, and immediately restarted. Given specific environmental circumstances, it could encounter a scenario where it is unable to bind to network ports after restart.
CP-30303 - Fixed: Voice campaign exceeds number of allocated concurrent ports
In a scenario where calls are retried (in a Pulse or Velocity campaign), and the Voice Campaign is configured with one concurrent port, Cyara might have exceeded allowed concurrency by one port.
CP-30450 - Fixed: Storage performance degradation under heavy load
The Cyara Storage service would experience performance degradation during heavy load, which would cause file lock errors to be logged.
CP-30530 - Fixed: Pulse Dashboard: Forcing a result to success updates results in all dashboards Previously when the "Force Success" function was invoked on a dashboard, the changes were not auto-updated for other users or a video wall. This has been resolved and the changes will be reflected on all open dashboards.
CP-30533 - Fixed: Fixed name of entry module when duplicating shared module
When duplicating a shared module, the entry module will also be renamed as well if the name has changed.
CP-31348 - Fixed: Deletion of CX Module with null Parameters
If a CX Module was missing its outcome parameter, then it was impossible to delete it through the Cyara Platform UI.
Comments
0 comments
Article is closed for comments.