Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0019827 | Openbravo ERP | B. User interface | public | 2012-02-21 17:38 | 2012-03-02 15:38 |
|
Reporter | dbaz | |
Assigned To | dbaz | |
Priority | urgent | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | 3.0MP9 | Fixed in Version | 3.0MP9 | |
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 | 0019827: You can leave a form view an empty required field |
Description | You can leave a form view an empty required field |
Steps To Reproduce | Go to any window with an existing created record with a required field (example "Sales Order")
Go to a form view of any existing record with a required field (example, "Document No.": "PR/1")
Delete the value of the required field/input (example: "Document No.")
Go next record. Notice that no error message is displayed
Go back to the previous record. Notice that the original value is set in the input.
I think you should not be able to move the record until all required fields be properly filled. |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | |
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2012-02-21 17:38 | dbaz | New Issue | |
2012-02-21 17:38 | dbaz | Assigned To | => mtaal |
2012-02-21 17:38 | dbaz | Modules | => Core |
2012-02-21 17:38 | dbaz | OBNetwork customer | => No |
2012-02-21 18:05 | mtaal | Assigned To | mtaal => dbaz |
2012-02-21 18:07 | mtaal | Note Added: 0045332 | |
2012-02-22 14:39 | hgbot | Checkin | |
2012-02-22 14:39 | hgbot | Note Added: 0045365 | |
2012-02-22 14:39 | hgbot | Status | new => resolved |
2012-02-22 14:39 | hgbot | Resolution | open => fixed |
2012-02-22 14:39 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/6e76a2a1af99178c4e94e4d6ceb089e91a746110 [^] |
2012-02-22 16:33 | AugustoMauch | Note Added: 0045374 | |
2012-02-22 16:33 | AugustoMauch | Status | resolved => closed |
2012-02-22 16:33 | AugustoMauch | Fixed in Version | => 3.0MP9 |
2012-03-02 15:38 | hudsonbot | Checkin | |
2012-03-02 15:38 | hudsonbot | Note Added: 0045923 | |
Notes |
|
(0045332)
|
mtaal
|
2012-02-21 18:07
|
|
It seems to be related to incorrect auto-save behavior, normally auto-save should be triggered and the system should stop when an error occurs.
gr. Martin |
|
|
(0045365)
|
hgbot
|
2012-02-22 14:39
|
|
Repository: erp/devel/pi
Changeset: 6e76a2a1af99178c4e94e4d6ceb089e91a746110
Author: David Baz Fayos <david.baz <at> openbravo.com>
Date: Wed Feb 22 14:38:41 2012 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/6e76a2a1af99178c4e94e4d6ceb089e91a746110 [^]
Fixed issue 19827: Now you can't leave a form with invalid data
by pressing next/previous statusbar buttons
---
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/form/ob-statusbar.js
---
|
|
|
|
Code reviewed and verified |
|
|
|
|