PROBLEM

This HotFix addresses three issues:

• Changing default presence status for agent in agent group in YSE doesn't save or change
• Email messages were being sent to FailedRoute due to handling of requeues
• Email messages were being sent to FailedRoute if the ticket or conversation ID contained the word "not". 

RESOLUTION

This HotFix is to be applied onto MiContact Center Version 8.0.1.0 with KB341275, and KB375344.

1. Ensure that KB341275 is installed.
2. Ensure that KB375344 is installed.
3. Download the attached KB389019.EXE to the MiContact Center server.
4. Double-click the KB389019.EXE file and follow the on-screen prompts.

NOTE: Installing this HotFix will restart the Mitel services.  In order to avoid service interruption we recommend applying this update after hours or during a scheduled maintenance window.

APPLIES TO

 MiCC 8.0.1.0

Problem

Workforce Scheduling clients cannot connect to the server

Symptoms

When opening the WFS client you will see the error:
“A network-related or instance-specific error occurred while establishing a connection to the SQL server. The server was not found or not accessible.”

Cause

The Server and clients may not be on the same domain or for whatever reason the clients cannot resolve the computer name of the server, possibly because of a DNS issue.

Resolution

The WFS clients pull down SQL information from the connection string on the server inside the registry.  If the clients cannot resolve this computer name, we need to do one of the following workarounds:

NOTE:  Do not perform step 2 on the MiContact Center server.  This is for client machines only, and can cause serious issues with real-time and softphone control if performed on the server itself.

1. Edit the connection string on the server to use the IP instead of the computer name.

• On the server, type regedit in the Run box then press Enter
• Expand the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\prairieFyre Software Inc\CCM\Client
• Double click the ConnectionString key on the right and modify the DataSource
• You should see something in the string like 'Data Source=CCM\SQLEXPRESS'
• Replace the computer name with the IP address of the server
• In this example, after the change it would look like 'Data Source=192.168.1.100\SQLEXPRESS'

• Type regedit in the RUN box to open the registry editor.
• expand the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\prairieFyre Software Inc\CCM\Common
• Create a new String Value called CCSConnectionString and set the value to the same as in step #1

• With notepad, edit the hosts file located in "c:\WINDOWS\system32\drivers\etc\hosts"
• Add the server IP address and server computer name on a new line below the loopback (127.0.0.1   localhost)
• Example: 192.168.1.100     CCM

Applies To

CCM version 5.6 and newer

INFORMATION

To use SSL with a self signed certificate a binding for the port most be added using IIS Manager.  Use the following steps:
1.  Open the Internet Information Service (IIS) Manager.
2.  Expand the list at your PC name.
3.  Expand the list at Sites.
4.  Right-click Default Web Site.
5.  From the menu list select Edit Bindings.
6.  In the Site Bindings window select the Add button.
7.  From the Type drop down menu select https.
8.  In the IP address edit box, leave everything All Unassigned.
9.  In the Port edit box enter 443.
10. From the SSL certificate drop down menu select your certificate from and internal or external certificate authority.
11. Click the OK button.  The Site Bindings window should now include your new binding.
12. Click the Close button.
13. In the File menu select Exit to leave the IIS Manager.
14. Restart the IIS service by going to a Command Prompt and entering IISRESET.

APPLIES TO

7.X

PROBLEM

This HotFix resolves the following issues:

• Agent Whisper unable to read the DNIS variable for a call
• Agent Whisper unable to read the DNIS variable for a call when transferred to queue via a System Speed Call
• When the first agent in a queue requeues the call, the Agent Whisper did not play when the second agent answered.
• Agent Shift by period report was occasionally missing time due to a RecallHeldParty MiTAI event

RESOLUTION

This HotFix is to be installed onto MiContact Center Business Version 8.1.2.0. 

1. Download the attached KB392414.EXE to the MiContact Center server.
2. Double-click the KB392414.EXE file and follow the on-screen prompts.
3. Go to [InstallDir]\Services\ConfigService\ .
4. Launch the GlobalAppSettingsEditor.exe.
5. Fill in the following information:

• Application: RoutingInboundService.exe
• SectionGroup: Mitel.Routing.Mitel.Properties.Settings
• Name: TransferDNsToSaveMediaRecordFor
• Value: Enter the system speed call numbers, separated by commas. eg: 123,124,125,126

6. Click Save.

APPLIES TO

MiCC 8.1.2.0. 

PROBLEM

The installation of a pre-requisite component fails. This can occur on the MiContact Center server or a Client installation. Not applicable to version 8.1 downloaded September 6, 2016, or later.  The correct installation file is named:  MiCC.8100.20160627.2.EXE.

SYMPTOMS

Installer log reports an error like the following:

Checksum for 'C:\Users\ADMINI~1\AppData\Local\Temp\2\chocolatey\vcredist2010\vcredist2010Install.exe' did not meet
 '66B797B3B4F99488F53C2B676610DFE9868984C779536891A8D8F73EE214BC4B' for checksum type 'md5'.

Chocolatey log (%programdata%\chocolatey\logs) reports an error like the following:

ERROR: Empty checksums are no longer allowed by default.  Please ask the maintainer to add checksums to this package.  In the meantime, if you need this package to work correctly, please enable the feature allowEmptyChecksums or provide the runtime switch --allowEmptyChecksums 

RESOLUTION

Download a new copy of the 8.1 installer from Mitel online.  Ensure the correct file name:  MiCC.8100.20160627.2.EXE

WORKAROUND (Note: some customers have reported this no longer works, in which case the Preventative Measures described below should be followed to create a new Client Component Pack.)

1. Leave the MiCC Installer Open.
2. Open a command prompt As Admin.
3. Run the following command:  cup chocolatey --force
4. Run the following command:  choco feature enable -n allowemptychecksums
5. Click Retry on the MiCC Installer.

PREVENTATIVE MEASURES

Modifications can be made to files such that the Client Component Pack (CCP) is corrected for Visual C++ 2010 Redistributable, and clients who download the repaired CCP can install successfully:

1. On the MiCC server, browse to the CCM folder, and into the PFInstaller\Supplemental folder.
2. Edit the Client Component Pack.deploy file in Notepad.
3. Search for vcredist2010, and you should find the following line: <add key="Arguments" value="vcredist2010 -source &quot;[INSTALLDIR]PreReqs;http://chocolatey.org/api/v2/&quot; -y" />
4. Modify and save the end of this line so that it reads:                  <add key="Arguments" value="vcredist2010 -source &quot;[INSTALLDIR]PreReqs;http://chocolatey.org/api/v2/&quot; -y -version 10.0.40219.1" />
     NOTE:  If you are unable to save the changes, this means that there is extra security on the file structure.  Run Notepad As Admin in order to edit the file.  If you need to do this, then you must also run CMD As Admin in step 5.
5. Browse to the CCM\PFInstaller folder in a command prompt and run "Micc.RedistPacker.exe /repackCCP" (without quotes).
     NOTE: The Command prompt will go to the next line immediately.  The MiCC.RedisPacker process can take up to 30 minutes to complete.  It will be visible in your system tray, and task manager until done.
6. This will fix the CCP, and installation on clients that download the CCP going forward should not experience this issue.

SUPPLEMENTAL

If a remote server may be installed, the Remote Server Pack deploy file (same folder location) should receive the same modification. Step 5 would then change to use /repackRSP.

APPLIES TO

MiCC 8.0.x, MiCC 8.1 downloaded prior to September 6 2016

PROBLEM

When the WFM Connector exports data, some intervals return 0KB files. 

SYMPTOMS

In the prairieFyre.WFM.Services.log file you will see warnings like the following:

Error: 2015-Apr-14 19:15:42.237 SQL Exception encountered in GetDataForPeriod: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ()

CAUSE

There is a timeout value configured in the registry that determines how long a SQL operation can take to connect or complete.  WFM uses this for the completion time.

RESOLUTION

You will need to increase the timeout period used for the SQL connection. Prior to MiContact Center version 8.x, you must change the timeout value in the system registry SQL connection string. In version 8.x of MiCC, this string is encrypted and cannot be edited. There is an independent setting for SQL timeout that was introduced in MiCC 8.0.1.0. (Note, you must upgrade to a minimum of 8.0.1.0 to leverage the Global Application Setting timeout value).

Procedure for version 7.x

NOTE: This solution requires a registry edit.  Please use caution when making changes.

1. On the MiContact Center server open the registry editor regedit.exe .
2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\PrairieFyre Software Inc\CCM\Enterprise\ .
3. Right click on ConnectionString and select Modify.

• The contents will look like:  Persist Security Info=false;Integrated Security=SSPI;Data Source=.\SQLEXPRESS;Initial Catalog=CCMData;Connect Timeout=30;
• Modify the Connect Timeout=##; value at the end.  We recommend incrementing the timeout value by 30 (measured in seconds) and testing until you are no longer seeing 0KB files.

• NOTE: If you are using the prairieFyre.WFM.Utilities.HistoricalDataRecollector.exe application instead, you will need to restart the program for the settings to take effect.

1. Launch the GlobalAppSettingEditor.exe located in the server's [InstallDir]\Services\ConfigService folder.
2. Enter the following:
   
   Application:prairieFyre.WFM.Service.exe
   SectionGroup:prairieFyre.WFM.Controller.Common.Properties.Settings 
   Name: SQLConnectionTimeoutSeconds
   Value: (the timeout period in seconds. Default is 30) 
   Description: (you must enter a value here to save)
   
3. Click the OK button. It can take up to 30 seconds for the save to complete.
4. Go to services.msc .
5. Click on the prairieFyre Workforce Management Service and Restart.

APPLIES TO

MiCC Version 7.X and newer 

PROBLEM

When IVR initiates a callback it will determine whether the call requires a 1 for long-distance, or 011 for international based on the saved callback number.  If the server resides in a region where multiple area codes are dialed as local, this can result in misdialed numbers as the 1 for long distance is added to the phone number. 

SYMPTOMS

In the device log for the outbound port you will see an error like the following:

Error: 2016-Apr-22 11:46:34.489   Mitel.Routing.Mitel.Implementation.ConferenceImplementation - Received CallFailedEvent due to Invalid Destination [16151231234]. (4006 - 10.47.34.85)

In the above example, 615 is considered local by the telephone service provider, however since 613 was configured as the local area code in YourSite Explorer the destination has included a leading 1 for a long distance call. 

WORKAROUND

There are two ways of working around this limitation.  The first would be to program the ARS Routing rules in your MiVoice Business to correct the outbound dialing digits after IVR has added the leading 1.  This is not the ideal solution in most cases since it requires a large amount of programming on the MiVoice Business.

The recommended workaround is to use a Variable Compare and Set Variable to determine the outbound digits needed.

1. Open YourSite Explorer and log in as a System Administrator account.
2. Click Variables, and then click the Add button at the top.
3. Call the new variable something intuitive such as ModifiedCallbackNumber. 
4. Add a description so others can see the purpose of the variable.
5. Set the Variable Type to Number.
6. On the left, open the IVR Routing section.  Select Subroutines.
7. Open the Outbound subroutine needing modification. 

• NOTE: If you use multiple forms of outbound callbacks you may need to add these changes to a voice, web, and abandon callback subroutine.

• NOTE:  This final variable compare ensures that 10 digit numbers have the digit for outbound dialing added, while other numbers (internal, for instance) will not.

What this means is:

• IF the callback number provided starts with any of the area codes you specified, the system will not attempt to evaluate whether it is long distance and will dial it as provided, adding a leading 8 if it is a 10-digit number.
• ELSE if the callback number provided does not start with any of the area codes you specified, the system will evaluate it as normal and append the 1 for long distance if needed.

APPLIES TO

MiCC IVR all versions

PROBLEM

In some cases old SMDR records could cause the Enterprise Server service to fall into an infinite loop, resulting in poor performance or triggering service restarts by the Server Monitoring Agent. 

SYMPTOMS

The Enterprise Server log may show a line like the following:

Info: 2017-Jan-06 12:00:44.912   EnterpriseServer::Stop()    at System.String.EqualsHelper(String strA, String strB)
   at prairieFyre.BAL.DataAnalysis.Engine.SMDRRecord.IsQueueCountPegged(Device device)

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.1.0.

1. Ensure that KB377624 is installed.
2. Ensure that KB386779 is installed.
3. Download the attached KB393158.EXE to the MiContact Center server.
4. Double-click KB393158.EXE and follow the on-screen prompts. 

APPLIES TO

MiContact Center Business 8.1.1.0 

PROBLEM

When opening a Callback monitor in Contact Center Client, the monitor will only display callbacks once their status is updated.  As a result, pre-existing callbacks will not be visible until something forces a status change, such as an attempted routing of the callback. 

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.2.0.

1. Download the attached KB393574.EXE to the MiContact Center server.
2. Double-click the KB393574.EXE and follow the on-screen prompts.

NOTE: Installing 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.

APPLIES TO

MiCC 8.1.2.0 

PROBLEM

When selecting an email in ignite, it is taking 30 to 40 seconds for that email to load.

This HotFix also addresses an issue where Junking on email resulted in Junked an additional message. 

RESOLUTION

This HotFix is to be applied onto MiContact Center Business version 8.1.1.0.

1. Download the attached KB393054.EXE file to the MiContact Center server. 
2. Double-click the KB393054.EXE file and follow the on-screen prompts.

NOTE: Installing this HotFix will restart the MiCC services.  To avoid service interruption we recommend applying this update after hours or during a scheduled maintenance window.

APPLIES TO

 MiCC 8.1.1.0

PROBLEM

Messages are sent into a queue, picked from that queue and transferred back before being picked again by an agent.  This results in Emails being sent to a FailedRoute state with the reason code of Hard Audit. 

RESOLUTION

This HotFix is to be applied onto MiContact Center Business version 8.1.2.0. 

1. Download the attached KB393073.EXE file to the MiContact Center server.
2. Double-click the KB393073.EXE and follow the on-screen prompts.

NOTE: Installing this hotfix will restart the MiContact Center services.  In order to avoid service interruptions we recommend applying the update after hours or during a scheduled maintenance window.

APPLIES TO

MiCC 8.1.2.0 

PROBLEM

This HotFix addresses two issues:

• Agent Greeting ports intermittently being unable to receive the DNIS or ANI values from the call being tapped. 
• A configuration option has been added to prevent timing errors.
• Extra logging has been added to further diagnose if needed into a new log file:  prairieFyre.Services.EnterpriseServer - InQueueServer.log
• Agent Greeting ports not properly releasing calls if the call is requeued 

RESOLUTION

This HotFix is to be applied onto MiContact Center Business version 8.1.2.0. 

APPLIES TO

MiCC 8.1.2.0 

INFORMATION

In a high-volume multimedia environment, the default ElasticSearch maximum memory size may be insufficient, and the service may restart on occasion, causing an alarm ALM0155.  Use the following steps to increase this maximum:
1.  Open a DOS command prompt window.
2.  Run the following command: C:\ProgramData\chocolatey\lib\elasticsearch\tools\elasticsearch-1.4.1\bin\service.bat manager
3.  In the Java tab, increase the "Maximum memory pool" value (2048 for 2GB limit, 3072 for 3GB limit, etc...). Feel free to set it as high as half the system memory - it will not immediately max out, but will only grow as needed.
4.  Press OK, then restart the ElasticSearch service.

APPLIES TO

8.X

Keywords: Elastic ElasticSearch memory ALM0155

PROBLEM

This HotFix resolves two issues:

• When the primary IVR fails, there is a 40 second execution timeout when querying the MiCCSDK
• IVR ports reporting that they are in a Ring No Answer state after supervised transfers 

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.0.0.

1. Download the attached KB393516.EXE to the MiContact Center server.
2. Double-click the KB393516.EXE and follow the on-screen prompts.

NOTE: Installing this HotFix will restart the Mitel services.  To avoid service interruption we recommend applying the update after hours or during a scheduled maintenance window. 

APPLIES TO

MiCC 8.1.0.0 

INFORMATION

NOTE:  Presently the only download location for MiCntact Center Business 8.1.0.1 or BluStar is via the Knowledge Management System available on connect.mitel.com.  It will be added to Mitel Online when 8.1.3.0 releases in July.

To enable CTI server capabilities, MiVoice Office 400 and MiVoice 5000 customers must install BluStar Server on the Enterprise Server, collocated with MiContact Center software. This article describes how to download and configure the BluStar Server for MiContact Center implementations.

We recommend you install BluStar Server prior to installing MiContact Center on the Enterprise Server. Once you have installed both the BluStar Server and MiContact Center software, you set your CTI Connection string on the media server in YourSite Explorer. See the BluStar Server documentation for content related specifically to the BluStar application.

NOTE: MiContact Center Version 8.1 requires BluStar Server Version 7.2.

Before downloading and installing the BluStar Server, you must enable the Application Server Role on the Enterprise Server.

Enabling the Application Server Role

To enable the Application Server Role:

1. From the MiContact Center Server, launch the Server Manager.
2. Select Add Roles and Features.
3. Navigate to the Server Roles page and select the check box beside Application Server.
4. Navigate to Application Server role services page and select the check box beside Web Server (IIS) Support.
5. When prompted to add additional features, click Add Features.
6. Navigate to the end and wait for the process to complete.

Downloading BluStar Server software

To download BluStar Server software:

1. Log on to the Enterprise Server with a Windows administrator account.

• The account must have full administrative privileges.

• Click I Agree [Download using Software Download Manager (Recommended)] to download using the Software Download Manager.
• Click I Agree [Download using HTTP] to download using your browser.
• NOTE: If you click I Disagree, you will be unable to download the software.

Setting up BluStar Server

To set up BluStar Server:

NOTE:

• The local SQL instance that is used by MiContact Center must have Mixed-mode Authentication enabled and the SA account must be enabled and configured with a password.
• If you use MiVoice Office A400, CSTA service must be enabled on the PBX. By default, this setting is turned off. In the MiVoice Office A400 Admin page, navigate to IP Network=>CSTA service, enable it, and click Apply.

1. On the BluStar Server Setup page, pick the relevant PBX and click Next.

APPLIES TO

MiCC 8.1.0.1 and newer with SIP 

PROBLEM

This HotFix addresses multiple issues:

• In Web-Ignite a security role which blocks access to real-time monitors will also prevent account codes from being visible
• Agents are unable to set themselves in a Make Busy state after handling a multimedia item
• Web-Ignite becomes intermittently unresponsive after extended use
• Transferring to resilient queues via a virtual queue group fails
• Calls in worktimer state become stuck in Ignite inbox.  New calls continue to be delivered
• No items are listed in the Ignite history when the 'All' filter is selected
• Queue group was placed into Do Not Disturb mode, and was subsequently removed in error
• Agent state showing unknown in Web-Ignite, and agents unable to change group options
• Some IVR servers were not synchronizing configuration changes unless the RoutingInbound service was restarted
• Web-Ignite showing stale calls in the inbox
• Agent on a multimedia item sets themselves Make Busy using the Contact Center Client, but is set back to available in error
• Completed calls were intermittently showing as on hold instead of worktimer
• Resilient Hunt Groups with resilient members were becoming stuck in a Ring No Answer state

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.1.0. 

1. Download the attached KB399587.EXE file to the MiContact Center server.
2. Double-click the KB399587.EXE file and follow the on-screen prompts.
3. Allow the Repackager process to complete, and any remote IVR servers to update.

NOTE: Installing this HotFix will restart the Mitel services.  To avoid service interruption we recommend applying this update after hours or during a scheduled maintenance window.

APPLIES TO

MiCC 8.1.1.0 

PROBLEM

You find that some data is not being collected correctly by the WFM Connector. 

SYMPTOMS

Occasional agent interval data is missing from FTP data sent to WFM server. 

CAUSE

Calls which span more than two 15 minute intervals will not be included in the FTP packet since the WFM service is sending data offset only by 15 minutes. For example, a call that arrives at 12:14:59 and lasts until 12:30:01 spans three 15 minute intervals, the 12:00-12:15 interval when it arrived, the 12:15-12:30 interval that it was still occurring in, and the 12:30-12:45 interval when it ended. The 12:00-12:15 interval data was sent to the server at 12:30, so the call that began in interval one and didn't end until interval three is missed in the data upload because that upload occurred at 12:30. 

RESOLUTION

Run the historical data recollector with the -auto switch and it will recollect all interval data from the previous day and fill in the missing data.

By default, the Historical Data Recollector is found in:  [InstallDir]\Services\WFM\prairieFyre.WFM.Utilities.HistoricalDataRecollector.exe

Create a new scheduled task using the attached batch file to run one hour after nightly maintenance. By default, maintenance runs at 02:00, so schedule the task for 03:00.

NOTE: The attached batch file assumes a default [InstallDir] of C:\Program Files (x86)\prairieFyre Software Inc\CCM\ or C:\Program Files (x86)\MiContact Center\.  If you have installed to another location, you will need to edit the batch file accordingly.

NOTE: Prior to version 8.0.1.0, to rebuild AgentScoreCard (adherence) data, the Historical data recollector must be run manually and the timeframe selected must cross midnight for the day you wish to recreate the scorecard for. For example, you want to recreate the scorecard for Jan 19, 2016 - In the recollection tool, set the START DATE to 01-19-2016 and the START TIME to 23:45 then set the END DATE to 01-20-2016 at 00:15.

KNOWN LIMITATIONS: Same day WFM reports may be incomplete for the above mentioned reasons. Historical reports will be complete if data recollection is performed. 



VALIDATING DATA RECOLLECTION

1. Go to the log: [InstallDir]\Logs\DataProcessor.log.

2. There will be a log line to indicate that the service has started a summarize job:

***********************************STARTING LOGGING 2016-Apr-06 02:02:27.357***********************************

3. Then not far below, look for a line like the following to indicate what date or date range of call records it is summarizing:

Info 2016-Apr-06 02:02:32.757 Summarize process information - Summarize for 4/5/2016 starting. Start time: 4/6/2016 2:02:32 AM

4. After summarize has written to SQL you will see some log lines like:

Info 2016-Apr-06 02:03:19.721 Summarize process information - Summarize for 4/5/2016 ended. End time: 4/6/2016 2:03:19 AM; Duration: 00:00:46.9646057

Info 2016-Apr-06 02:03:19.722 Summarize process information - End time: 4/6/2016 2:03:19 AM; Duration: 00:00:47.1370509

5. If there are no errors or warnings in the logs, writing to SQL has completed at the time indicated.

6. Next look at the Historical Recollector log to ensure it did not start before the data was sent to SQL by the Data Processor Summarize. The log for the recollector is at [InstallDir]\Logs\prairieFyre.WFM.Utilities.HistoricalDataRecollector.log.

7. You will see a log line to indicate the recollector has started like this:

***********************************STARTING LOGGING 2016-Jun-02 03:12:48.940***********************************

8. You will see a log line a little lower showing the date range of data to re-send over FTP. It should be for the previous day on an automatically configured re-collection and then a log line farther down showing it has completed:

Info: 2016-Jun-02 03:12:49.298 Data collected and sent. ()

9. If there are no warnings or errors, then FTP files should havve been re-sent reflecting summarization of the previous days call records.

APPLIES TO

MiCC 6.x, 7.x, 8.x 

PROBLEM

After assigning ASR and/or TTS licenses in to the MiCC ARID in AMC, these licenses do not activate automatically. 

RESOLUTION

The process for enabling these licenses requires a manual step.  You must email NuanceRegistration@Mitel.com with the ARID, and the MAC address of the server where Nuance licensing will reside.  Once manually added, the Order Desk will email the key back to you. 

APPLIES TO

MiCC 8.X and newer 

PROBLEM

In Windows, setting the Display to 125% or greater magnification causes elements in the MiContact Center software user interface to overlap, making it difficult to properly navigate. 

In MiCC Version 6.X and 7.X this would manifest as overlapping fields, sometimes blocking your ability to click.

WORKAROUND

We recommend using the on-screen magnifying glass instead of a full-display zoom, as this does not cause layout issues in our user interface. 

NOTE: A reboot may be required after adjusting the windows display settins.

APPLIES TO

6.0.1.0 and newer 

PROBLEM

Users are unable to drag and drop files onto the Desktop Ignite window in order to attache them to an email. 

WORKAROUND

Click the Add attachment button and select the file manually. 

RESOLUTION

In order to use the drag and drop functionality in Ignite you must ensure that:

• The client computer has Internet Explorer 10 or newer.
• You are running Ignite as a normal user (This functionality does not work if you run Ignite "as administrator")

APPLIES TO

MiCC Version 7.1.3 and newer