Anyone have a creative solution for adding a cancel button to a start form that

In 7.11 you could use images or links instead of standard buttons. Your "Continue" link could use the new a!submitLink() to continue the process whilst your "Cancel" button can use a!recordLink() to return to the record dashboard or any other navigable area.

Good deal. Seems like 7.11 has a lot of good features. Unfortunately, we're still running on 7.9.

Why not allow the user to just navigate away and add a exception timer to the first user input task. This is something you would have to do quite often anyway.

In 7.9 you could have the Cancel button save to pv!, use the pv! in an XOR as the first node of the model and just route to an End Event if the pv! is set via cancel.

Good workarounds but I am trying to not start a process instance. Both the exception timer and the XOR would require a process instance.

Sure, but a related action for example always starts a process as a start form is not allowed. For a action on the actions tab this is different.

That isn't true. You can have a start form on a related action and it doesn't start a process instance.

At least that is the case in 7.9.

It certainly looks like upgrading to 7.11 is the only way to 100% meet your strict requirement... out of interest why are you so strict on not starting a process instance, even one that immediately terminates from a cancel button?

At least for entity based records a related action model must have no start form.

Create a process model called Update Phone Number with a process variable named employeeId of type Number (Integer) marked as a parameter and no start form.

forum.appian.com/.../Records_Tutorial.html