What’s Fixed?
This Hotfix addresses the following issues:
Issue Description | Symptoms | Resolution |
---|---|---|
Removed the ability to add the variable <<DestinationQueues>> to the interflow activity and the ability to paste a transfer activity into an inqueue workflow as both of these are not valid | When transfer activity with destination as <<DestinationQueues>> is pasted in the Email Inqueue workflow, The IVQ counts mismatch with CCC and Ignite. | Validation error is added if transfer activity is pasted to the Email Inqueue workflow. Removed the variable <<DestinationQueues>> from the variables list for Setting Destination in the Email Inqueue Workflow |
Fix issue where certain emails with certain attachments could cause MiCCSDK cpu and RAM usage to spike | When the system is processing emails that have pdf, or word doc attachments we would see exceptions thrown complaining of an incorrect Tika dll version | The correct dll version has been incorporated into this fix, thus eliminating the exceptions. |
Fixed issue where supervisors could still see all web callbacks | Have two different queues with two different agent groups both with one different agent (both employees with May see all queues disabled) In a voice inbound workflow have a two callback requests one to first callback queue as a destination other to the other one. Now place a callback request to Queue A where is a member Agent A. Once the callback is set it will show in the web ignite callback widget when logged as Agent A. Now place a second callback request to Queue B where Agent B is a member however as the callback is set it will still appear in Agent A callback widget. If Agent A presses F5 (reloads the Web Ignite page) the second request will no longer appear in the widget, however once the status of the second callback changes (let say that the Agent B requeues it) it will appear again in Agents A callback widget. | The api call that was missing the additional check has been corrected. |
Fixed issue with restoring a backup using Lab Restore option that has an OAuth type mail server where it wasn’t pacifying the connection data | When you do a “Lab Restore” with a 9.4 or newer backup that has an OAuth SMTP server defined in it, we were not pacifying the data on this mail server thus it would try to connect after restore. | We now pacify these mail servers correctly on Lab Restore of a backup. |
Fixed issue with OAuth based mail servers not reloading in storage service when modified in YSE | OAuth mail server changes were not being reflected in storage service when saving changes to them in YSE | Storage service now reloads the OAuth mail server when it detects changes made to relevant properties via YSE |
Fixed issue that could occur when using Excel based data sources in querying them from IVR query activity | IVR DB Query failing with error 'External table is not in the expected format' | Added some threading protection to guard against race conditions. |
Fixed issues with emails not being duplicated properly in the case where multiple queues and set to be delivered multiple email addresses \ aliases | Emails routed to wrong queues and <<DestinationQueues>> set with wrong email queue values Emails Getting duplicated when an email with ToAddress which is not configured as an alias or from address along with a ToAddress from another mail server. Emails not getting routed to all queues configured with same email alias, only sends to first found Queue | Emails get cloned properly and routed to correct <<DestinationQueues>>which are mentioned in the To/CC addresses. If any email comes in with To address which is not configured in MICC-B , it gets ignored and duplication does not happen. |
Cumulative Fixes Included
The following previous hotfixes are also included in this hotfix:
Hotfix | Description | Link |
---|---|---|
KB536902 | Fixes: Unable to save employee added via Pick user from Active directory and Email processing fixes and improvements | |
KB536401 | Fixes for Microsoft Exchange OAuth mail server connections and Web Ignite Callback Widget issue |
Environment
MiContact Center Business
Installation
This Hotfix is to be installed onto MiContact Center Business version 9.4.0.0
Go to https://www.mitel.com
Click the Login button.
Click the Sign in button under MiAccess.
On the left, select the Software Download Center.
Expand the tree to MiContact Center Business and then down to MiContact Center Business 9.4.0.0 and 9.4.0.0 HotFixes.
Download the "MiCC Hotfix KB537372.exe" Hotfix to the MiContact Center server.
Double-click the MiCC HotFix KB537372.exe and follow the on-screen prompts.
Wait for the repackager and auto-updates to complete.
NOTE: Applying this Hotfix will restart the MiContact Center services. To avoid service interruption we recommend applying the update after hours or during a scheduled maintenance window.