I think I found a bug that matches this.  Take a look at CSCue59553.  It affects these non-reactive debugs.  It also mentions affecting applications without a trigger.  I've still got a TAC case open on this waiting for confirmation, but I think this will be our issue.  Symptom: 1. When using the non-reactive debugging feature of the Unified Contact Center Express Editor to step through a Document step, such as "Create XML Document", it fails to execute showing the following error message: "Source Document variable "start" has null value" 2. When calling an Application bound to a script containing a Document step, such as "Create XML Document" from another script with the 'Trigger Application' step, the XML object is not populated and data from the XML file is not processed. Conditions: Unified Contact Center Express versions with the fix for CSCuc15580 (versions: 8.5(1)SU4+). As part of the fix for CSCuc15580, an active Trigger (ContactApplicationTrigger) was made compulsory to access the XML document data using Create XML Document step. Non-reactively debugging or calling an Application without a Trigger from the 'Trigger Application' step does not product a ContactApplicationTrigger. Workaround: 1. Use Reactive Debugging from the UCCX Editor instead. 2. Redirect the call from the originating script to the destination Application referencing the script that contains the Document steps instead of using the 'Trigger Application' step. Symptom: 1. When using the non-reactive debugging feature of the Unified Contact Center Express Editor to step through a Document step, such as "Create XML Document", it fails to execute showing the following error message: "Source Document variable "start" has null value" 2. When calling an Application bound to a script containing a Document step, such as "Create XML Document" from another script with the 'Trigger Application' step, the XML object is not populated and data from the XML file is not processed. Conditions: Unified Contact Center Express versions with the fix for CSCuc15580 (versions: 8.5(1)SU4+). As part of the fix for CSCuc15580, an active Trigger (ContactApplicationTrigger) was made compulsory to access the XML document data using Create XML Document step. Non-reactively debugging or calling an Application without a Trigger from the 'Trigger Application' step does not product a ContactApplicationTrigger. Workaround: 1. Use Reactive Debugging from the UCCX Editor instead. 2. Redirect the call from the originating script to the destination Application referencing the script that contains the Document steps instead of using the 'Trigger Application' step. ... View more

The Calls in Queue is displayed as a report within CAD.  Agents would have to click on the  Reports icon (or Ctrl-Q) then select Contact Service Queue Statistics. If you want more detail, one workaround is to use a wallboard.  There are some opensource ones available (search the forums).  If you have a web-based wallboard setup, you can customize it, then display it as a tab within the CAD integrated browser.  That way your agents always see it (without clicking), and you can show any data you want. I don't believe you can modify the Supervisor Desktop icons. ... View more

Hello Pavan, thanks for the reply. Yes -- we do use Citrix (XenApp 6.5) to launch the browser (Server OS is W2K8 R2).   Glad it's already a known issue, thanks. I've just tested IE (8 and 10) and Firefox locally and it seems to perform much better.  That's not an option on our standard corporate image, but will be a sufficient workaround. And thanks for the update on the enhancement request.  I'll be looking forward to that in a future release. Tom ... View more