Completion message while ending a task

Question

Hello All, 
 
 We have a process wherein user completes one task and another task is automatically getting accepted to them. When user clicks the end button they are not able to see anything and new task is opened for them, This makes a confusion in order to understand whether the task was closed or not and the task that they are seeing is the new task or the same old task. Hence, As a solution to it we are looking for some kind of message display or something similar that can tell the user that your task is successfully closed. Can someone please help here? Thanks in advance

Mike Schmitt · Answer

Unknown said: user completes one task and another task is automatically getting accepted to them. 
 I would personally need some more detail regarding what your current configuration is, before attempting a guess as to what's happening here. Can you post, perhaps, a screenshot of your process flow? There are at least a half dozen different scenarios I could think of that might lead to this question: 
 
 Does your process model have two consecutive User Input Task nodes that both look similar? 
 Or is it that you're using a Sites tab pointing to a process model with a "Start" form, but nothing else after the start form when a user submits the data (which to a user would look like they're getting a "new task" with blank fields immediately after submitting, but it's really not a "task" at all)? 
 
 Hence more detail being needed.

Mike Schmitt · Answer

It should be fairly easy to add a "confirmation screen" task after the initial task is submitted. From here a user could confirm that they want to step into another "round", and perhaps with the option to exit from there.

Peter Lewis · Answer

What if you display a banner at the top of the new task? Something like these alert banners usually works pretty well. This makes it easy to determine when the previous task completes while not requiring an extra click. I'd also suggest setting it up so that the banner hides itself once the user starts interacting with the new form.

Mike Schmitt · Answer

Unknown said: Can't we do something on the same interface? 
 You could, but I don't see how that would reduce the user clicks, as switching from one interface to a different one within the same task still requires user interaction of some sort.

Dave Lewis · Answer

I assume you're doing a loop to the same form, so the PM returns to the same exact user input task. 
 You could pass a parameter that includes whether the last input was completed successfully. By default it would be false. 
 You can then put almost any component you want at the top of your interface with a showWhen set to only appear when that parameter is true. That serves as a message to let the user know that this is a new form. You can then set an extra save() inside each other component's saveInto to set it false again, so the message disappears. 
 (It might cause an awkward jump now that I think about it; you might not want to use showWhen, but a component that is always visible, but read-only and usually with an empty string. That might keep the other interface components from jumping around your screen.) 
 You can do a read-only text field, a richText, a boxLayout that usually has nothing in it, a card layout that usually has nothing in it, a nice billboard layout that only sometimes features an overlay with text. Basically anything, and have text that says "The last one you did has been entered successfully!" It will take a click / user interaction to make it go away, but no more user interactions than they would have had to do anyway.