WebServices Creation Operation

Hi All,

I am configuring Create operation for WebServices connector. This application has native identity set to userId. The issue is userId is generated by application itself. So, after account creation, the account is displayed as “???” in IDN and gets corrected after aggregation. I also tried to setup multiple end points for Create operation. When I setup parent endpoint, the second one does not execute. I guess that is because there is no response coming from first endpoint. If I make them independent, the second end point can’t find the user. I am guessing that is because they are executed in parallel and account is not created yet. Can someone please confirm if this is how WebServices connector works with parent endpoint and indenpendent endpoints?

The only other option I can think of is to set up after operation rule to call an end point to get the account and put userId in response map.

Is there any better option?

Thanks,
Gaurav

Hey Gaurav,

Assuming application generated userId is being returned in create account operation response. In create account operation response mapping, populate userId in account schema or whatever attribute that you define for Account ID.

Create a get object (single account aggregation) operation and pass $plan.nativeIdentity$ in request should do the trick. e.g. GET /users/$plan.nativeIdentity$ Web services connector will call get object operation if one is being defined after create account operation, automatically.

Cheers,

Thanks Kenny!! That is the main problem, The create account operation response does not return userId.

Thanks,
Gaurav

Create operation chaining does not need mention of parent end point. The sequence in UI is something gets executed in api calls.

If create is not getting generated id then try to get it in second create operation in response.

If this is not working then afteroperation rule is the only option here.

“When I setup parent endpoint, the second one does not execute. I guess that is because there is no response coming from first endpoint.” ----> Second end point would get executed irrespective of response coming in or not