In our process we have various user input tasks along the process involving user interfaces.
Does anyone know how to configure the cancel button so that it simply "exits" the interface?
Discussion posts and replies are publicly visible
Any buttonWidget with the 'submit' parameter set to true will exit the interface and continue the process flow
hi aaronp0001, what I am looking for here is that it closes the interface without progressing the process model (ie the task remains open), so almost like a "close interface" button
Any user input task in a process model allows you to select a checkbox on the forms tab labelled "Allow users to save a draft of in-progress tasks" which sounds like it should do what you're asking, allowing the user to close the task and resume it at any point from their tasks in tempo.
However, with numerous user input tasks in your process it sounds like this could lead to very long lived processes if escalations/exceptions aren't configured correctly, so bear this in mind.
I'm not sure why you say the process instance can't be progressed any - with any submit button click the process instance would need to progress at least a little bit.
So, if you specifically need an "exit" button (i would suggest not calling it "cancel" because that carries other meanings for most users), you would simply have a gateway after the User Input Task in your process model which loops back to the same task but without chaining.
Cancel usually denotes ending the process without doing anything further, or possibly rolling back changes that were made. You can always configure tasks to be assigned to a group, and the person who accepts the task will have the option of returning it to all assignees.