User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm designing a form to schedule a specific job to run. However, one of the requirements is that the user be able to run the job without scheduling it, and then either abandon the job or continue onto scheduling it.

Specifically, the workflow is:

form flow example

I'm sort of stumped how to do this elegantly; the results list is a fairly large table (probably taller than the screen), so it either needs to be a scrolling table inside the form, a modal, or a separate page (in which case the flow is weird because it goes p1 -> p2 -> p1). Anyone have any suggestions?

share|improve this question

Since the Naming&Scheduling is an endpoint and needs to be accessed from two other steps in the flow, I see no harm in putting it in a modal dialog. In that sense it's outside the flow, so the modal won't interrupt, and either you schedule it or you don't.


download bmml source – Wireframes created with Balsamiq Mockups

share|improve this answer

You could make it a sub workflow and have a popup window to handle that. That's probably the most elegant solution.

share|improve this answer

I'd have to agree with Koen's answer here but for the sake of keeping things isolated for decision triggers, leave the Schedule button along with the parameters and then once the results are generated and the user is happy with the results you'd use the same workflow as if the user never executed the results to begin with.

Also, are the number of parameters a user can supply for a job a long list or something that falls into a small space on the screen?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.