Clarity

I am trying to use the InvokeAction Process and found that that schema is wrong:

This was tested in SOAPUI 4.6.4:

This is the SOAP result from the InvokeAction Process WDSL

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:inv="http://www.niku.com/xog/InvokeAction">

   <soapenv:Header>

      <inv:Auth>

         <!--Optional:-->

         <inv:SessionID>?</inv:SessionID>

         <!--Optional:-->

         <inv:TenantID>?</inv:TenantID>

         <!--Optional:-->

         <inv:Username>?</inv:Username>

         <!--Optional:-->

         <inv:Password>?</inv:Password>

      </inv:Auth>

   </soapenv:Header>

   <soapenv:Body>

      <inv:Process>

         <inv:code>?</inv:code>

         <inv:request>

            <!--You may enter ANY elements at this point-->

         </inv:request>

      </inv:Process>

   </soapenv:Body>

</soapenv:Envelope>

Using the inv: prefix does not work, altough Clarity logs in an return a session.

Now this works:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:inv="http://www.niku.com/xog/InvokeAction">

   <soapenv:Header>

      <inv:Auth>

         <!--Optional:-->

         <inv:SessionID>?</inv:SessionID>

         <!--Optional:-->

         <inv:TenantID>?</inv:TenantID>

         <!--Optional:-->

         <inv:Username>?</inv:Username>

         <!--Optional:-->

         <inv:Password>?</inv:Password>

      </inv:Auth>

   </soapenv:Header>

   <soapenv:Body>

      <inv:Process>

         <code>?</code>

         <request>

            <!--You may enter ANY elements at this point-->

         </request>

      </inv:Process>

   </soapenv:Body>

</soapenv:Envelope>

We need urgent that to be corrected and an workaround to make it work now.

Can you help?

Looks like you have stumbled onto a known issue.

You are correct, the schema is wrong.  I believe we have talked about it a few times on the forums.
The correct syntax to invoke a process is shown below.
 

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:inv="http://www.niku.com/xog/InvokeAction">
   <soapenv:Header>
      <inv:Auth>
         <inv:Username>username</inv:Username>
         <inv:Password>password</inv:Password>
      </inv:Auth>
   </soapenv:Header>
   <soapenv:Body>
      <inv:Process>
         <code>rego_open_close_periods</code>
         <inv:request/>
      </inv:Process>
   </soapenv:Body>
</soapenv:Envelope>

As of right now I don't believe you can send any request parameters to the process.

Is this what your talking about?

Chris,

We send request parameters like this:

https://communities.ca.com/web/ca-clarity-global-user-community/message-board/-/message_boards/message/105824156?p_p_auth=LhM7PS7j&#p_19

An in the process action script, you just pull them out of the request.

V/r,

Gene

I have searched around these forums many times and that post has never come up...You Are Awesome!

The link seems to be broken. Would you mind posting it once again please?

Try this link:

Gel access to WSDL Process InvokeAction content

V/r,

Gene

The problem is that the webservice tool we use does allow us to change the SOAP structure provided by the schema.

We could alter the schema on a On Premisse server but we can't do that on an On Demand Clarity Server.

I am openning a ticket in support.

Let me know if someone have an work around ...