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 cannot be customized. Sorry ...
Thanks for your reply Stefan, is it possible to come out of the timed out UI on-click of OK button in the default confirm dialog.
"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."
I don't think that can be done. The user will have to close the tab or refresh if the task is timed out. Only on successful completion of your task, your requirement will be satisfied.
I am just curious to know can't we use Exceptions here??
Could using a timer exception in the interface to redirect the user be a valid option?
BalajiR said: on click of OK button the system should redirect the user to the page where the process was triggered i.e., record summary page."
I will connect to end node , so process will end and it will take us to the summary view. I thought of this but it's not preferable i guess?
Venky Avuluri that didn't work, on exception we can connect to end node and once the timer is reached it triggers the exception and reaches the end node. But as the task is opened in users browser, system will not close the task and redirect the user to summary, the user will stay in UI task only.
BalajiR said:. But as the task is opened in users browser, system will not close the task and redirect the user to summary, the user will stay in UI task only
Sorry, I misunderstood the Question : )
Venky Avuluri
I hope this answers your question to me,
This way of design would not make sense for the requirement he is expecting. The timer is for exception cause the user is not taking any action due to lack of his/her presence. Why would we want to show another UIT. Also the question was on a different point I understand.