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
Discussion posts and replies are publicly visible
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).
Yes this one i tried and its working. Thanks James Lepone
Also can you let us know which info is wrong here which Harsha listed
The best way to review how SPSS interacts with activity chained flows is here: https://docs.appian.com/suite/help/25.1/Start_Process_Smart_Service.html#using-activity-chaining
This part of her response seems incorrect to me: "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."
You can use SPSS for this (you do not need to use subprocess node), you just need to chain to it and run it synchronously, as with your original post. Your original post is the "correct" design, we just need to fix this bug that requires the following flow to also be chained.