I'm using the createObject method in a PAM flow to create new contacts on SDM. The insert is performed but an error is returned by WS, the operator becomes locked and the post execution code fail.
<impl:createObject xmlns:impl="http://www.ca.com/UnicenterServicePlus/ServiceDesk"> <sid>sid__</sid> <objectType>objectType__</objectType> <attrVals> attributes__ </attrVals> <attributes> </attributes> <createObjectResult>createObjectResult__</createObjectResult> <newHandle>newHandle__</newHandle></impl:createObject>
Where 'sid__' , 'objectType__' and 'attributes__' are replaced at execution time
You mention the insert is performed, are all the attributes being filled in as expected?
all attributes was filled as expected. The method response may be the cause, because the process variable 'ContactHandle' still NULL after operator execution.
Do I need to pass any value on this tags?<createObjectResult>createObjectResult__</createObjectResult><newHandle>newHandle__</newHandle>
The way the process was deployed don't replace this values under Dynamic Parameters section.
The post execution code try it:
That's strange, I would have thought one or more attributes was not being set correctly. Can you check the SDM logs for errors? jsrvr.log and stdlog.x may have some information.
The stdlog.x contains this error message:
In your request code try updating the following.
When you leave this blank it'll return everything, but you can limit the response by adding one or more fields. If that doesn't help you might want to open a support case.
Yeah! inserting the persistent_id on the attributes section the operator works fine as you can see below:
Many thanks !
That's great! It looked like the response was being truncated, I'm not sure if that was PAM or the SDM WS that was cutting off the response.. Either way this is probably a bug.