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
If I understood your requirement correctly, we can achieve this by providing cancel button which will be passing flag (Exit) to process model using rule input. When user choose cancel you can have XOR gate to check the user action from flag(Exit) and redirect to the user input task without activity chaining. So process instance will be alive and task can be picked anytime later.
Hi Arunkumarc, will this result in another task ID/task instance being created?
Hi,
Yes, it is created new task but existing task is done. Again user can open that task they can do their activities on that.
Unknown said:will this result in another task ID/task instance being created?
Yes - the new task would be a new instance with a new task ID. There is really no way around this, other than just having the users click back out to their task list without clicking anything. Any button or link that causes the form to submit will require the process model to move forward and for the existing task instance to end, as I mentioned in my reply from yesterday.
The only other option is assigning the task to a group. An individual has to accept the task to start it, and after accepting, they have the rights to reject that task and return it to all assignees.
The process won't move forward until someone submits the task rather than rejecting it and returning it to all assignees.