Thats a nice suggestion. I just checked and saw that the user logging in via XOG did not have the 'Process - Autostart' right.
I have added the right and will do the soap call to create instance in Clarity. Will let you know how it goes. thanks.
-Deepu.
Original Message:
Sent: Jun 11, 2025 02:02 AM
From: Paul Schofield
Subject: Clarity process does not get triggered.
Hi Deepu,
What user is logging in via XOG, and does it have the necessary rights (instance or global) to execute processes? I'm guessing you're using your own logon for the non-process (direct) XOG and via the UI, but what user is in the process?
Paul
Original Message:
Sent: Jun 10, 2025 04:42 AM
From: Deepu Divakaran
Subject: Clarity process does not get triggered.
Hi Experts,
I have a custom object (which has a sub-object) to which i have linked a process to run. Upon created of an instance of this object, the process should trigger.
The workflow is that a soap call external to clarity creates an instance of the object in clarity which should trigger this process. I find that the soap call creates the instance but the process is not getting triggered for such instance. The process tab on the instance is empty with no entries.
The soap response of the soap call is provided below which says success, but the process does not trigger.
<soapenv:Body>
<WriteCustomObjectInstanceResponse xmlns="http://www.niku.com/xog/Object">
<XOGOutput xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/status.xsd">
<Object type="customObjectInstance"/>
<Status elapsedTime="0.273 seconds" state="SUCCESS"/>
<Statistics failureRecords="0" insertedRecords="7" totalNumberOfRecords="7" updatedRecords="0"/>
<Records/>
</XOGOutput>
</WriteCustomObjectInstanceResponse>
</soapenv:Body>
However, if I xog in the instance, the process runs successfully.
Also, if I create the instance from UI, the process runs successfully.
Regards,
Deepu.