Release Notes - Hotfix release DC2024.01f

This document contains a list of the updates and current versions of AnywhereNow software and components.

Announcement

Update 12-11-2024: After extensive field testing, this bundle is now a Recommended bundle. Three known issues when using Dialogue Studio remain (see: Known Issues).

Update 06-12-2024: One more issue has been identified in the latest version of the platform underlying Dialogue Studio (see: Known Issues). Please delete the debug nodes from any operational Dialogue Studio flow before upgrading to this Bundle.

Update 23-01-2025: If AnywhereNow Authentication has been enabled on an earlier bundle, when upgrading to this bundle the authentication Redirect URI should be applied in your Microsoft Entra ID Formerly known as Azure Active Directory (or Azure AD, or AAD) tenant and in the Partner Portal after the bundle upgrade has successfully completed. Please see: AnywhereNow Authentication Migration Guide

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.

Client Components

Note

To enhance our support process, please ensure that client software used is upgraded to the 'minimum required' version mentioned for this bundle, so that the logs provided with the ticket are on par with the Bundle programs. Please note that we will be unable to process support tickets raised on non-matching versions.

⁺= updated in this bundle.
Component	Version	Remark
Ucc.Creator scripts (SharePoint UCC A Unified Contact Center, or UCC, is a queue of interactions (voice, email, IM, etc.) that are handled by Agents. Each UCC has its own settings, IVR menus and Agents. Agents can belong to one or several UCCs and can have multiple skills (competencies). A UCC can be visualized as a contact center “micro service”. Customers can utilize one UCC (e.g. a global helpdesk), a few UCC’s (e.g. for each department or regional office) or hundreds of UCC’s (e.g. for each bed at a hospital). They are interconnected and can all be managed from one central location. templates)	8.3.0.0	(Recommended version for enhancements below). Upgrading requires careful consideration and planning, Learn More
Power BI template (for Power BI Desktop)	8.8.24303.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 Enhancements

PBI	Description
113526	Adaptive card not correctly shown on initial Web Chat connection from customer. When an adaptive card was used in the initial WebChat pop-up the WebChat was not displayed correctly. This has now been fixed.
120020	Fixed an issue in DialogueManager where the file extension for media files was not correct on channel WhatsApp. Attached audio files (whether recorded with the microphone button or attached with paperclip and file search attachment) to a WhatsApp message were not marked as audio file and treated as a text file. Hence these could not be opened. now specific audio file types (.ogg, .opus, .wav) files will now be recognised and can be played back directly or downloaded.
121976	Html injection blocking by Dialogue Studio was interfering with WebChat. Enhanced security measures in the latest Dialogue Studio was blocking html injection which is a mechanism used in the Text API nodes when processing text handler messages from DialogueManager. We have now customized Dialogue Studio to allow these to be freely (but still safely) processed. WebChat should now be able to be handled also through Dialogue Studio.

PBI

Description

113526

Adaptive card not correctly shown on initial Web Chat connection from customer.

When an adaptive card was used in the initial WebChat pop-up the WebChat was not displayed correctly. This has now been fixed.

120020

Fixed an issue in DialogueManager where the file extension for media files was not correct on channel WhatsApp.

Attached audio files (whether recorded with the microphone button or attached with paperclip and file search attachment) to a WhatsApp message were not marked as audio file and treated as a text file. Hence these could not be opened. now specific audio file types (.ogg, .opus, .wav) files will now be recognised and can be played back directly or downloaded.

121976

Html injection blocking by Dialogue Studio was interfering with WebChat.

Enhanced security measures in the latest Dialogue Studio was blocking html injection which is a mechanism used in the Text API nodes when processing text handler messages from DialogueManager. We have now customized Dialogue Studio to allow these to be freely (but still safely) processed. WebChat should now be able to be handled also through Dialogue Studio.

Known Issues

Known Issues are currently under development and 'expected' to be included in the first upcoming (hotfix) release.

Please note, these items are typically still under investigation, therefore no more specific information can be given at this time. We provide this pure as high level information in advance but ask you for your patience if you may be encountering a similar issue. Please raise a regular support ticket if not done so already if you suspect a similar occurrence.

PBI	Description
123321	Dialogue Studio Say node in Dialogue Studio cannot use Custom Voice functionality. When using the Custom Voice functionality in a Say node within Dialogue Studio, an error message is displayed, and the audio fails to play.
124555	Issues with Authentication Refresh and Cache in Dialogue Studio with AnywhereNow Authentication. We have identified problems with the authentication refresh and cache mechanisms when using Dialogue Studio in combination with AnywhereNow Authentication. Specifically, Dialogue Studio fails to process the refresh token correctly, resulting in authentication failures once the initial token expires. The current workaround is to re-login in a new browser session (close the entire browser or use incognito mode) or click the log-out button in Dialogue Studio. Importantly this has no impact on the flows within Dialogue Studio.
124617	Incorrect queue positions in the Dialogue WaitingQueue node. We have identified a problem that when using Dialogue Studio, the queue position values in the output object of the Waiting Queue node are incorrect. If you are using these for a Say or Play node, the customer will hear the wrong position. This issue does not affect Queue Messages in SharePoint, only those in Dialogue Studio.
125589	Latest version of the out-of-the-box Debug nodes in Dialogue Studio consume excessive resources. We have identified a problem in the latest version of the platform underlying Dialogue Studio. When the out-of-the-box Debug node is used in your call flows an excessive amount of data may be contained in the debug body overloading the resources in your Dialogue Studio when multiple simultaneous calls are being handled. This can cause restarts or failures of your Dialogue Studio. We advise to delete your debug nodes before upgrading. As a rule of thumb, please use Debug nodes only during building and testing of your flows. Remove them afterwards for readability and performance. Also read our page on How to Disable All Debug Nodes at Once for more guidance and prior warnings about memory consumption of Debug nodes. For this current issue however disabling the Debug Nodes is not sufficient, deleting them is the only solution.
130012	Issue with "Open debug in new window" option in Dialogue Studio. We have identified a problem when the debug message button "Open in a new window" is used. This can cause restarts or failures of your Dialogue Studio. We advise to not use this option and keep using the default debug window embedded in the Dialogue Studio UI.