11-09-2017 07:35 AM
Finesse has an ability to post XML on call alerting, connect etc.
The below is a sample screen shot from Finesse 11.5 Admin posting some XML.
You can get Finesse to POST XML to a SOAP Web Service which could be very useful.
There is one issue.
SOAP 1.1 requires a specific HTTP Header also to be set.
So even if the XML is in the correct format, the SOAP Web service is likely to reject it with a 500 error.
To support this, (and it would be simple to add) you need to set the HTTP Header "SOAPAction"
But today, the only HTTP header value that can be set by Finesse is the Content Type as per below.
A nice feature enhancement would be to have the ability to add a custom header (with a checkbox to enable it).
You could then add the following example HTTP so that the SOAP post was 100% valid.
Example:
HTTP CustomHeader1: [X] SOAPAction: "http://schemas.mywebserver.mydomain.local/blah/IncomingCall"
Screen Shot of FInesse 11.5
Gerry
11-09-2017 10:52 AM
Hi Gerry,
I have forwarded this request to the Finesse product owner.
Thanx,
Denise
11-10-2017 05:02 AM
Just as a follow up, I got Finesse working with a SOAP 1.2 web service.
SOAP 1.2 does not require the SOAP action header.
It requires the ContentType header (which can be configured to be set correctly).
Example below of a SOAP 1.2 ContentType Header Example Value.
Content-Type: application/soap+xml; charset=utf-8; action="http://schemas.mydomain.com/CallService/IncomingCall"
It would not always be possible to get the API developers to switch to SOAP 1.2, especially if it was not a new API.
So its still a good feature to add to Finesse, and it could likely could be used for other things too, since it a custom header where you could set it to whatever you wanted to.
Gerry
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: