I want to show customized confirm dialog box (instead of the Appian default "The Task Couldn't be submitted" message) whenever the user input task is timed out (in our case the exception timer we have kept for UI task is 20 mins).
Also at present when the user clicks OK button in the default dialog box, then the page stays there and either the user have to press F5 to restart the process or have to click on any of the SITE tabs to come out of the screen.
Instead, I have a requirement to come out of the current UI and the system should redirect the user to the page where the process was called from eg., if the process was a related action and one of the UI task timed out, on click of OK button the system should redirect the user to the page where the process was triggered i.e., record summary page.
Discussion posts and replies are publicly visible
that didn't work, as the exception flow cannot be a chained activity though the exception flow moves to new user input task, for the user the timed out task is only opened and visible in his browser.
BalajiR You can create your popup using refreshvariable refreshinterval. of 20 minute timer, so once timer crosses 20 mins, you can show the popup and hide the old form. So when user submits, you can submit the popup he will navigate to homepage.
This type of workaround you can try, but this will affect your process performance as tasks will be open for long time then it should be.
Unknown said:using a timer exception in the interface to redirect the user
This wouldn't actually "redirect the user" though. The user (who's walked away to have lunch and exceeded the timer value) will still see the (now expired) task on their browser screen when they get back. In the background, the process has followed the exception flow and now the user has an extra task in their Tasks List, but they still won't see that until they deal with the current task's error message and successfully navigate back to home/etc.
What's the use case for having a task timeout timer of 20 minutes? Every time I've seen one set that short (from an End User perspective) i have found it to be, let's say, unnecessarily cruel. When I use these I almost always allot enough time that the user is almost certain to have abandoned the task completely and won't be put out by it ending automatically - like 24 hours, or at least, "1 am the next night" or something like that.