Completion message while ending a task

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.

Hi Mike

You are almost correct about the implementation. Let me explain you the entire set up now.

1) Currently as a user you go to a specific site. There you can see the link to open a task.

2) Once you click on that link. a!startProcessLink() is being called in the backend

3) Inside this process model we are making an integration call that takes the data from 3rd party system

4) Using that data a task form is generated and shown to the user

5) Now after entering the required details when user clicks complete task, The current process gets ended and a new call to the same process is being made

6) Which in return makes an integration call to 3rd party system. Collects data and display the task.

7) This entire process keeps on running until user finally click one of the button that stops this behavior and let them get back to the site again

So, point (5) and point (6) is needs to be separated here. I.e when user clicks on complete task and before the next task becomes available. We need some kind of message display to make them aware whether the task they are seeing currently is the new task or the old one

Hi Vivek,

You can have one more interface configured with the confirmation message stating "You have successfully Submitted the task" or may be message relevant to your use case so that user will be notified after submitting the task.

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.

Our entire approach is to save users from additional click. Putting in a separate interface for success message will increase one more click. Can't we do something on the same interface? 

This will increase an additional click for the user. Earlier we were doing the similar thing wherein users were redirected to site again after they submit the task and from there they again click on new task link but to reduce this additional click, We came up with the solution of auto-acceptance of next task. Can't we have something in the same interface?

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.

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.

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.