Okay, I have a process flow that goes like this: a person enters an interface to reassign a case, maps the emails, etc. Then they enter a synchronous subprocess that connects to an API. Depending on the validation (whether the user clicked "assign" or "reassign"), an asynchronous process runs that sends an email notifying them that the case has been reassigned. The requirement is that after this is done, the user returns to the main screen. The flow works when the email isn't involved, but when the email is, even though it's asynchronous, the activity chaining breaks. Could you help me find a solution for this, or suggest other options? Thanks!
Discussion posts and replies are publicly visible
Did you consider using the "Start Process" smart service instead of "Subprocess"?
You second process model breaks chaining as it misses the chain from the start node to the XOR.
Use the Start Process smart service node to trigger the email process, It fires it as a completely separate process instance. Place it after the user-facing chain completes so it doesn't interfere with activity chaining.https://docs.appian.com/suite/help/26.3/Start_Process_Smart_Service.html
I believe Stefan already mentioned this but just tp specify, your "Assign" subprocess is running synchronously but drops chaining in the first flow line.
As Rocky from Project Hail Mary would say: "Amaze, amaze, amaze!", using `Start Process` from the interface allows for a faster workflow and prevents the interface from breaking. Thank you so much, community!