A process model is exposed as webservice, while calling the webservice using values are not being passed to process parameters even though the process is triggered successfully.
webservicequery( wsConfig: a!wsConfig( wsdlUrl:<WSDL_URL>, service: <SERVICE_NAME>, port:<PORT_NAME>, operation: {appiancorp.com/.../pm}start ), inputVar: { startRequest: { username:<user_name>, password:<password>, param1:”A”, param2: “B”, param3:"C" } })
Above code generates the following error, if those process parameters are marked as mandatory..
WsResult httpStatusCode: 200 httpErrorOccurred: false fault: "<env:Fault xmlns:env="">schemas.xmlsoap.org/.../"> <faultcode>env:Sender</faultcode> <faultstring>SOAP request doesn't contain a required process parameter: param1</faultstring> </env:Fault>" returnValue: Dictionary startResponse: null (startResponse)
Has anyone experienced the same? Any suggestions?
Discussion posts and replies are publicly visible
I thought process models exposed as a webservice via the plug in had been deprecated and we ought to use webAPI's instead that can start a process?. It might be worth exploring that as a more strategic option ? Personally I've not tried to test an Appian process model exposed as a WS via Appian itself but if its like starting a process from a related action shoudl the params be wrapped in a set of {} to mark the inputs as a dictionary item ?