a!startProcessLink() redirecting back to last clicked PM

Question

I am using a!startProcessLink() to create four different actions from a main page. Main page is part of a process model which contains start node >> main Page (where all four start process links are configured) >> end node (configured to terminate). 
 When i launch main process model it shows me page with four link e.g "A", "B", "C" & "D". I also have one "exit" button as buttonWidgetSubmit in main page. If i click on any of the link it will it will launch related PM and clicking on "Back" button will redirect to the main page. Problem is that when i click on "exit" button afterwards, process redirect me to last clicked link instead of completely exit process. 
 e.g. 
 main page >> link "A" >> back button >> main page >> link "B" >> back button >> main page >> clicked exit will redirect me as if i clicked on link "B" and open "B"'s UI. 
 Any advise would be great help. 
 Note: "All in tempo under Action tab" 
 Thanks, 
 Ajay Pandey

ajayp · Accepted Answer

Thanks Mike Schmitt (mschmitt) & Josh for your suggestions. At this moment i am proceeding with large button layout ( so that look and feel would be same for end user). This way i can achieve my goal to go back and forth from main page to all different pages. I'll also look for Appian support response on mentioned behavior.

Josh · Answer

I've encountered this behavior when using process task links on a form started via a related action. It is annoying, but the basic idea is that Appian retains the context stack for a user and returns the user to the previous context. I've copied the exact phrasing below. It isn't documented that well and can be confusing in situations like these. The product use case they gave me was #934. 
 
When a task is completed, the user is redirected to the URL where the user initiated the task from. In most cases, this is a report on a record view or site page. If they complete the task from the task tab, it returns to the task tab URL. In this defined customer use case, they are being redirected back to the the related action. The reason you are seeing this invoke a new related action is that currently both related actions and actions are invoked or kicked off when navigated to directly via the URL.

Mike Schmitt · Answer

So far my main use case for Start Process Links has been in Task Reports, since it allows me to essentially create purely database-backed "tasks" that aren't actually tasks and don't rely on running processes / clunky task reports / group assignments to pull back. Luckily there's no such issue when using them from task reports, and I assume there is similarly no issue when using them in regular reports or on Record Dashboard forms. I don't think I've used any inside an actual running process yet, though I understand that there are probably valid use cases for this. 
 By any chance have you tried using Submit Links in your parent process task? Using submit links will not only cause your form to submit and step forward to a chained subprocess / etc, but also you can use the link itself to store a specific value into a rule input (essentially mimicing how a regular button works), which could be used to select the desired subprocess (since you mentioned maybe needing to use radio buttons for this).