Release Notes - Hotfix release DC2023.04d
Tip
If you’re upgrading from an older bundle, be sure to check out our What's New pages for a comprehensive list of new features and important updates spanning multiple bundles.
This document contains a list of the updates and current versions of AnywhereNow software and components.
Client Components
Note
To streamline our support process, before raising a support ticket you need to ensure that the client used is upgraded to the version of the bundle and so the log provided with the ticket is inline with the Bundle. Please note that we will be unable to process support tickets raised on unsupported version.
Component | Version | Remark |
---|---|---|
Ucc.Creator scripts (SharePoint template) | 8.2.0.7 | |
Power BI template (for Power BI Desktop) |
8.8.23482.01 |
(Minimum required version for this bundle) Learn More |
Inflight Wallboard (desktop client) | 6.5.7 | |
Snapper (desktop client) |
8.7.7 |
(Minimum required version for this bundle) Learn More |
Feature Improvements
PBI | Description |
---|---|
113434 |
Previously, the WFM plugins would only send statistics data to Workforce Management platforms for the UCC's default skilltype (aka "Skill") associated to an agent. Now various skilltypes supported by the UCC, to be sent to WFM, can be configured with a new setting (if no skilltypes are defined the default "Skill" will be used). For Teleopti (by Calabrio) see: Teleopti HD - Send (agent) queue statistics For Verint see: Verint CSI – Contact Statistics Interface |
Feature Enhancements
PBI | Description |
---|---|
115159 |
Adding an email recipient in WebAgent that starts with a capital letter fails. When an email address was entered which started with a capital letter, the contact search would fail to return a result and prevent the "+" button to work. This has now been fixed. |
116459 |
The Snapper install wizard broken in version 8.7.6 when used for updating. The Install Wizard of Snapper install file version 8.7.6 did not retain a client type (New Teams client) when running as update. This has now been fixed in this version. |
114562 |
DialogueManager (text-handler backend) enhancements. Fixed an issue where after restarting the DialogueManager, valid sessions (emails/chats) still open could not be picked up and handled properly. Additionally a nlog logging error was fixed. |
113047 |
Handling emails forwarded to other UCC has been made more efficient. DialogueManager email conversations after a forward to a UCC with no subrule (plugin flow) available will now be closed instead of remaining open in the database with a permanent error message. |
115103 |
Outbound calls from a UCC not processed correctly when a WFM plugin is used. Outbound calls made from a UCC which was also configured to use and send data to a Workforce Management (WFM) tool resulted in the call statistics for the outbound calls not being sent and the subsequent error messages created resulting in a memory accumulation/leak. This has now been fixed. |
116596, 116598 |
DialogueStudio updated NodeRed and jwt-decode library to fix AnywhereNow Authentication. The NodeRed component of Dialogue Studio has been updated to the current stable version 3.1. Additionally a jwt-decode library check has been updated to cause logging in to Dialogue Studio with AnywhereNow Authentication enabled to fail. This has now been fixed. |
115867, 116364, 115129, 116095 |
Telephone number (SipUri) checking is made less restrictive in UCC and WebAgent. The required E.164 The E.164 phone number format is an international (ITU) standard for dialing telephone numbers on the Public Switched Telephony Network (PSTN). Loosely formulated, only "+" and upto 15 digits (0-9) are allowed For example: +4433221100 (For number notation/display and storage see the E.123 standard) compliance checking introduced in Bundle DC2023.04b is internally lowered from 'valid' to 'possible'. This allows the use of extension numbers by prepending them with leading zeros and a country access code, which results in a telephone number that is well-formed ('possible') but not valid. For example sip:+31000012345@domain.local;user=phone would not pass strict checking because it is not a valid E.164 PSTN (Public) destination. We now allow processing the use of this number because it is formatted 'like' an E.164 number (just not valid). |