Is there a way in a process model to add a node with an informative screen, that does NOT require any user input, and the process continues running immediately after displaying the screen to the user?
For now i see two aproaches, but none of them are what I'm looking for
The first one: A User Input Task with a form, and a timer, that makes the process continue after a specified amount of time. But that makes the process wait when there's no need to. Also after the timer runs out and the user clicks a button on the screen, an error appears, saying that the task no longer exists.
Second one: Make the form return something when clicking a button, and continue after the output. The problem is that I want the process to run even when the user navigates away from the screen, or closes the tab, as to account for the user not clicking the button.The two approaches can be used simultaneously, but still I would rather not wait for neither user, nor the timer. I just want it to go to the end node immediately.
Is there another approach that I could use?
Discussion posts and replies are publicly visible
This is my approach:
Launch the "confirmation screen" in a quasi-asynchronous way, and continue the process immediately. Give no buttons on the form, and force the user to navigate away (potentially explaining this to them on the form), and/or give them a link to click back to their Site (now that a!safeLink can open in same tab, and with more flexible Site URL options, this is more doable now than it was in the past).
Edit: plus as pointed out in Stefan's blog post, you would normally want this to be configured as a Quick Task, which these days only means it won't show up in a user's task list.
This configuration doesn't seem to work. The process enters the node with confitmation screen, but it is not displayed in the UI.
You will need to make sure chaining is correct. It should chain all the way up to the user input task (and not along the other output from the AND gateway). If you'd like to post a screenshot of your process flow here I can double check it for you.
Inside of 'Confirmation Screen':When monitoring the process I see that it reached the node, but the Screen was not displayed in the UI
Your chaining following the AND gateway is reversed. The path to the confirmation form needs to be chained, and the other path needs to not be chained.
Thanks for noticing. Still the parent of the process with the AND node is waiting for both end events here to complete, so this approach doesn't change much. Is there a way around that, or should I just stick to the timer?
The other path would end with a Terminate node, instead of a standard End node.
The problem with doing that, is I'm getting an error in the UI, as the child task has also been terminated.
Guess I'll just stick to the one-minute timer.
You won't get this if you chain into the task but don't chain into your subsequent processing. You'll get your confirmation screen which the user then has to navigate away from (or you can provide a link that they can use to click away).