Temporary Interface

Hi eleazarr,

To the best of my knowledge, this is not possible. Even if you were to add an exception timer, you can not chain that flow and the chain would be broken.

If you find a way to do this I would be very interested to know your solution.

Brad

Thank you and yeah that's what i figured would happen. Oh well! ¯\_(ツ)_/¯
I'll post the solution if I do find one.

Hi,

you can have the interface in the chaining and have escalation timer on it which will redirect the task to end after the time you will mentioned on it.

Yeah, i'm currently doing this, but the issue is the user is still in the interface in till they navigate away. I was kinda hoping it would be done automatically. I'm still trying a few things out.

Since there's no way to have a form "automatically submit" and chain the user along, something I've done in the past with a pretty high degree of success is have a "waiting screen" similar to what you describe except it has a "refresh" button on it - the user is free to spam the "refresh" button and each time they click it, it submits and loops around in-process until the on-the-side processing has finished, in which case either A) the user lands back on the same "refresh" screen and the language is updated (and it has a different button), or B) the user chains to the next desired task with the results/etc.

I also usually provide a "dismiss" button next to "refresh", which kills off the persistent task and once the processing finishes, the user gets the next task in line automatically in their task list.

I would recommend the approach given By Mike, Since on clicking of Refresh, the chaining will still apply to the task and on completing the background work the task will not to Tasks tab. This will hold good, If the wait time is acceptable by the End User.
Adding My thoughts, You can also send an Email that the task has been assigned to the User queue. Once the user clicks on dismiss button this can happen, Instead of going to his queue and verify that the task is back .