allow backwards navigation after job submit

[bekozi]

who: @bekozi

After submitting a job, it is not possible to navigate backwards on the forms without getting validation errors. I can imagine a number of cases where the user would like to run a minor modification of the parameters again.

[murphysj]

From Joe:
This needs to be fixed as we figure out how to handle the backwards navigation.

A Bug : The red "error" notice is not cleared (Workflow Page 1 screen shot -- attached) . This happened when I used the "back" button to go from the workflow page 3 back to the first page to change something, and it created an error where there was none. this was true even when I selected a choice from that pull-down menu -- the error message still was there.

[murphysj]

From Joe in testing 0.3.1
(Code) Design issue how to handle going "back" in the workflow.... Ideal behavior when using the back button on the browser to revisit previous steps in the workflow is to keep all the selections that were made (this seems to be mostly true). This allows users to complete the workflow, and then go back to the beginning and change, say, one aspect of their choices such as the area, and complete the workflow with the new choices -- without re-entering all the other choices that stay the same. I know this is sometimes difficult to achieve but it is the "ideal".

[LucaCinquini]

I believe that most if not all selections are kept. Can Joe identify which selections are not kept ?
thanks, L

On Mar 21, 2014, at 9:39 AM, Sylvia Murphy <notifications@github.commailto:notifications@github.com> wrote:

From Joe in testing 0.3.1
(Code) Design issue how to handle going "back" in the workflow.... Ideal behavior when using the back button on the browser to revisit previous steps in the workflow is to keep all the selections that were made (this seems to be mostly true). This allows users to complete the workflow, and then go back to the beginning and change, say, one aspect of their choices such as the area, and complete the workflow with the new choices -- without re-entering all the other choices that stay the same. I know this is sometimes difficult to achieve but it is the "ideal".

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/104#issuecomment-38288619.

[murphysj]

Luca,
Joe won't see this email. You'll need to contact him directly.

On Fri, Mar 21, 2014 at 10:02 AM, Luca Cinquini notifications@github.comwrote:

I believe that most if not all selections are kept. Can Joe identify which
selections are not kept ?
thanks, L

On Mar 21, 2014, at 9:39 AM, Sylvia Murphy <notifications@github.com
mailto:notifications@github.com> wrote:

From Joe in testing 0.3.1
(Code) Design issue how to handle going "back" in the workflow.... Ideal
behavior when using the back button on the browser to revisit previous
steps in the workflow is to keep all the selections that were made (this
seems to be mostly true). This allows users to complete the workflow, and
then go back to the beginning and change, say, one aspect of their choices
such as the area, and complete the workflow with the new choices -- without
re-entering all the other choices that stay the same. I know this is
sometimes difficult to achieve but it is the "ideal".

Reply to this email directly or view it on GitHub<
https://github.com/NCPP/ClimateTranslator/issues/104#issuecomment-38288619>.

Reply to this email directly or view it on GitHubhttps://github.com//issues/104#issuecomment-38291375
.

---

Sylvia Murphy
NESII/CIRES/NOAA Earth System Research Laboratory
325 Broadway, Boulder CO 80305
Time Zone: U.S. Mountain
Web: http://www.esrl.noaa.gov/nesii/
Email: sylvia.murphy@noaa.gov
Phone: 303-497-7753