On Premises

Release Notes - Hotfix release DC2024.02c

Announcement

DC2024.02c has been made GA on October 20th, 2025.

Important

When upgrading from an older bundle A bundle is a fixed combination of our software platform elements of very specific versions. These are designed and tested to optimally work together to assure their intended function and interoperability., be sure to check out the What's New page for a concise list of all new features, behavioral changes and important updates you need to consider or execute, before upgrading!

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

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.1

(Recommended version for this bundle)
Update UCC Creator

Power BI template (for Power BI Desktop)

8.10.250327.01

(Minimum required version for this bundle)
Updating AnywhereNow Power BI template

Inflight Wallboard (desktop client)

6.5.8

 
Snapper (desktop client)

8.8.2

(Minimum required version for this bundle)
Update Snapper

Feature Enhancements

PBI Description
136778

Accurate AgentAccepted timestamps for transferred calls

Previously, when an audio call was transferred to another skill/agent, the AgentAccepted event in UCC_CallDetail could reflect the first agent’s acceptance time for subsequent agents. The event now captures the actual acceptance time per agent during transfers, improving the precision of answer-time reporting and audits.

Data note: Existing historical records are unchanged; new events use the corrected timestamp

139916

Outbound dialer campaigns: all invites processed under load

Under high load (e.g., ~300 agents), some campaign invites were left unprocessed until a UCC restart. We’ve improved dialer coordination to prevent multiple dialers from “stealing” the same invite, ensuring every invite is actually called even in large batches.

139909

WebAgent with OIDC: reliable SignalR handshake (no more 404 on long tokens)

Some agents saw SignalR handshakes fail with a 404 and the client falling back to long polling when OIDC was enabled and the auth data made the query string exceed typical limits. The handshake now succeeds even with long authentication parameters, restoring stable WebSocket connections.

135829

WebAgent with Salesforce CTI after transfer: Agent B gets active controls

After a blind or consult transfer, Agent B sometimes didn’t receive the “accepted” signal in the Salesforce CTI plugin, leaving CTI/CRM Customer Relationship Management, or CRM, is (usually) a software-based, data management method to deal with interactions with customers and potential customers. buttons inactive. We’ve removed redundant checks in WebAgent so transferred conversations trigger the same CTI state as initial ones.

134776

Improved Dialogue Studio stability resiliency to unsynchronized events.

We have improved our code to handle more unexpected exceptions which could ultimately lead to a crash of the plugin or even the UCC. We now catch off more unhandled exceptions and mark them in a manner that our Core can effectively process or ignore them.

Known Issues

Known Issues are currently under development and 'expected' to be included in the first upcoming 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
133684

WebChat conversations started with an adaptive card have reversed or inaccurate sender and provider

Adaptive Card–started WebChat writes WebChatSipUri into CustomerUri; standard.customerUri / standard.customerName aren’t honored, causing reversed/inaccurate sender and receiver attribution.

Impact: Power BI customer dimension; PluginFlow SenderUri; WebAgent Queue attribution; WebAgent CRM Service & CTI searches.