Any workaround to achieve activity chaining with wait period?

Question

Hi All, 
 We have a customer requirement where user enters few data in task-A and then the process do some checks, DB writes and integrates with 3-4 web services to fetch the details. The consolidated result should be displayed on task-B seamlessly. These checks and service calls is taking some time (15 to 20 sec) to give the desire result and increase the no. of nodes as well. So, activity chaining fails in direct flow. As we know, any kind of wait/timer or split/join fails for seamless output. We split the path and put entire logic in a sub process then also waiting for any flag or timer fails to achieve activity chaining. I tried using loop in flow with a flag condition till the parallel sub-process returns value but that is also runs many time and count exceed more than 50 nodes . Is there any workaround to achieve activity chaining with wait node. Or, anyway we can engage/hold process (15 to 20 sec.) between two nodes without failing activity chaining. Note: We cannot add another(blank) task in between task-A and task-B. Also, we cannot increase activity chaining limit in custom.properties. In this situation, any suggestion please ? Thank you.

Sandeep Deshmukh · Answer

Whatever you have mentioned in Notes, I guess that's theonly option we have to fix this chaining issue. Try to minimize number of nodes and expressions.

ankita0004 · Answer

There are multiple ways to solve this - 
 
1. We can call web service process as Asynchronous and set the parameters as call as reference so that the node of that process will not 
 count and chaining will not break. 
 
2. We can convert multiple nodes in single node like script task and number of nodes will reduce.

Puspendu Pal · Answer

Hello, 
 
Since the time to process the checks is more than 15-20 seconds, you may do these checks in asynchronously (may be in a subprocess), while providing an intermediate task with a "Refresh" button for the user to check if the checks and results are available? Once the result are available you can take the user to task B.