vaguely remember experiencing this.
from my exp., the main reason to use this (process after Save) is because after the save, you need to run a process.
you don't (or can't) want it coming back to the calling process because that process needed to complete with a VIEW as the last statement... if not, then pressing a button on that form would generate the dreaded "do you want to end the running process" dialog (or similar, cant remember - its late)
(I think thats why Vlad built this (process after Save) into the architecture originally because that parent process needed to end so other processes could start via buttons on the form.)
so something's telling me you've called this form with an EDIT (not a VIEW) thereby suspending that Process and aware can't BOTH return to the calling process AND run your process after the SAVE.
