[MGNLFORM-147] Previous *and* next steps of a form should be displayed. Created: 16/Jan/13 Updated: 26/Feb/13 Resolved: 25/Jan/13 |
|
| Status: | Closed |
| Project: | Magnolia Form Module |
| Component/s: | None |
| Affects Version/s: | 1.4.4 |
| Fix Version/s: | 1.4.5 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
The form dialog has an option to display steps of a form on each page/step: "Check to display a step-by-step form navigation. The navigation will appear, if form sub-steps are defined." It currently only display previous steps. While that might be a valid behavior in some cases, in other cases, people expect to also see how much they still have to go through before being done with the form. |
| Comments |
| Comment by Jan Haderka [ 25/Jan/13 ] |
|
I understand that in template you need the list, but in general it would be preferable to return iterator rather then forcing loading of all of those siblings in memory. |