Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0034211 | Openbravo ERP | B. User interface | public | 2016-10-14 15:32 | 2022-02-01 08:05 |
| Reporter | dbaz | ||||
| Assigned To | Triage Platform Base | ||||
| Priority | high | Severity | minor | Reproducibility | have not tried |
| Status | acknowledged | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | No | ||||
| Web browser | |||||
| Modules | Core | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0034211: [UX] Bad behavior of 'New in form' button | ||||
| Description | Actually 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 Reproduce | Go 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. | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| 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 | ||
| There are no notes attached to this issue. |