[CP-1440] - Feature: Audit Logs
All User interactions (for example, login, editing a Test Case, creating a Campaign, etc) in the Web Portal are now logged.
- These logs are available in the Web Portal for Super Administrator Users
- Logs can be filtered on a number of criteria
- Results can be exported to CSV
Please see the User Guide (Super Administration -> Audit Logs) for a more detailed breakdown of the functionality.
[CP-1653] - Feature: Default Confidence level per Account
A default value for Voice Test Case Steps can now be defined at the Account level. This default value will apply to all new Test Case Steps created, including Steps created when editing existing Test Cases.
[CP-1672] - Feature: CVA - Data Validation
Call Classification and Validation rules can now be defined in the Web Portal. These can then be used in a Behavior for handling conditional execution of activities, as well as to validate bulk attached data, without the need for multiple Behaviors. Please see the User Guide (Virtual Agent Configuration -> Data Rules) for a more detailed overview of the functionality.
[CP-1815] - Feature: CVA Activity "Abort on Failure"
All Behavior Activities can now have the "Abort on Failure" flag set manually. Previously, only certain Activities had this flag set, and it was not configurable.
[CP-1355] - Feature: CVA - Multiple Instances
Cyara Virtual Agent now supports multiple instances running on the same host. Please see the Deployment Guide for more information on this configuration.
[CP-1464] - Feature: Purge tool directory processing
The Purge tool can now process a recording directory directly, instead of filtering by Test Case results.
[CP-1923] - Feature: Additional TTS Language support
The "ru-RA Milena", "ko-KR Yuna", and "ko-KR Narae" voices are now available for use.
[CP-1251] - Changed: CVA Installer
The Cyara Virtual Agent installer now prompts for the Site name to be supplied during installation, instead of needing to manually edit the configuration file after install.
[CP-1826] - Changed: Web Portal Default Site Value
The default value for "WebPortalSite" in tblConfig has been changed to a non-existent URL that clearly indicates it needs to be updated with an appropriate value.
[CP-1999] - Changed: Chat support for CEF
Chat Coordinators now have full support for CEF, and Awesomium has been deprecated. All Chat Test Cases will need to be manually updated to be compatible with CEF. Framesets now need to be referenced by Index or by Name, instead of CSS selectors or XPath.
[CP-1146] - Changed: CVA - Agent Chat Server using TLS
Cyara Virtual Agent will now automatically detect when an Agent Chat Server is using a TLS connection. Previously, this needed to be manually specified.
[CP-1396] - Changed: CVA - Saving Behaviors
On some systems, saving a Behavior with a large number of Activities could be slow. A loading spinner is now displayed while the Portal is saving Behaviors, to clearly show that the Web Portal is still processing.
[CP-1542] - Changed: Editing CVA Environments
An Environment can no longer have its Channel changed once it is used by an Agent.
[CP-1543] - Changed: Deleting Agent Servers
A Server can no longer be deleted if it has Agents associated with it.
[CP-1531] - Changed: Oracle Update Scripts
The Oracle Update scripts now prompt for an index namespace before performing updates.
[CP-1687] - Changed: Chat Coordinator Test Runners
Chat Coordinators now destroy Test Runners after each Test Case execution. Previously, Test Runners would be reused as long as the Chat Coordinator service was running.
[CP-1806] - Changed: Pulse database performance improvements
Pulse related database queries have been changed to be non-blocking.
[CP-1466] - Fixed: CVA intermediary states "Finishing" and "Aborting".
Aborting a CVA Campaign and then immediately running it again was causing the Campaign to go in to an Internal Error state, as CVA was still cleaning up after the last Campaign Run. Now, when a Campaign is tearing down after naturally concluding, the Campaign will enter the state "Finishing". When tearing down after an abort, the state will be "Aborting".
[CP-357] - Fixed: Rest API Request Scoping
Some REST API routes were not properly checking scope (Agent or Voice) before performing actions.
[CP-672] - Fixed: Stitched Campaign Reports
The Load v Unsuccessful report was incorrectly not displaying failed and satisfactory calls on the graphs, which were present on the individual reports.
[CP-960] - Fixed: Daylight Savings Time and DateTime fields
Attempting to enter a datetime that does not exist was throwing an exception (for example, setting the datetime to be in the hour that's skipped when a clock is moved forward for a daylight saving time change). The datetime fields will now display a validation error when an invalid time is entered.
[CP-1140] - Fixed: Web Portal Installation
When installing the Cyara Web Portal as a non-default Administrative user, the installer would fail due to lack of permissions. The error messaging around this situation has been improved so that the root cause of the issue is clearer.
[CP-1257] - Fixed: Omni Scheduler Infinite Loop
When upgrading from pre Cyara 6.0, some CCM Campaigns were not correctly migrating to CVA, which could result in them having an invalid run frequency. The Omni Scheduler now correctly handles Campaigns with an invalid run frequency.
[CP-1411] - Fixed: Improved Test Case Field Validation
When editing the Called Number field, case and white-space changes are now correctly saved to the database.
[CP-1435] - Fixed: Purge tool on Oracle Platforms
The Purge tool installer now sets the correct membership and role providers for Oracle installations.
[CP-1474] - Fixed: CVA - Portal Load Times
The performance of a number of CVA database queries has been improved. This lowers page load times significantly when working with a large (>500) number of Agents.
[CP-1513] - Fixed: Purge tool command line options
The Fetch and Delete page size options were not being correctly parsed.
[CP-1517] - Fixed: DB Utils duplicate key exception
The DB Utils was throwing an exception when attempting to purge Agent Chat results.
[CP-1550] - Fixed: CVA Attribute Truncation
When attempting to edit an attribute that contained punctuation characters, the value could be truncated.
[CP-1557] - Fixed: Users unable to log out of the Web Portal
If the following criteria were met:
- an action was performed that displayed a toast notification at the top of the screen, and
- the toast notification had disappeared
...users were then unable to log out of the Web Portal, unless they had navigated to a different page. Users are now correctly able to log out after the notification has disappeared.
[CP-1607] - Fixed: Campaign Max CAPS
When creating a Campaign, the Web Portal would automatically fill the Campaigns Max CAPS to the Account maximum. This was causing validation errors when the selected Plan had a lower Max CAPS than the Account. The Web Portal now correctly selects the lower value of the two.
[CP-1625] - Fixed: Chat Campaigns not completing
Customer Chat could get in to a state where it would attempt to process the same Test Step Result multiple times, causing the Campaign to never complete.
[CP-1642] - Fixed: Deleting Crawler Nodes
Nodes in a crawled Model were unable to be deleted unless there was an existing prompt. Nodes can now correctly be deleted without a prompt.
[CP-1661] - Fixed: Voice Scheduler Routing Rules Cache
In some cases, the Voice Scheduler was incorrectly not updating the cached configuration after the routing rules were changed in the configuration file.
[CP-1700] - Fixed: Web Portal displaying wrong version
A race condition existed that would cause the Web Portal to incorrectly display an Area's version number, instead of the Web Portal version number. Where an Area is in use, the Portal will now display the Portal version number, followed by the Area's version number in brackets.
[CP-1758] - Changed: Pulse database performance improvements
Pulse-related database queries have been tweaked to be more CPU efficient.
[CP-1766] - Fixed: Creating CVA Behaviors
On Platforms where Chat functionality was disabled, Behaviors were unable to be created due to hidden fields being left blank.
[CP-1814] - Fixed: Duplicate Chat Test Case History
Under heavy load, the Omni Scheduler was creating duplicate Test Case Histories when inserting results into the Database, which resulted in an exception. This was causing Campaigns to stall as not all results were completely processed.
[CP-1890] - Fixed: CVA - Adding Activities to a Behavior
When adding an Activity, if the following series of steps were performed in order:
- an Activity was selected from the Activity Type drop-down (e.g. "Accept Invite")
- a different Activity was then chosen (e.g. "Reject Invite")
- the "Add Activity" button was then clicked
...the Behavior Activities table would incorrectly display the first activity selected (e.g. "Accept Invite"). This cosmetic discrepancy has been fixed.
[CP-1907] - Fixed: Web Portal Method Logging Level applied incorrectly
When Web Portal instances had the method logging level set to inbound, only outbound was logged. When the method logging level was set to outbound, only inbound was logged. Note: This only affected Crawler and Custom Pulse Reports method logging. The Method logging setting now works as documented.
[CP-1917] - Fixed: Database Performance Improvements
A number of indexes have been added to improve Test Result retrieval performance.
[CP-1921] - Fixed: Default Crawler Speaker
When a Node is updated to use a non-default Speaker, and is then changed back to use the default, the UI would not reflect the change.
[CP-1924] - Fixed: Blocking Database Query
Fetching Pulse Test Case results over a large time period was temporarily locking results tables, which could lead to delays in result insertion. The procedures have been improved to be non-blocking.
[CP-2116] - Fixed: CVA - Agent Voice
When running Agent Voice Campaigns, if the following conditions were met:
- an Agent is handling an Interaction, and the current Activity has a long pause - the Interaction is terminated before the pause is over
- an Agent receives another Interaction after the initial one was terminated
- the Activity for the first Interaction becomes unpaused
...the second Interaction would incorrectly be handled by the orphaned Activity the Agent was executing for the first Interaction.