Web Service using JavaScript as external action - always fails with "cc -1"

[LZ359]

Have anyone succeeded in running JavaScript as external action in extactions?

The JavaScript is executed as expected, but right after it ends, I have the "se.external.action returned -1 in parameter one" error, so the Web Service response is fault code. I did try to force $L.exit to "normal" in the JavaScript, but still no meaningful return from the Web Service.

SM version is 7.11.175

Any suggestions are appreciated!

[gumarrita]

In some documentation I found this:

Problem


<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>A CXmlApiException was raised in native code : error 19 : scxmlapi(19) - Doc Engine call failed with cc -1</faultstring>
<faultactor>Server</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body></SOAP-ENV:Envelope>

Cause


When Rejecting an Incident in the Windows client, the user is presented with another screen to provide a reason. Web services is not designed to handle such interaction from the server so the Rejected status will fail. Web services is only designed to add, update and delete records so any actions beyond this, such as calling a pop-up window, will fail. In this case a script is run that calls another window.


Fix


Depending on the version, modify either IM.update.incident or IM.template.update format control record. In Subroutines, look for the Application Name of "script.execute" then under Update modify the condition to read problem.status in $file="Reject" and gui()=true. When using Web services this condition will fail allowing the update to go through but still allow users with a Windows client to enter a rejection reason.

Hope is it useful.

[olga.petrishina]

Use the variable $L.action = "normal" instead of the variable $L.exit = "normal"