topic Call Studio 11.0 - Web Services: WSDL File loads but options remain disabled in Contact Center

Call Studio 11.0 - Web Services: WSDL File loads but options remain disabled

eric.butcher — Fri, 15 Mar 2019 13:16:25 GMT

I'm running CVP 11.0.1 / Call Studio 11.0 and am trying to use a Web Service element.

When I load the WSDL file, the other options don't become enabled. I click the load button and it pauses as if it is loading (button stays popped in and then pops back out after a couple of seconds), but never enables the settings for the web service call and Runtime Settings.

I've tried loading an invalid WSDL file to compare behavior and in that case it throws an error saying it isn't formatted properly, etc.

Anybody run into this before?

the element is designed to

Chintan Gajjar — Tue, 15 Mar 2016 10:39:41 GMT

the element is designed to work with following specifications:

WSDL 1.1 (using namespace http://schemas.xmlsoap.org/wsdl/)
- Binding Styles
  
  - RPC/encoded
  
  - RPC/literal
  
  - Document/literal
  
  - Document/literal (wrapped)
SOAP 1.1 encoding (using namespace http://schemas.xmlsoap.org/soap/encoding/)
- Includes built-in support for 1-dimensional SOAP-encoded arrays that do not use href references for array items.
- To parse n-dimensional SOAP-encoded arrays (where n is greater than 1) or href references in web service response messages, use the "Store Full Response XML" option and process the response with custom code.
XML schemas (using namespace http://www.w3.org/2001/XMLSchema)
- Includes built-in support for 1-dimensional arrays (that is, sequences).
- To parse n-dimensional arrays (where n is greater than 1) in web service response messages, use the "Store Full Response XML" option and process the response with custom code.

the WSDL you are trying to load into element might not be compliant with above specifications.

you can check with your service developer to confirm the same.

Well, it is definitely SOAP 1

eric.butcher — Tue, 15 Mar 2016 14:05:43 GMT

Well, it is definitely SOAP 1.2, but I would have thought I would get an error message from Call Studio rather than it just silently loading and unloading it like it seams to be doing. I'll see if my dev team can switch to SOAP 1.1 and try again.