We have an SOAP integration with the Service Catalog, but it is very complicated and I strongly suspect is not the correct way to do it.
Basically what happens is that a SOAP message comes in and a transform map sets the fields for the Request. The rest of the message is then processed in an After Transform Script to create the Requested Item and then after that there is complicated code to create copies of the variables from the catalog item definition and set them for the newly minted RITM. This is all very complicated and prone to errors.
On the ServiceNow wiki it mentioned using the Cart API. It has a caveat that the cart will be that of the SOAP user for SOAP integrations.
With all this in mind, I have some questions:
1) Is the Cart API the best way to go, instead of our code which has a role-your-own flavour to it?
2) If there is one user for all SOAP interactions, is there a danger that while one request is being processed, the cart is emptied for another concurrent transaction? Or doesn't it work that way? Or if it does work that way, how is this guarded against? (Locks?)
