[CP-7424] - Feature: Velocity Test Case auto-transcription - Data-driven phone number
Support has been added for using a data-driven phone number in Velocity Test Case auto transcription. Only static (not dynamic) data-driven phone numbers are supported (scenarios added manually, or uploaded from a file), and only the phone number defined in the first scenario will be used. Any changes to data-driven scenarios require the Test Case to be saved before the changes can be used in auto-transcription. [CP-7751] - Feature: Platform Logging Enhancement - Call Context Logging has been improved for Voice Components to include context information. The context information helps track the life cycle of a particular Call across the various components that take part in its execution.
[CP-7751] - Feature: Platform Logging Enhancement - Call Context
Logging has been improved for Voice Components to include context information. The context information helps track the life cycle of a particular Call across the various components that take part in its execution.
[CP-8421] - Feature: Database Tools updated to support Media Storage service
The Database Tools are now Media Storage aware and can perform delete operations to remove unnecessary recordings. An additional improvement removes unused Test Result history records as well.
[CP-8448] - Feature: Direct File Transfer
The Cyara Platform now supports a new Direct File Transfer API, for transferring files between various components. This is a replacement for the numerous fileshares required across the platform. While fileshares are still supported in this release, the functionality is now deprecated and will be removed in an upcoming release.
[CP-8470] - Feature: API - Bulk export of Test Cases
A new REST API has been provided to Export Blocks and Test Cases. The optional parameters 'folder' and 'recursive' can be supplied for bulk operations.
[CP-8508] - Feature: CE.Next - G.711 support for 10ms packetization
CE.Next now supports 10ms packetization when using G.711 (alaw or ulaw) codecs.
[CP-8549] - Feature: Enable Queueing of SIP re-invite for Call Engine
The Call Engine will now defer the processing of SIP re-invites until it is ready to handle them. Previously, it would respond immediately with a SIP 491 Pending response.
[CP-8592] - Feature: Dashboard - Monitor Agent results on the Dashboard
Support has been added for monitoring Agent Behaviors on the Dashboard. This feature currently only supports on-premises Dashboards and AX.
[CP-8604] - Feature: CX Model recognizes Choice tags in prompts
The CX Model editor now recognizes {Choice} Tags in Prompts, and allows the use of the {$var} parameter in DTMF responses.
[CP-8747] - Feature: Dashboard - Chart series color customization
The colors used for the Dashboard chart series are now configurable.
[CP-8774] - Feature: Agent Historical reports for Request Service Call activities
'Request Service Call' Activities on Agent Historical Activity Result Details pages will now show the detailed results of the Service call. This includes the name of the Service, duration, input values, and the output values returned.
[CP-4466] - Changed: CRV - Save Recording Audio
The 'Save Recording Audio' checkbox present on the CRV Pulse Campaign creation page has been removed as it was unused; Recordings are always saved.
[CP-6309] - Changed: CE.Next - Phone Number formatting
Phone Number fields on the Test Result Details page are no longer prepended with the string 'sip:'
[CP-7576] - Changed: Outbound Voice Campaign CAPS
The CAPS field for Outbound Voice Campaigns has been removed, as it was not used.
[CP-7622] - Changed: Improved logging when inserting Test Results
The log entry for prcInsertTestResult now prints all the input parameters, instead of only the CampaignRunID, TestRunTicket, and TestCaseHistoryId.
[CP-7673] - Changed: Desktop Manager Error Messaging
When the Agent Desktop Manager tries to connect to remote desktops, it is possible for the Group Policy settings on the target computer to enforce a new username and password dialog to be presented, instead of using the supplied credentials. The re-entering of the username and password cannot be automated, but a detailed error message is now provided outlining how to modify the Group Policy to allow direct connections.
[CP-7780] - Changed: Updated default password length requirement
The minimum password length is now 11 characters by default, up from the previous default of 8 characters. This will be enforced for all new Users, and any password resets.
[CP-8197] - Changed: Voice Scheduler - Call Routing Rules violation
In situations where the Call Routing Rules were violated via a Tag override, the Result that was stored in the database was "No Call Engines were able to make the call". This has been changed to indicate exactly what the issue was.
[CP-8443] - Changed: Bulk email notifications
The batch size for sending Bulk email notifications can now be set in the Web Portal's configuration file.
[CP-8449] - Changed: Audio Files integrated with Storage
Audio Files (Reference audio used for PESQ/MOS by Test Cases) are now integrated with the Cyara Storage Service. All new and existing Audio Files will be saved and retrieved via the Storage service. Saving Audio Files to Shared folders is no longer available. A migration utility is available to move existing Audio Files from the filesystem into Media Storage.
[CP-8476] - Changed: Platform Email Notifications Integration with Storage Service
Platform Email Notifications is now integrated with the Cyara Storage Service to save and retrieve Attachments. All new Attachments will be saved and retrieved via the Storage service. Saving Attachments to Shared folders is no longer available.
[CP-8478] - Changed: Crawler Integration with Storage Service
The IVR Crawler is now integrated with the Cyara Storage Service to save and retrieve Crawler Recordings. All new Crawler Recordings will be saved and retrieved via the Storage service, but preexisting Crawler Recordings will still be retrieved from shared folders. Saving Crawler Recordings to Shared folders is no longer available.
[CP-8775] - Changed: Dashboard - Service Group name no longer mandatory
The Service Group Label and Name are used to describe the Service being monitored. The Name is no longer required; only the Label is mandatory.
[CP-8981] - Changed: Logging severity changes
Across all Platform Components, a large number of log messages have had their severity reclassified as appropriate.
[CP-2993] - Fixed: Test Case Validation with EndCallIfNoMatch Tag
When Validating a Test Case which used the Tag {EndCallIfNoMatch}, real-time results were not being displayed immediately in the Portal.
[CP-7114] - Fixed: Cyara.Voice.Asr Startup Time
Startup time for the Cyara.Voice.Asr service has been improved significantly.
[CP-7572] - Fixed: Voice Scheduler unable to insert a Test Result
In a very rare set of circumstances, multiple Campaigns running the same data-driven Test Case could enter a race condition while inserting Voice Test Results into the database, where it would log an Exception into the log file and subsequently fail to insert the Test Result.
[CP-7596] - Fixed: CE.Next - Stuck after playing Audio
In very rare circumstances, CE.Next could enter a stuck state after playing an audio response, causing the Test Case to eventually fail when the Call was disconnected by the far end. This manifested as the following errors: 1) The detailed result for the offending Step was 'Hang up while playing response' 2) The Duration reported for the Step was much longer than observed in the Full Call Recording (from the start of the Step, until the call was terminated) 3) No Step Recordings were made available for the Call.
[CP-7597] - Fixed: CE.Next Startup Sequence
CE.Next now waits for initial capability assessment by ASR and TTS before accepting any work from the Voice Scheduler. Previously, Calls could be started before any speech resources were available, causing the Test Case to immediately fail.
[CP-7602] - Fixed: Dashboard Alerts occasionally not sent
When a Dashboard Alarm fired that had multiple targets defined (Email, SMS, or Web Hook), and an error was encountered while sending to one of the targets, then the remaining targets would incorrectly be skipped.
[CP-7814] - Fixed: Consecutive Optional Speech Steps
When using Consecutive Optional Steps in a Test Case, the thresholds and confidence values for each Step were incorrectly being sourced from the first Optional Step, instead of each individual Optional Step.
[CP-7840] - Fixed: Multiple Voice Step Failures
If a Step Result contained multiple failures (e.g. no-match ETH, and a response threshold being exceeded), the least-severe failure could sometimes be reported as the primary reason for failure, which could cause a Spot on the Executive Dashboard to be Amber instead of Red. The most severe failure is now reported as the primary reason for the Step failure.
[CP-7848] - Fixed: CE.Next - Multi-Step prompts with Choice Tags
In a Multi-Step prompt, which used Choice Tags on more than one Step, and the Choice tags did not declare a variable, CE.Next would incorrectly fail to run the Test Case, and report a duplicate variable name error.
[CP-7922] - Fixed: CRV Campaign Status Report
When a CRV Campaign fails because the Cyara.Voice.Quality service is not running, it will now correctly be reported as an Internal Error instead of a Failure.
[CP-7988] - Fixed: Incorrectly pronounced TTS reply
When generating TTS, if the Reply Field contained a single capital letter, e.g. 'A', then the audio would incorrectly start with the word 'Capital', e.g. 'Capital A'.
[CP-8201] - Fixed: Edit Service Error
When opening a Service for editing, an appropriate error message will now be displayed if something goes wrong while trying to load it. Previously, only a blank edit page was displayed.
[CP-8204] - Fixed: CE - Cleanup Exception
When the Call Engine was configured in Lite mode, if a Test Case ended during utterance collection, a race condition in Test Case cleanup could result in audio resources being released before utterance collection had completed, resulting in an Exception.
[CP-8395] - Fixed: Unresolved Data Driven variables
Unresolved Data Driven variables which end up in the ETH field no longer cause an exception in the Cyara.Voice.Asr service.
[CP-8403] - Fixed: Web - Test Result Race Condition
In very rare circumstances, a race condition could cause Web Test Case Results to be sent to the Scheduler before all Step Results were recorded, which would subsequently cause the Validation or Test Case Execution to fail.
[CP-8412] - Fixed: User Guide Search with IE
The User Guide's Search functionality now returns results as expected when using Internet Explorer 11.
[CP-8420] - Fixed: Default Speaker for Accounts
When a new Account is created, or an existing Account without a default Speaker is edited, it will now be given a default Speaker (English, United States - English (USA) - Speaker Independent v1), which can be used for Velocity. Additional Speakers can be manually created through the CX/Crawler Model creation page, and then set as the default for the Account.
[CP-8458] - Fixed: Synchronized Campaign without CLI
If a Voice Campaigns is Synchronized with an Agent Campaign, and also contains one or more Test Cases without a CLI, the Voice Campaign will now be marked as 'Failed Validation' when run. Previously, the Voice Campaign would fail, but with an 'Internal Error' status.
[CP-8461] - Fixed: Campaign Edit redirect loop
If the Campaign Media Type in the URL bar was edited to mismatch the Campaign being edited, it could result in a never-ending redirect loop.
[CP-8464] - Fixed: CE.Next - No RTP ports available
In rare circumstances, CE.Next was failing to release all Call resources when ending a Call, which could cause a very slow exhaustion of the available pool of resources. This would eventually result in all Calls failing to start with the error 'No RTP ports available', requiring the CE.Next service to be restarted.
[CP-8465] - Fixed: CE.Next - Uninstallation removing log folder
CE.Next was incorrectly deleting its log folder when uninstalled.
[CP-8553] - Fixed: Dashboard - Decimal number for MOS gives invalid validation error
When creating a Dashboard Chart series for MOS with a fractional Minor Threshold value, it incorrectly gave the error "The Minor and Major Thresholds should be swapped for the chosen Field."
[CP-8561] - Fixed: CE.Next - Test Case hangs on the last Step
If the following conditions were met: 1) CE.Next configured in Lite Mode, 2) running an Outbound Test Case, where the last Step contained a DTMF ETH; and 3) the Caller immediately hung up the call after sending the last DTMF tone ...then the Test Case run could get stuck, resulting in an Internal Error.
[CP-8565] - Fixed: SAML - Advertise the ACS route capitalized
The ACS route advertised by our SAML component is now with an uppercase A. Previously, the Url shown on the Identity Providers page was all lowercase, which was misleading.
[CP-8566] - Fixed: Web - Error when shutting down the Coordinator
When the Chat Coordinator shuts down, it attempts to Abort all running Campaigns. Under certain circumstances, this would fail, where there were incorrectly two instances of the same Campaign being tracked.
[CP-8590] - Fixed: SAML - Ensure redirect links are honored
If the following conditions were met: 1) an Account was configured to use a SAML Identity Provider, 2) a User for that Account was not logged into the Portal; and 3) a link was clicked on, e.g. from a Pulse alarm email, ...then after authenticating, the target URL would be lost, and the User would be presented with the Home page.
[CP-8610] - Fixed: Dashboard - Services sometimes fail to start
On certain Windows environments, the Dashboard Feed and Notification services could fail to start if connecting to the Message Bus took too long.
[CP-8613] - Fixed: CE.Next - Test Case Stalling on Optional Step
With CE.Next, if a Test Case contained a Step with the {Optional} Tag followed immediately by a Step with the {Choice} Tag, then the Test Case could become stuck on the Step with the {Optional} Tag if the collected utterance matched the {Choice} Tag.
[CP-8629] - Fixed: Dashboard - Skipped MOS Steps would show a 0 on the chart
When a MOS Step for a Test Case was missed, it would represent a 0 value on the Chart causing an unnecessary dip on the Series. Now when a MOS Step is not run, no entry is present on the Chart.
[CP-8630] - Fixed: CE Waiting for non-existent Result
A race condition in Call Engine meant that an end-of-audio event could be processed before a start of-audio event. The out-of-order processing meant that the Test Case would fail with an Internal Error result, and the CE would wait indefinitely for a recognition result that would never be generated.
[CP-8660] - Fixed: Optional and Solo Wildcard Tag Interaction
Solo Wildcard Tags (a single {*} Tag without any other ETH text) can be used once again with the {Optional AudioLength} Tag. Solo Wildcard Tags are still not permitted to be used with the {Optional Speech} Tag, but were also incorrectly not permitted with the {Optional AudioLength} Tag.
[CP-8673] - Fixed: BypassRecognition with no ASR
If a Test Case uses {BypassRecognition} and the Platform is not setup with an ASR service, CE and CE.Next were incorrectly reporting a failure as "Language not available".
[CP-8679] - Fixed: Campaign Delays from slow Notifications
If the Notification Service encountered very long delays sending Alerts, the next Campaign Run could possibly fail with an Exceeded Ports error, as the previous Campaign Run had not yet been marked as completed.
[CP-8717] - Fixed: Web Screenshots
If a Web Test Result Step didn't have a screenshot, the remaining screenshots will now be shown, and a placeholder will be displayed for any Steps without a screenshot. Previously, if a Step didn't have a screenshot, an error message would be displayed instead of the carousel.
[CP-8733] - Fixed: Spaces in Tag Variables
The Tag Helper in the Portal had been modified to use spaces to separate variables and values for the {Digits} and {Optional} Tags, which would subsequently cause the Test Case to fail to start with an 'Invalid variable name' error. The Tag Helper no longer inserts spaces between variables and their values for these Tags.
[CP-8746] - Fixed: CX Model - Duplicate Reply Step
If a CX Model contained a Database element, generated Test Cases and Blocks incorrectly contained duplicate Reply Steps.
[CP-8760] - Fixed: CE.Next - Stuck call
If a Call was aborted during session setup, and a response to the subsequent CANCEL message was never received, then Call resources could incorrectly become stuck in the allocated state, and never freed.
[CP-8826] - Fixed: CX Model Import
CX Model Importing could fail if Nodes with PESQ Audio Files were located in a sub-folder.
[CP-8890] - Fixed: CX Models stuck in the top left-hand corner
When editing a CX Model, occasionally the Model would be anchored to the top left-hand corner of the page, and would not be movable.
[CP-8893] - Fixed: Blocks created by manual generation from a CX model were Read-Only
When a User manually generated Test Cases and Blocks from a CX Model, the resulting Test Cases were editable, but the Blocks were not. Now, manually generated Test Cases and Blocks are editable, and only automatically generated Test Cases and Blocks are Read-Only.
[CP-8898] - Fixed: Web - Test Cases with excessive console messages
When a Web Test Case collects a large (as observed, over 6MB) number of console messages, this can sometimes cause the Test Case to fail to complete successfully. A new Test Case Attribute 'EnableConsoleLogging' has been added to control whether or not the console logs are captured, which defaults to True.
[CP-8906] - Fixed: CE.Next - No Channel available for incoming call
In some circumstances, CE.Next was failing to release all Call resources when an Outbound Call was rejected by the Voice Scheduler, which could cause a very slow exhaustion of the available pool of resources. This would eventually result in all Calls failing to start with the error 'No Channel available for incoming call', requiring the CE.Next service to be restarted.
[CP-8953] - Fixed: CX Models - "No Input" Nodes
In the 7.5.1 update, a bug was introduced which broke pre-existing Nodes which had an Input Type of "No Input". These Nodes were no longer crawlable, and attempting to do so would result in an Internal Error.
Comments
0 comments
Please sign in to leave a comment.