Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0034211
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] B. User interfaceminorhave not tried2016-10-14 15:322022-02-01 08:05
ReporterdbazView Statuspublic 
Assigned ToTriage Platform Base 
PriorityhighResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0034211: [UX] Bad behavior of 'New in form' button

DescriptionActually the 'New in form' button behavior (pressed from the form view) with autosave enabled is:
* It saves the record. If the record cannot be saved (missing mandatory fields, ...), the record changes are discarded/cancelled.
* The new form window is opened.

It is wrong. If the record cannot be saved, it should behave the same than if you try to close the form or go to the next/previous record: an Error message should be shown, and the button action ('New in form' in this case) should not be performed.

The UX problem with the current (bad) behavior is that if there is a large form, and you miss to fill some mandatory fields (maybe they are in a unnoticed collapsed section) and press the 'New in form' button, the changes (or the new form) is going to be lost without any warning to the user.
Steps To ReproduceGo to "Sales Order" window.
Press 'New in form' toolbar button.
Without filling all the required fields, press the 'New in form' button again.
The previous partially filled form is lost forever.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2016-10-14 15:32 dbaz New Issue
2016-10-14 15:32 dbaz Assigned To => platform
2016-10-14 15:32 dbaz OBNetwork customer => No
2016-10-14 15:32 dbaz Modules => Core
2016-10-14 15:32 dbaz Triggers an Emergency Pack => No
2016-12-01 13:04 alostale Status new => acknowledged
2016-12-01 14:03 alostale Priority normal => high
2022-02-01 08:05 alostale Assigned To platform => Triage Platform Base


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker