Release Notes - Feature Release DC2025.01

Introducing Our New Microsoft Copilot Studio Integration in Dialogue Studio: Enhanced AI for Your Customer Support.

We're thrilled to announce a significant new feature: the integration of Microsoft Copilot Studio with our Dialogue Studio. We've developed a specialized Dialogue Studio node that now makes Microsoft Copilot Studio's powerful AI capabilities directly accessible within our platform. This means your customer support team can now build more intelligent, dynamic, and personalized chatbot flows than ever before. This new integration allows your bots to learn from interactions and adapt to user needs, moving beyond static, predefined responses to significantly enhance the overall customer support experience.

For more information, see: Copilot Studio

WebAgent - Introducing Dialogue AI Assist (Powered by Deepdesk) for Voice.

We're excited to announce a new integration that empowers agents with real-time assistance during voice conversations! Agents can now leverage Deepdesk's Knowledge Assist and Agent Assist directly within voice channels. This means as calls come in through the IVR Interactive Voice Response, or IVR, is a telephone application to take orders via telephone keypad or voice through a computer. By choosing menu options the caller receives information, without the intervention of a human operator, or will be forwarded to the appropriate Agent. and connect with an agent, Deepdesk will transcribe the audio, transform it into text, and provide relevant prompts, suggestions, and triggered actions within our product via a new WebAgent UI plugin. This integration ensures agents have immediate access to crucial information and support throughout the entire call flow, enhancing their ability to assist customers efficiently.

For more information, see: Voice Channel

Persistent WebAgent Settings for Enhanced Agent Mobility.

We've introduced a new feature allowing WebAgent settings to be securely stored on the server, ensuring a consistent user experience regardless of the browser or computer an agent uses. This means agents no longer need to reconfigure their preferences or redefine their contact lists when switching environments, significantly improving convenience and efficiency. This functionality is enabled via a new SqlConnectionString setting in the WebAgentService. It is also possible to have this managed through our newly introduced Secure Vault, which automatically manage the required database infrastructure and exposes secure API endpoints for managing individual user settings, including creation, retrieval, and deletion.

For more information see: Configure user settings storage for WebAgent

Transferring a call directly to a users voicemail in now possible from WebAgent.

Adding onto the capability to configure your UCC call-flow logic (i.e. ForwardSkill) so a customer call can end up directly in a user's (Microsoft Teams) voicemail, it is now also possible for an Agent to see and select a voicemail destination directly in the contact list in WebAgent. This allows Agents to transfer a call from a customer directly to the voicemail box of another user in their organization depending on their preferred way-of-working.

See screenshots in our WebAgent Userguide: Learn More

WebAgent Now Supports Cancel Consultation and Transfer Calls While Ringing.

Agents can now cancel consultation and transfer calls (including Consultative, Blind/Direct, and Delight Consult transfers) while they are still ringing, providing greater control and flexibility during call handling. This new "Cancel" button, available in both the WebAgent and Attendant, allows agents to quickly correct misdials or abort unwanted calls before they connect, preventing unnecessary engagements. Upon cancellation, the ringing call leg will be immediately terminated, and any failure in the cancellation process will be clearly communicated to the agent through an on-screen error message.

See screenhots in our WebAgent Userguide: Learn More

Enhanced Visibility for Outbound Calls in WebAgent.

We've introduced a significant update to the WebAgent, providing both agents and supervisors with a comprehensive view of all call activities by displaying Outbound Dialer calls—including intercepted calls—in the Connected tab. Previously, only inbound calls were visible, requiring users to rely on Snapper for outbound call oversight. Now, outbound calls are clearly identifiable with a distinct icon, mirroring Snapper's functionality and ensuring a more complete overview of ongoing conversations. While agents and supervisors can now see outbound calls, specific supervisor actions for these calls will be implemented in a future update. This enhancement is a crucial step towards providing a unified and efficient call management experience directly within the WebAgent.

Enhanced WebChat Accessibility (WCAG 2.1 Compliance).

We are pleased to announce a significant improvement to the WebChat, enhancing its accessibility to meet WCAG 2.1 standards. This update ensures that the WebChat is more usable for individuals with disabilities, providing a more inclusive experience. Key enhancements include full keyboard navigability throughout the chat interface, ensuring all interactive elements can be accessed without a mouse. Additionally, all WebChat content is now compatible with screen readers, allowing users with visual impairments to understand and interact with messages and controls. We've also implemented a color palette with sufficient contrast to improve readability, and the WebChat is designed to integrate seamlessly within your website for consistent navigation.

For more information see: WCAG Compliance for WebChat and WebAgent

Further Enhanced WebChat Accessibility (WCAG 2.2 Compliance).

Building upon our recently released compliance with WCAG 2.1 guidelines, we are excited to announce that our WebChat now fully supports WCAG 2.2 standards, significantly enhancing accessibility for all users and ensuring compliance for government organizations. This crucial update introduces further improvements for a more inclusive experience: we've refined keyboard navigation and enhanced focus indicators for interactive elements throughout the chat. Furthermore, all click targets, including header buttons, attachment/emoji buttons, and adaptive card inputs, now meet a minimum size of 24x24 pixels for easier interaction. We've also implemented new keyboard controls for dragging and resizing the WebChat window (using arrow keys for movement and Shift + arrow keys for resizing), offering greater flexibility. These advancements collectively provide a more seamless, accessible, and compliant experience for everyone engaging with your WebChat.

For more information see: WCAG Compliance for WebChat and WebAgent

WebAgent - Enhanced Accessibility (WCAG 2.2 compliancy).

We are excited to announce a major enhancement to WebAgent, reinforcing our commitment to a more inclusive experience for everyone. WebAgent now adheres to the latest Web Content Accessibility Guidelines (WCAG) 2.2 standard, ensuring our WebAgent is more accessible than ever for people with disabilities. This update, built directly into the WebAgent platform, focuses on improving usability and navigation (through keyboard handling and graphical UI standards), particularly for those who rely on assistive technologies. By building to this higher standard, we empower you with a more user-friendly online experience for all your users.

For more information see: WCAG Compliance for WebChat and WebAgent

PowerBI: Improved Data Accuracy & Performance.

We've rolled out a set of PowerBI template updates to enhance data reliability and the performance of your views:

More Reliable Dialogue Data:
You'll now see more accurate information across dialogue-related features. We've fixed how skill names display (Bug 137066), ensured dates align between templates and your database (Bug 137067), and corrected SLA calculations and display, even when some data is missing (Bug 137075).

Faster & More Complete Data Views:
We've enabled incremental refresh by default for quicker data updates (Bug 137073) and resolved an issue where not all data was appearing in the Dialogue Overview (Bug 137445).

Please see our Update Guide for the PowerBI template on: Updating AnywhereNow Power BI template

Implemented retry mechanism for establishing UCC application endpoints.

In case a UCC fails to establish its system endpoints during startup (usually through trying to establish too many at once after a restart of a UCC service ). Until all configured endpoints of a UCC are operational the affected UCC is not started (other UCC's in the service may be started). Retrying establishment of the affected endpoint of that UCC will now be retried with an incremental retry time.

Enhanced Adaptive Card Capabilities.

We've updated our Adaptive Card library to version 1.3.1, significantly expanding the capabilities available to our customers within WebChat. This upgrade now fully supports Adaptive Card Schema 1.6, enabling the use of new features such as responsive layouts, icons, badges, carousels, and charts, among others. This ensures Anywhere365 users can leverage the latest design elements and functionalities to create richer and more interactive experiences, all while maintaining full compatibility with existing WebChat features and backward compatibility for Adaptive Cards Adaptive Cards are preformatted boilerplate messages that can be selected by an agent to be sent to a client. They are written using an open card exchange format that allows the developers to 'write once' and share with any compliant host application designed with older schemas (e.g., 1.0)

Improved Outbound Dialing Flexibility.

We've enhanced the WebAgent's outbound calling functionality to allow for a broader range of phone number formats. Previously, strict validation in the WebAgent prevented calls to numbers that were otherwise valid, resulting in "Uri is not a valid phone number" errors. This update loosens the WebAgent's phone number validation to align with the more flexible standards used by platforms like Microsoft Teams and Skype for Business. Validation will now primarily occur at the UCC level, ensuring more successful outbound calls while still maintaining necessary number integrity checks.

Enhanced Secure Database Connectivity to WebAgentService.

We've implemented a new, centralized library to streamline and secure database connections across our applications, enabling robust token authentication via Azure Key Vault and Service Principals. This library simplifies configuration by utilizing either an App Secret or Certificate Thumbprint for Key Vault authentication, retrieving sensitive database connection details (like server name and database name) from uniquely prefixed Key Vault entries, and automatically managing token refreshes for continuous database access. This enhancement not only bolsters security by centralizing credential management and leveraging modern authentication methods but also improves operational efficiency by standardizing database access while ensuring clear error logging for troubleshooting.

Included View of Outbound Calls in WebAgent.

Supervisors and agents now have a comprehensive view of all call activities within the WebAgent, as outbound audio queue items, including outbound dialer and interception calls, are now visible in the "Connected" tab. This enhancement provides a unified perspective of both inbound and outbound call activities by ensuring that the /queue endpoint and queue events include all audio queue items, regardless of direction. Outbound calls will only appear in the "Connected" tab once accepted, preventing them from cluttering the "Waiting" tab, and the "Requeue" action has been appropriately disabled for outbound text items to reflect their distinct workflow.

Improved WebAgentService Stability with Classification Management.

We've enhanced the WebAgentService's stability when handling complex classification configurations, specifically addressing an issue where a high number of classification levels could lead to memory overload and service unresponsiveness. To prevent system instability, the WebAgentService will now process a maximum of five unique classification levels when receiving configuration from the ListPlugin. While this ensures continued smooth operation for agents, any classifications configured beyond the fifth level will not be displayed.

Supervisor capabilities on queue item are now no longer set to true when call is not connected yet.

We've improved the supervisor experience in WebAgent by refining the visibility of the "Listen" button within the queue. Previously, this button was visible even for incoming calls that had not yet been accepted by an agent, leading to confusion. Now, the "Listen" button will only appear when a call is actively connected and being handled by an agent, ensuring supervisors have a clearer, more accurate view of live conversations and can engage with relevant calls at the appropriate time.

In WebAgent, Personal queue Display Name from CRM Customer Relationship Management, or CRM, is (usually) a software-based, data management method to deal with interactions with customers and potential customers. issue Resolved.

We have resolved a bug causing the caller's display name to no longer appear in the personal queue list/tab (only the number), when their phone number resulted in a CRM match. This has been fixed and your personal queue will now correctly display the caller's information as expected.

Call Queue Overflow Threshold Not Always Respected in Dialogue Studio Flows.

We've fixed an issue where the Overflow Threshold set (in SharePoint) for call queues, was not consistently respected when calls were routed through Dialogue Studio flows containing an "Ask and Wait" node. Previously, in specific scenarios, more calls could enter a queue than the configured threshold allowed. This update ensures that your defined queue limits are now accurately enforced, preventing unintended call overflows and improving queue management.

Wrap up was presented on Outbound calls even with the setting disabled.

The Wrap up counter is not presented anymore when the setting UseOutBoundWrapUp is False. False has always been the default value since introduction of this setting so if the setting is not added to the SharePoint Settings list it is possible that customers who have not specifically set this to true will now experience the Wrap-up counter not being displayed in WebAgent after an Outbound call. The solution then is to add the setting to your SharePoint Settings list for every UCC which needs this. See: UseOutboundWrapUp

PlayPrompt rapid loop occured when certain IVR questions were empty or misconfigured playlist.

If IVR queue or playlist audio files are empty (misconfiguration) we now do not trigger a play event anymore to prevent excessive memory consumption (which until now played multiple silent sound bytes in rapid succession).

When Dialogue Studio sends call to callback CallBack, an IVR menu feature for voice, enables the customer to confirm or leave an alternative phone number to be called back by an available agent during business hours., agent hunt is now canceled.

This solves the issue with callback messages still playing when agent is connected after an accepted hunt.

Improved performance of the SLA Scheduler implementation.

Removed superfluous verbose logging. Implemented caching of data used in SLA(only; not FIFO) algorithm. SLA scores will be cached for five seconds; this is a compromise between calculation time and the scores varying with wall-clock time.

Changed the retry policy to get users from Microsoft Graph API in case of failure.

We improved the retry mechanism for retrieving user presence information from the Microsoft Graph API. Previously, a timeout could interrupt presence synchronization for affected users until the next retry cycle, resulting in temporary gaps. The updated policy introduces four exponential retry attempts within a five-minute window, followed by ongoing retries every five minutes until successful. This enhancement reduces interruptions in presence updates caused by temporary connectivity issues.

Dialogue Studio - Waiting Queue Node - Message or audio file keeps playing after the agent accepts the call.

This fix will prevent playing audio file after the agent accepts the call, when using Waiting Queue Node in Dialogue Studio, a programming error introduced in dc2024.01f.

Dialogue Studio Action Node - Show used config visually in DS canvas.

A visual marker is now displayed below the Action Node in the Dialogue Studio canvas to indicate which UCC is being used. This marker is updated automatically after a successful call to the Action Node and will also inform if the incoming node is functioning correctly.

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. This caused a conflict with WebChat. We’ve now adjusted Dialogue Studio to safely allow this type of content, restoring the compatibility with WebChat.

Improved NodeRedPlugin 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.

Fixed an issue for WebChat where the sender changed after a skill transfer and refresh.

This release addresses an issue in WebChat where, after a skill transfer and a customer refreshing the page, all previous agent messages incorrectly displayed the currently connected agent's name instead of the original sender's name. To resolve this, the system now correctly retains and displays the AuthorName for each message, ensuring that messages from different agents consistently show the name of the agent who originally sent them, even after a page refresh.

Duplicate setting names with same scope names caused thrown exceptions in the dialogue providers.

We've resolved a critical issue where a provider would fail to start if a configuration "setting" was defined more than once in the SharePoint configuration page. This previously caused an "An item with the same key has already been added" error, which disabled the provider and could block functionalities like sending WebChat messages. The system now correctly ignores duplicate settings, processing only the first instance it encounters and logging a warning for any others. This ensures the DialogueProvider starts reliably and works as normal, maintaining system stability.

Agent Display Names Now Correctly Shown in WebChat Transcripts.

We've fixed an issue where WebChat conversation transcripts always showed a default agent name for messages, even when the UseAgentDisplayName setting was enabled. This made it hard for customers to see which agent sent which message, especially when multiple agents were involved in a conversation. Now, with UseAgentDisplayName set to 'True', your WebChat transcripts will correctly display each agent's unique name next to their messages, providing a much clearer and more accurate conversation record.

Adaptive Card Form Input Retention.

We've addressed an issue where customer input in adaptive card form fields was lost if the user clicked outside the WebChat window before submitting the form. Previously, if a customer was filling out a form within an adaptive card and then clicked anywhere on the webpage outside of the chat interface, reopening the chat would show an empty form. This has been corrected; now, customer input in adaptive card forms will be retained even if the user navigates away from the chat window momentarily, ensuring a smoother and more persistent user experience.

Improved File Upload Handling in WebChat.

We've resolved a bug in WebChat where uploading multiple files with identical names would cause all but one copy to become "stuck" in the draft area, making them impossible to remove without refreshing the chat. Now, when customers upload multiple files with the same name and send the message, all copies will be successfully sent, and the draft area will be correctly cleared of all uploaded files, ensuring a smoother and more reliable file sharing experience.

WebChat Language File Loading Fix.

We've resolved an issue preventing the WebChat from loading correctly on certain websites, specifically due to an incorrect lookup for the en.json language file. Previously, the WebChat would erroneously attempt to retrieve this file from the website's host, leading to a "404 Not Found" error, while the nl.json file was correctly fetched from the cloud host. This update ensures that the en.json language file is now consistently retrieved from the designated cloud host, allowing the WebChat to load successfully and function as expected for all users.

WebChat Language File Loading Fix.

We've resolved an issue preventing the WebChat from loading correctly on certain websites, specifically due to an incorrect lookup for the en.json language file. Previously, the WebChat would erroneously attempt to retrieve this file from the website's host, leading to a "404 Not Found" error, while the nl.json file was correctly fetched from the cloud host. This update ensures that the en.json language file is now consistently retrieved from the designated cloud host, allowing the WebChat to load successfully and function as expected for all users.

WebChat theming for light and dark mode were dysfunctional.

Previously:
Changing the Light theme on a deployment with dc2024.01f/g > Nothing changed.
Changing the Dark theme on a deployment with dc2024.01f/g > Changed the display of the Light theme.

We have now corrected this to the intended behavior.

Improved Attachment List Performance in WebChat.

We have resolved an issue where the attachment list in the Webchat was not updating efficiently, ensuring the repeater now receives the correct state comparer path for proper model updates and allowing for significantly improved list update efficiency.

Prevent Multiple Submissions of Initial Adaptive Card.

Previously, customers could accidentally click the submit button twice, resulting in duplicate submissions. This issue could cause stale conversations and redundant messages in the database. We have now resolved this problem to ensure a smoother user experience.

Rework on scrollable areas in WebChat.

We've released an update for WebChat that significantly improves our scrollable areas for a more stable and consistent experience across all browsers. By shifting our approach to leverage more native browser functionality, we've enhanced both performance and reliability. This update uses the browser's own engine to handle scrolling and style scrollbars, making them look and feel like a natural part of your operating system. As a result, scrollable areas now correctly auto-grow with their content and display familiar, mouse-wheel-compatible scrollbars when needed, ensuring a seamless and predictable experience everywhere.

Webchat now opens with intended size in Safari browser.

Webchat opened with a bigger size than allowed in the safari for iOS browser, we have now made sure Webchat opens in the available space also in the Safari browser.

Enhanced Inbound Call State Reliability.

We've implemented a significant improvement to the WebAgentService's handling of inbound call states, addressing a complex, race-condition-driven issue in the Core that occasionally prevented calls from being correctly marked as accepted. Previously, the system relied on a workaround involving AgentDisplayName and AgentSipAddress due to the unreliable setting of the AcceptedSince property. This update now prioritizes the AcceptedSince property to trigger state changes, while retaining the AgentDisplayName and AgentSipAddress combination as a robust fallback. This dual-condition approach drastically reduces the chance of misfires, ensuring more consistent and accurate inbound call acceptance and transfers, correct display of accepted calls in the frontend, and continued support for agents configured solely by phone number.

Enhanced Stability for Outbound Delight Conference/Transfer.

We have addressed a critical bug that could render the WebAgent unusable during outbound delight conferences when the primary agent attempted to transfer primary ownership. Previously, the system erroneously allowed the original call receiver to be selected as the new primary agent, leading to a malfunction in the WebAgentService and requiring a restart. This fix ensures that the original receiver is no longer presented as a valid option for primary agent transfer. Attempts to assign the receiver as primary will now be gracefully rejected with an appropriate error message, preventing system disruptions and maintaining WebAgent functionality for all participants, while also ensuring the original primary agent remains in the call to manage the hand-off.

Improved Primary Agent Assignment in Conferences.

We've resolved an issue in delight conference calls where, under certain race conditions, the incorrect agent was sometimes displayed as the primary agent after a transfer of ownership. Previously, a conflict could arise when the primary agent left the call and assigned a new primary, occasionally leading to inconsistent displays across different agents. This update ensures that when a primary agent leaves a multi-agent conference and designates a new primary, the intended agent is consistently and immediately recognized as the primary by all participants, providing a more accurate and reliable display of call roles within the WebAgent.

Improved Real-time Skill Updates for Countdown Calls.

We've resolved an issue where the WebAgent UI was not accurately reflecting skill changes for calls transitioning from a countdown skill to an escape skill, particularly when no agents were available to be hunted. Previously, agents and supervisors would not see the queue item's skill update in real-time, leading to outdated information. This fix ensures that a conversationchanged event is now correctly sent to the frontend when this skill transition occurs, guaranteeing that the WebAgent always displays the most current skill for such calls.

Fixed an issue where the system threw an error when saving voicemail call classification.

We've resolved an issue preventing successful classification of calls handled by the Voicemail Dialer. Previously, agents encountered an error when attempting to classify these calls in WebAgent, due to the attendantcurrentlyhuntingevent being prematurely removed. With this fix, the system now correctly maintains the hunting event throughout the voicemail handling process. Agents can now reliably classify voicemail calls after receiving, during handling, and even if removed while processing a voicemail from the UCC, ensuring accurate reporting and seamless workflow.

WebAgent CRM Dynamics365 Case search irregularity resolved.

We've resolved a bug affecting the Cases search functionality. Previously, when a contact was selected, searching for cases would incorrectly display all cases associated with that contact, rather than filtering results based on the search query. Now, the Cases search will accurately filter and display only the relevant cases, regardless of whether a contact is selected, ensuring you always see precise results.

In WebAgent with CRM service AfasProfit phonenumber based contacts search now works also without adding 'tel:' in front.

We've enhanced the Contact functionality within AfasProfit. You can now search for contacts using just a phone number, without needing to prefix it with 'tel:'. This improvement streamlines your search process, ensuring contacts are retrieved correctly and more efficiently.

CrmService - Capabilities and Description endpoints return 409 Error: Conflict when the config file is missing

We've addressed an issue where missing CRM configuration files incorrectly caused the CRM's capabilities and description endpoints to return a 409 Conflict error. Now, even if a CRM configuration file is absent, these endpoints will correctly return a 200 OK status, ensuring that basic CRM information remains accessible and preventing unnecessary errors. This improvement applies to all CRM integrations.

CrmService - Bullhorn case search now also supports partial search.

We've now included partial word search in the search capabilities of Bullhorn when searching for cases. This improvement should streamline your search process, ensuring cases are retrieved correctly and more efficiently.

Snapper - SharePoint App Secret field for Screen Recording Settings can now be emptied.

In the Snapper application the field for storing the Client Secret, for application access to a SharePoint library, could not be emptied after a value had been populated.This can now be deleted to disable the screenrecording functionality without having to uninstall and re-install a Snapper from scratch.

Snapper- Allow AutoAnswer Shortcut to be configured.

Microsoft has announced they will make the keyboard shortcuts for many used features of Teams client configurable to adhere to your Application preferences. A conflicting shortcut was introduced (Ctrl+Shift+s) which was used for accepting incoming Teams Audio calls, and simultaneously the embedded Browser screen capture functionality of Edge browser. To get around this, Microsoft is suggesting to make all Teams action shortcut key combinations configurable to get around this and similar issues. We have prepared our Snapper application to make the Accept Audio Call shortcut key also configurable in the Settings. We mimic that key combination when Snapper detects an inbound Teams Toast A toast is a pop-up instant message or audio call notification the user receives on his desktop. for an Audio call to act as an Auto Answer for calls.

A new text Dialogue in WebAgent with an existing contact showed Finish flag button before accepting the hunt.

When a new conversation was received from a previously known contact, an agent would be hunted and the finish flag (intended to only be shown and activate at the end of a conversation) would be shown in the Agents WebAgent before accepting the hunt. After the accepting the hunt the WebAgent buttons work and show up as designed.

We now do not show the Finish button where it shouldn't be.

Addressing Email Recipient Input Issue in WebAgent, now capitalization has no effect anymore.

We've resolved an intermittent issue in WebAgent where adding a customer's email address as a recipient would fail if the email address began with a capital letter. Previously, agents experienced difficulty adding contacts, often leading them to resort to Outlook. Our investigation revealed that the system's generic search results were not populating correctly for email addresses starting with a capital letter when no existing contact matched, preventing the "+ " button from functioning. With this fix, WebAgent will now correctly process email addresses regardless of capitalization (e.g., "Someuser@domain.com" or "sOmeuser@domain.com"), ensuring a smoother experience when adding recipients.

WebAgent CTI Framework email conversation to activity enhancement.

The CTI Framework will now close an earlier created (email) activity in the connected CRM if a new activity is noticed. As example, in an email conversation with a customer, any replies to and forth will be stored as separate activities in the CRM system (with corresponding timestamps etc.) Previously the activities were not actively "completed" by our CTI. This is now done for our CTI integrations with Dynamics 365, Salesforce, Servicenow and SAPC4C.

Supervisor Call Monitoring Activity Now Added For DaVinci CTI WebAgent Integration.

We've resolved a bug where an activity was not being created in the CRM system when a supervisor started listening to a call in WebAgent. Previously, this oversight meant interactions in DaVinci and SAP CRM remained open indefinitely. Now, when a supervisor begins monitoring a call, an activity will be correctly created and updated in the CRM system, ensuring accurate conversation status reflection.

CTI for DaVinci WebAgent integration does now closes activity after a consult transfer.

Previously when a consult transfer was done and completed by an initial agent, the activity for initial agent in DaVinci was never completed and registered in DaVinci as still ongoing even after the initial agent left the conversation. We now complete this activity.

WebAgent - Memory leak when adding/removing conversation fixed.

We have fixed an improper WebAgent memory cache handling procedure (i.e a memory leak) which occurred after each end of a conversation. This should now reduce ongoing memory consumption even after multiple conversations during daily use in WebAgent.

Ucc.Creator SharePoint Template - German translation file issue.

Installation of a UCC Site using the Ucc.Creator template with the German language selected filled an incomplete "Settings" list. This should now generate a completely filled "Settings" list.

Ucc.Creator Outbound Dialer Data Display inconsistent when the 'OutboundDialer' list had more then 5000 items.

Previously, the Outbound Dialer section would not show correct data when the 'OutboundDialer' list in SharePoint contained more than 5000 items. This has been fixed, and the Outbound Dialer section in the portal will now accurately display data regardless of the number of items in the 'OutboundDialer' list.

Ucc.Creator Routing Rule Skill Selection Fix for Non-English Browsers.

We've resolved an issue impacting UCC routing rule configurations when using a browser with a non-English language (such as Dutch) as its default. Previously, editing a routing rule under these conditions would incorrectly revert the selected skill to the first item in the list, even if a different skill had been previously chosen and saved. This update ensures that the skill selection in routing rules now functions correctly and retains the intended value, regardless of the browser's default language settings.