Synchronous start process behavior

Question

Hello folks, 
 I would like to understand the Start Process SS behavior. From my understanding, we no longer need to perform chaining inside a child process if the child process is configured as a Synchronous Start Process. 
 Below is the configuration I applied for one of my record-related actions. 
 Here once action is completed we re query the audit data in the interface which is set in refresh variable and refresh after "RECORD_ACTION". But this is not working as expected. I have to refresh the entire screen to get latest audit data. But if i put chaining between start process(Write audit) and end node, page is refreshing as expected and getting latest audit data. Please let me know if it is expected behavior. Thanks in advance

Harsha Sharma · Accepted Answer

Yes this is expected behaviour. Chaining maintains the execution of each node one after another and returns back to the start form with data available till the node chaining is configured. In scenario 1, when you dont have chained till start process then process executes in backend without passing any context data to start form back. In scenario 2, when you do have it chained till start process then process executes keeping the start form active - so that user's action completion happens after then node when chaining is complete. So the process holds the user form, waits till sub process is complete and returns the data back in main process and then lastly action is complete and user sees UI will latest data. 
 Process being synchronous/non-synchronous doesn't not relate to the above mentioned behaviour. To understand simply, the sync/no-sync allows system to run process in serial/parallel for optimal performance in same/different engines. Its used mainly to improve processing performance and break big processes into smaller ones depending on their dependency on one - another. 
 If the need is for user to wait for some data to be updated/refresh the data on after action then activity chaining is needed with synchronous sub process.

James Lepone · Answer

Harsha Sharma That is almost correct, but not fully. In fact, the issue you are running into Vaishal seems to be a bug we found yesterday. All you should need to do is chain the flow after the Start Process node, and it should work (you do not need to chain anything in the child process, just run it synchronously from the parent).

Synchronous start process behavior

Top Replies