For consistency with the Call Control gadget could be desirable to fetch the display names configured in Finesse admin "Call Variables Layout". This code snippet shows how to do that. In addition it uses an array to list the variables that should not be displayed, for code conciseness. Note that code is not optimized (the map is rebuilt for each call), and only the differences with the sample script are summarily listed. const hiddenVarNames = ['dialedNumber', 'callType', 'DNIS', 'wrapUpReason', 'queueNumber', 'queueName', 'outboundClassification', 'mediaId', 'user.layout']; var layoutsCollection   ... display routine {  // gets applicable layout  if (typeof callVars['user.layout'] !== 'undefined') {   for (let layoutId in layoutsCollection) {   if (layoutsCollection[layoutId].getName() === callVars['user.layout']) {    let ld = layoutsCollection[layoutId].getData();    // now build the object    var callVarDisplayNames = {};    callVarDisplayNames[ld.header.mediaProperty] = ld.header.displayName;    for (let c of ld.columns) {     for (let r of c) {      callVarDisplayNames[r.mediaProperty] = r.displayName;     }    }    break;   }  }  // display callVariables which are not null or hidden names  for (let callVarName in callVars) {   for (let hiddenVar of hiddenVarNames) {    if (callVarName === hiddenVar || callVars[callVarName] === null) {     callVarName = null;     break;    }   }   if (callVarName) {    var displayName = callVarDisplayNames[callVarName] || callVarName;    html += displayName + ' ' + callVars[callVarName] + '<br>';   }  } } _handleLayoutsLoad = function() { layoutsCollection = layouts.getCollection(); } _handleUserLoad = function (userevent) {  layouts = user.getMediaPropertiesLayouts({ onLoad : _handleLayoutsLoad }); }   ... View more

Yes I'm running ES2 Active Master Version: 11.6.1.10000-51 Active Version Installed Software Options: ciscouccx.11x.CSCvj74116-chrome67-ET.cop ciscouccx.1161.ES02.24.cop uccx-language-pack_26-11.5.1.10000-1.cop The issue that I have is the first one described in my OP: UI settings doesn't appear and Finesse tries to load an external resource script. The other one (SSL error) is of no concern to me and perhaps would be better to discuss it separately. ... View more

Just to be clear. In the screenshot above, the "mixed content" error is related to a gadget using <UserPrefs>. If one remove that in the XML, the error goes away. The "failed resource" error happens, at least for me, as long there is any 3rd party gadget configured in Team Resources. ... View more

Yes. I've also tried a "dummy" gadget without init function, and still happens. ... View more

Thank you Denise. What about the other issue - SSL on port 8082? Doesn't seem to cause any problem, but it would be nice to have an error free console. ... View more

I was able to reproduce your issue and looks like you are hitting a bug ( CSCvn92810). This will be fixed in 12.0 ES1. Denise, FYI the above bug can't been seen by the public - and interested developers.   Paolo ... View more

Hi Denise, thank you for your reply. Here's the button element inspection, as well the errors logged. As mentioned I'm using Chrome (latest 64-bits on Win). The existence of a settings UI is  summarily described in the Developer Guide. The <UserPrefs> section defines controls that allow users to specify settings for the gadget. For example, a personalized greeting gadget might provide a text field for users to specify their names. It describes the user input fields that are turned into user interface controls when the gadget runs. User preferences are stored persistently. ... View more

What release version of 3.1 are you running for that trace, as I get similar results to the others above, in that it stops working when client set to TLS1.1 so I wondered if a certain versions of 3.1 worked whilst others didn't.   No. AnyConnect, any version, do adapt to the Windows version running. Newest OS versions prevent obsolete TLS versions to be negotiated. ... View more

That is wrong. See Wireshark capture of Client Hello from AnyConnect 3.1.   TLSv1.1 Record Layer: Handshake Protocol: Client Hello Content Type: Handshake (22) Version: TLS 1.1 (0x0302) Length: 99 Handshake Protocol: Client Hello Handshake Type: Client Hello (1) Length: 95 Version: TLS 1.1 (0x0302) Random: 5aad3dc8639ca8ea4944bc71e363602801a4106d5621fe67... Session ID Length: 0 Cipher Suites Length: 14 Cipher Suites (7 suites) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a) Compression Methods Length: 1 Compression Methods (1 method) Extensions Length: 40 Extension: status_request (len=5) Extension: supported_groups (len=8) Extension: ec_point_formats (len=2) Extension: SessionTicket TLS (len=0) Extension: extended_master_secret (len=0) Extension: renegotiation_info (len=1) ... View more

I think what happened is that I had uploaded the gadget on the master only, and for a period of time the HA system tried to fetch it from the slave. While the FQDN config was pointing to the master, so it was fine. As a side note, there have been a couple more things that didn't worked right after the upgrade: Needed to set again Supervisors permission for dashboards permalinks. We use custom dashboards, something in the data "formatting" has changed, so our application had to be corrected accordingly. Thanks again, Paolo. ... View more