• State Verified Answer
  • +2 person also asked this people also asked this
  • Replies 6 replies
  • Subscribers 11 subscribers
  • Views 4489 views
  • Users 0 members are here
Related Discussions
Home » Discussions » User Interface

Temporary Interface

eleazarr
A Score Level 1

My question, is it possible to have a temporary interface?

Now, let me give a bit of an explanation, by temporary interface i mean an interface that would act as a waiting screen? Within this "waiting screen" i don't want the user to do anything. It's more to notify the user that their request is being processed. Then, after a given amount of time to be redirected them to a different Interface were they would finalize a few details. Is there a way to implement this idea? 

Personally, I was considering using something like a timer and using use Activity Chaining, but i'm not sure if this is the way to go about it. Any other ideas or tips would be helpful.

 

Thank you,

Eleazar Rosales

  Discussion posts and replies are publicly visible

Parents
  • +1
    Certified Lead Developer
    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.
Reply
  • +1
    Certified Lead Developer
    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.
Children
  • 0
    A Score Level 2
     in reply to Mike Schmitt
    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 .
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.