WEB API response not updating the process variable

Question

I have one web api which is using a!startProcess to call the process async. As it is async and does not wait for process model to complete it is not updating the process variables in the response. 
 What are the possible fixes we can do?

Stewart Burchell · Accepted Answer

Kind of. Separate the generation of the CaseIds from the creation of the Cases themselves. I presume you're generating some human friendly readable CaseId. Create the number that you need (you could use a Stored Procedure to do this to ensure that any concurrent API requests don't overlap), return them to the Process and hand them out to the sub process instances as required to use.

agam · Answer

Hi radhikam0005 , 
 If your response is returned like this and in the process the case id's are present as expected, then you are running out of activity chained nodes. At any time, max of 50 chained nodes can be executed and then activity chaining would by default break but the process would continue. 
 You can read it over here: https://docs.appian.com/suite/help/20.1/Process_Model_Recipes.html#breaking-a-chain 
 
 You can follow the approach Stewart has suggested below, I would prefer that as well. 
 If you want to not use stored procedure, save blank rows in your database to generate new id's in your table and then update the ID accordingly in your loop to map the ID's. 
 
 if your case creation scenario is more complicated and creating ID's upfront doesn't look feasible I would suggest to restrict one case creation at once or remove looping and create a logic which allows writing multiple rows at once.

agam · Answer

Apply activity chaining till the point your process variable is updated. 
 API will capture the response till it's activity chained from the start event. 
 See documentation for more details

WEB API response not updating the process variable

Top Replies