AnsweredAssumed Answered

InvokeAction - Process WSDL

Question asked by BobSimmers on Jan 18, 2012
Latest reply on Mar 19, 2014 by joni.campos
We have been using several of the WSDL's (Query and Object) to integrate some of our custom web development with Clarity. These have been working perfectly.

However, when trying to use the InvokeAction - Process WSDL, we are simply getting a ReturnValue of False - no other debugging information. Needless to say, the process in Clarity is not being started. I've tried with multiple custom processes even very simple one's with no difference.

Here is the WSDL being executed and as you can see it's very simple.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:inv="http://www.niku.com/xog/InvokeAction">
<soapenv:Header>
<inv:Auth>
<inv:Username>#####</inv:Username>
<inv:Password>#####</inv:Password>
</inv:Auth>
</soapenv:Header>
<soapenv:Body>
<inv:Process>
<inv:code>mit_check_timeslicing</inv:code>
</inv:Process>
</soapenv:Body>
</soapenv:Envelope>

Here is the output:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header/>
<soapenv:Body>
<SessionID xmlns="http://www.niku.com/xog">79777672__2D1B6723_134EDB3F3F4_48DF</SessionID>
<ProcessResult xmlns="http://www.niku.com/xog/InvokeAction">
<returnValue>false</returnValue>
</ProcessResult>
</soapenv:Body>
</soapenv:Envelope>

This is being executed with an admin userid and password so privileges should not be the issue. We are successfully connecting (see the SessionID)..

Thanks in advance..

Outcomes