01-20-2020 06:00 PM
I am getting Max number of variables in action exceeded error in Finesse while invoking web service in workflow.If Input parameters are less than 5 its working fine.In Cisco links i do see there is a limitation of 5 parameters.currently we are 11.6.1 version, would like to know if there is any patch with new ES to pass more parameters or a change in registry to pass more parameters is available option with existing version?Any help/info is really appreciated.
01-20-2020 07:38 PM
I've ran into this before and the answer was see if you can combine the parameters and break them up on the receiving end or your out of luck.
david
01-21-2020 11:33 AM
Thanks a lot David for your quick response.Have you tried invoking webservice from gadget with more than 5 parameters? My plan was to verify whether we can invoke using gadget with more than 5 paramters? If you have any code can you please share?
01-21-2020 11:36 AM
Yeah, I've tried and it's not possible. My recommendation of combining them is your best bet.
david
01-21-2020 01:21 PM
Hi David, Thanks for your responses on this issue.You are saying even if we write custom gadget with more than 5 parameters we still get 'Max number of variables in action exceeded' error due to limitation from cisco?So only option is to combine? Did cisco TAC say anything, if not i plan to open case?
01-21-2020 02:14 PM
I didn't open a case so it might make sense to get official word, but this has been a limitation for a while so I don't see them changing it. Please update the thread based on what Cisco says.
david
01-21-2020 07:56 PM
Sure David.I have opened case will update once i get final outcome.
01-21-2020 02:31 PM
Hi,
What exactly are you trying to accomplish? Are you trying to update more than 5 call variables via a workflow?
Thanx,
Denise
01-21-2020 07:55 PM
01-21-2020 08:30 PM
Hi,
Is this an external (non-Finesse) webservices request? If so, you can make a custom gadget to send a raw http request. You can put as many parameters you want in there. Here is a sample gadget making an exteral rest api request: https://github.com/CiscoDevNet/finesse-sample-code/tree/master/ExternalRestApiSampleGadget
When making a custom gadget, you will need to write code to trigger on the workflow condition.
Thanx,
Denise
01-22-2020 10:31 AM - edited 07-21-2020 10:29 AM
Thanks Denise.I am trying to invoke external webservice using with below changes in gadget and still have issues to invoke.Do you have any idea what is causing this?Any help is appreciated.
handleNewDialog = function(dialog) {
clientLogs.log("handleNewDialog()");
// Call the REST API and display the results
//SM -- var url = "http://finesseFQDN:8082/finesse/api/SystemInfo";
var url = "WEBSERIVCE URL";
//var contentBody = "<User><state>READY</state></User>";
makeRequest(url, {
//SM --- method: 'GET',
method: 'POST',
//authorization: _util.getAuthHeaderString(finesse.gadget.Config),
contentType: 'application/xml',
content: <?xml version="1.0"?><soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" soapenv:mustUnderstand="1">
<wsse:UsernameToken><wsse:Username>username</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">password </wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
<soapenv:Body>
<p735:Request xmlns:p735="">
<par1></par1>
<par2></par2>
<par3></par3>
<par4></par4>
<par5></par5>
</p735:Requestst></soapenv:Body>
</soapenv:Envelope>,
}, {
success: handleResponseSuccess,
error: handleResponseError,
});
01-22-2020 11:49 AM
Your content needs to be escaped. You cannot have xml formatted that way in a JS file.
01-29-2020 07:49 AM
Thanks Denise.We have resolved this issue and working fine with workflow itself.
07-07-2020 02:36 AM
Hello smeegada1
Can you please give us more details for your solution?
We are on same page and this is answer from TAC:
Unfortunately, I checked internally and there is no alternative for this.
Finesse only supports 5 variables per action.
We can open an enhancement request based on the customer needs so Finesse can support more variables in the future. However, please note that an enhancement request will be only considered for future Finesse releases and it will take a while until it is implemented.
Your help will be appreciated.
Thanks
07-07-2020 05:54 AM
Hi Slobodan,
Try dynamically building the webservice paramaters(with shorter name) and passing it to FromEXT ECC variable(length 100). This will build the webservice request with less input varibales.
Let me know if you need more info.
Thanks.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide