Platform Release Version 20.1.0 (Formerly 7.11.0)

20.1 Release & Support Timetable

Release Date End of Life End of Support
April 14th, 2020 April 14th, 2021 April 14th, 2022

Note: "End of Life" states that no more new deployments are allowed of this version.
End of Support is that no more issue fixes or patches will be made available for this version.

20.1 New Release Numbering System Introduction

This release is the first to feature the new Cyara release numbering system. Previously this release was titled v7.11.0. This change to the numbering system allows for greater clarity in when releases were developed within Cyara, as the release now features the calendar year, followed by the release number for that year. So as this is the first Cyara release of the 2020 calendar year it is titled 20.1

20.1 New Features

[POR-1154] - Searching within a CX Model

Cyara CX Models now support Searching using the Search tool in the top right corner of the CX Model editor UI.

[SP-134] - Feature: CX Models - Calling Number Optional

For users who are using the Cyara CX Model as a design driven document, the Calling Number field for CX Models has now been changed to be optional rather than a required field.

[CP-11979] - Feature: CX Model Test Case Generation and Naming Conventions

Test Cases generated from a CX Model will now have an updated naming scheme. Test Case names contain each Menu Element that was traversed and the final Element in the flow for that Test Case, making these names much more intuitive.

[CP-12189] - Feature: Cyara Virtual Agent - Twilio Flex Support

The Twilio Flex Contact Centre Solution is now supported by the Cyara Virtual Agent service.

[CP-11684] - Feature: Cyara Virtual Agent - Genesys Purecloud Organisation OAuth

For Genesys Purecloud integrations with Cyara Virtual Agent, Organisations that require the Organisation in the OAuth token are now supported.

[CP-12485] - Feature: New Tag - {ListenForPsstAfter}

Tag: {ListenForPsstAfter x}
This tag will delay when the system starts checking for PSST by the duration specified in seconds. The timer will start from the start of Speech.

[CP-11734] - Feature: ServiceNow Integration Import Set API

The ServiceNow Integration now supports the import Set API end-point rather than creating the Ticket directly using the Incident table.

[CP-11023] - Feature: Integrations - Add a new button to verify credentials to 3rd party systems

A new button has been added to the Integration Configuration page to test the authentication details against the 3rd party API.

20.1 Platform Updates

[CP-11833] - Changed: Campaigns link to last Campaign runs

Now provides a link on the last run field for non Pulse Campaigns to improve the efficiency of viewing the latest Campaign results.

[CP-11931] - Changed: Added RunBackgroundJobs flag to portal

Within the Portal there are some background tasks such as CX Model auto generation and custom Pulse reports that can be switched off by setting the WebSiteSettings.RunBackgroundJobs setting in the web.config file to false.

[CP-12659] - Changed: Portal: Agent Switch Password is masked

Agent Switch Password is no longer displayed in plain text in the user interface.

[CP-11779] - Changed: Portal - Donut charts show failure category

The donut chart used to group failures by the detailed result. For a Campaign with lots of failures, this could produce many small slices. Failures are now grouped by category for more human readable data.

[CP-11823] - Changed: Portal - Link to imported Test Case or Block

After a successful import a link is now available to the successfully imported Test Case or Block.

[CP-11910] - Feature: Mobile App Configuring for SSO users

Users using their enterprise security to login, can now receive an email with a link to auto-configure the Cyara Pulse App to work with their security.

[CP-12210] - Changed: Ensured all folder names are trimmed

In previous versions of the Cyara Platform it was possible to create folders that had leading or trailing spaces as part of the folder name. This release ensures that all folders are trimmed of spaces. If there were clashing folder names, eg " _Example" and "Example" (where _ represents a space), then the one with the space will be renamed with an appended (#), eg "Example (1)" to ensure that the folder names are unique.

[CP-12266] - Changed: Improved API Error Reporting

For API and web controller methods, for certain fields (such as enumerations) if an invalid value is passed, then the error message will no longer include the invalid value, just the error and indicate the field which is in error.

[CP-12268] - Changed: Call Engine Next Port Density Tables

Benchmarks for Call Engine Next are now available in the Deployment Guide.

[CP-12650] - Changed: Genesys Purecloud Integration Locations Update

Additional Location options are now available when configuring the Genesys Purecloud Integration with Cyara.

[CP-10476] - Changed: Direct File Transfer Endpoint Logging Levels

In the scenario where Cyara Web Portal application pool is recycling (or other unforeseen scenarios), it could hit an issue where it cannot bind a listener to designated DFT endpoint. In this situation, it will continue trying every 5 seconds until successful. This will now generate logs with the INFO level every 5 seconds, WARN level every 5 minutes.

[CP-12680] - Changed: Service Log files in UTF-8 format

Cyara Services now strictly enter logs in the UTF-8 text format.

20.1 Issue Fixes

[CP-8708] - Fixed: Call Engine Next Call Instantly Disconnects

If CallEngine Next receives an incoming call, which then disconnects almost straight away, a race condition occurs which would lead to an internal error.

[CP-12692] - Fixed: Web - Campaigns would fail with session availability

Occasionally the process that dispatches session reserved messages to the Scheduler would throw an exception. When this happens subsequent session reserved messages would fail to send until the Coordinator is restarted.

[CP-682] - Fixed: Max string length validation for multi-line fields

There was inconsistency between how portal was validating the input for multi-line fields such as "Description" field in test cases or steps. It was possible to enter more characters than field allowed and there was no visual indication of that until "Save" button was pressed.

[CP-693] - Fixed: Change report range's end date to be inclusive

Reports with graphs that use a date range such as Load vs Unsuccessful, will now include results to the end of the minute specified. For example, if the end time is 12:15, then results up to 12:15:59.999 seconds will be included in the graph.

[CP-1933] - Fixed: Fixed WebSiteSettings.MethodLoggingLevel

If WebSiteSettings.MethodLoggingLevel was set to log the output, either as 0-both, or 2 - Outbound, it would cause an exception in the logging code for some actions on the website. We have addressed the reason for this, and you should once again be able to use these log levels.

[CP-9677] - Fixed: Alarms - Additional information added into email alerts

Additional information regarding the failing test has been added to the Alarm alerts, inline with the information that is already sent in the Voice Pulse alerts.

[CP-10354] - Fixed: Missing Save Details button when creating a campaign

When creating a campaign if a channel was selected that did not have a valid plan, then the save details button would not be displayed even though a valid channel and plan were selected by default.

[CP-10501] - Fixed: Fixed CSV export vulnerability

When exporting data to CSV it was possible to have csv values that would behave as formulas when opened in Excel.

[CP-11238] - Fixed: Data Set Column Name Restrictions

Data Sets will now display an error if square brackets are used in the column names.

[CP-11761] - Fixed: Resolved user access on Account Usage report

Resolved inconsistent permission requirements on the Account Usage report which was preventing full use of the page.

[CP-11764] - Fixed: Cyara Virtual Agent Running Campaigns

In some scenarios, CVA Running Campaigns page database queries would cause blocking on Voice Scheduler result population. These scenarios have been addressed.

[CP-11769] - Fixed: Dashboard - Fixed ranges for known datasets

Dashboard now has fixed ranges for confidence and MOS scores which gives a consistent view across charts regardless of the data values recorded.

[CP-11850] - Fixed: Export of Email Test Cases error messaging

The correct error message will now be displayed if an export of an Email Test Case is attempted.

[CP-11864] - Fixed: Fixed layout in emailed custom PDF reports

The "Folder" column within a Cyara Pulse emailed report will no longer be overwritten by the "Test Case" column when the Test name is long.

[CP-11868] - Fixed: CX Model ghost nodes or Models being in a broken state

When multiple user were requesting CRAWL against the same MODEL node path, it had the potentiall of breaking the MenuPrompt / MenuResponse relationship.

[CP-11877] - Fixed: Processing detailed result messages

Some detailed result messages looked like they were of a system message format, but were producing an error that was not handled.

[CP-11897] - Fixed: Incorrect number of selected nodes displayed

In certain situations the count of nodes selected, reflected objects in the database rather than the number of objects selected in the front-end.

[CP-11901] - Fixed: Foreign language characters are incorrectly displayed when importing JSON CX model files

When importing a CX Model JSON file that contains foreign language characters, such as "ö" and "è", viewing the newly uploaded model would display these characters incorrectly.

[CP-12194] - Fixed: CX Models with Long Phone Numbers Crawling Issue

The previous release included a change that caused crawling of CX Models with phone numbers of 11 to 15 digits in length to fail.

[CP-12221] - Fixed: Fixed folder validation event loop

It was possible to create or rename folders and audio files in a way that would cause an endless loop of re-validation (with the same changes) which could be difficult to escape.

[CP-12251] - Fixed: Fixed API 2.5 clashing with CX Model endpoints

Updated the Web configuration file to fix issues where API 2.5 was being blocked by new CX Model endpoints. Be sure to use the new configuration file when applying this update.

[CP-12449] - Fixed: "EmailFrom" settings in Web.config were ignored

When a new user account is created, an email is sent to them from support@cyara.com, even if a different "from" email address has been set in the Web Portal config. This has been fixed, so that if an email address is provided in the config, newly created account users will receive an email from that address, otherwise, no email will be sent to them.

[CP-12565] - Feature: API - New endpoint to extract the screensots for a web test result

A new API endpoint has been added to extract the screenshots for a web test result.

[CP-12758] - Fixed: CX Models - Navigator Window Issue

The CX Model navigator window can no longer be dragged to an area outside of the CX Model.

[CP-12805] - Changed: Call Engine Reconnection Issues

If Call Engine loses connection to Voice Scheduler (due to flaky network for example), it will try to reconnect. For as long as Voice Scheduler's underlying TCP socket is not cleaned up by operating system, Voice Scheduler will deny the new connection.
This has been changed, so that in scenario where the same Call Engine is connecting to Voice Scheduler on a different port, but same IP address, Voice Scheduler will accept the new connection in favour of the old one.

[CP-13057] - Fixed: SMS Usage report Incorrect Timestamp

This report incorrectly displayed the time in UTC, this has been changed to display in local time.

[CP-13071] - Fixed: Platform Insight Call Routing Rules not showing

In the scenario where Call Routing Ruleset did not include any Route elements (e.g. only DefaultRoute present), or a CE group was defined without optional "Type" element, the page would not render.

[CP-13096] - Fixed: Agent Desktop - Browser memory spike

When using the enlarge view option in chat Test Case, agent desktop screenshot components resulted in browser memory increasing rapidly and eventually causing the browser to stall.

 

Was this article helpful?

0 out of 0 found this helpful