This document contains a list of the updates and current versions of Anywhere365 software and components.
|Ucc.Creator (SharePoint template)
|Power BI (desktop template)
|Inflight Wallboard (desktop client)
|Snapper (desktop client)
(Minimum required version for this bundle) Learn More
+ = updated in this bundle
Snapper desktop client updated to .NET 6.0. Note this requires users of Snapper to have .NET 6.0.x Desktop Runtime installed on all Windows desktops running Snapper. Prior releases of Snapper depended on components of .NET (version 3.x) that will no longer be supported by Microsoft later this year. Learn More
|Removed the bundled "Teams Presence Plugin" from Snapper.
The Snapper Teams "Presence Plugin" (to connect to Teams Graph API for collecting Presence information) was bundled with the Snapper application as a "legacy solution" to allow each Snapper to connect to graph for Teams and Presence information, at a time when the 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. Core application did not have an official Graph Presence Provider yet. A centralized Graph Presence Provider is now fully operational from the UCC service therefore the Snapper "Teams Presence Plugin" should not be used anymore, has been declared End-Of-Life and has been removed from the Installation package. (added 09/06/2023).
|Enhanced statistics to prevent incorrect value for Waiting Calls on WebWallboard.
|Additional verification there is two-way audio between the Agent and the Consultee when multiple Agents initiate a consult to the same UCC endpoint.
|Additional verification that UCC endpoints are registered successfully on startup, to handle all incoming calls accordingly.
|Introduced a feature toggle to disable Advanced Statistics and Personal Statistics shown in the Snapper client.Introduced a
The WebAgent no longer tries to retrieve CRM Customer Relationship Management, or CRM, is (usually) a software-based, data management method to deal with interactions with customers and potential customers. information when there is no CRM Services configured In DC2022.06 the WebAgent always tried to retrieve CRM information when a new conversation is opened in the WebAgent, when no CRM Service is configured this resulted in an error message.
Phone number searched in the WebAgent dialpad on Direct Routing can now be selected When searching for a phone number in the dialpad in the WebAgent and you were on a Direct Routing environment endpoint was filtered out, preventing you from clicking to call. The phone number endpoint is now visible to be clicked on.
|The right participant will be set to Primary Agent after a consult on Direct Routing. After a Consult to a Consultee, the Consultee was not set as the Primary Agent and could not perform all the interactions in the conversation. This has been addressed.
Inbound intercepted conversation no longer disappear from the WebAgent after accepting
Improved scenario for post dialogue adaptive card when conversation is started by Initial adaptive cardWhen the WebChat Dialogue was already started with an Adaptive Card, it didn't trigger the Post Dialogue Adaptive Card at the end of the conversation. Now the WebChat Dialogue can have both an Initial Adaptive Card and a Post Dialogue Adaptive Card.
Increase ME-ID Formerly known as Azure Active Directory (or Azure AD, or AAD) cache retention time The cache retention time is increased from 15 minutes to 12hours.
|Fix for unresponsive omnidir It sometimes happened that the omnidir became unresponsive and would show an error for quite some time. A fix should prevent this from happening again.
|Show correct call state for consulted transfer Fixed the issue that in consulted transfer calls both are in on-hold state in Attendant console before the second call connected, as only the first call should be on-hold
|Fix for attendant not showing calls when attendant was running for a while Now user can see the incoming calls in Attendant console even after leaving the window open for a while.
|Fix call not visible in attendant on even numbered hunt attempts (second, fourth, etc. time) When an agent was hunted for a second time, because he/she didn't pick up the first time, the call was sometimes not visible in the Attendant, and even not in webagent. This has been fixed