Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] B. User interfaceminorhave not tried2018-10-11 13:132018-10-31 18:38
ReporterplujanView Statuspublic 
Assigned Todbaz 
PrioritynormalResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionmainSCM revision 
Review Assigned To
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0039437: [PR18Q4] Error message after a wrong entered value does not disappear when values are fixed

DescriptionWhen trying to create an incomplete Sales Order line, an expected error message is shown. But after the data is corrected and the record successfully saved, the error message does not disappear.
Steps To Reproduce1. Enter as F&B admin
2. Open Sales Order window
3. Create a new header with valid data
4. Focus the Lines tab and click the "new in form" button.
5. Do not complete any data and change the focus back to the header
6. As expected, a red message in the line will alert the user of the missing data.
7. Return to the line and complete the data. Note that after saving the error message is not removed (see attached screenshot)
8. Complete the Sales Order. Note the message is still there.
9. Create a new Sales Order header. Note the message still there.
10. Create a new Line. Note the message still there.
TagsNo tags attached.
Attached Filespng file icon ErrorSalesOrderLine.png [^] (84,761 bytes) 2018-10-11 13:13

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0040179 closedalostale Validations defined at column level must display an appropriate message to the user 

-  Notes
alostale (developer)
2018-10-26 10:43

Moving to design defect: currently, messages are designed to be removed only after user closes them; there is no way to define any other automatic mechanism to close them.

DBA: can you comment on how this should behave?
dbaz (developer)
2018-10-29 10:23

Testing in livebuilds, I am able to get the Error Message automatically disappear just by fixing the field that generated the error.

Here it is a video: [^]

In the second part of the video, there is another different issue: I am able to leave the header of the BP window in error status (by going to the child tab), but without showing the error message.

- Issue History
Date Modified Username Field Change
2018-10-11 13:13 plujan New Issue
2018-10-11 13:13 plujan Assigned To => platform
2018-10-11 13:13 plujan File Added: ErrorSalesOrderLine.png
2018-10-11 13:13 plujan Modules => Core
2018-10-11 13:13 plujan Triggers an Emergency Pack => No
2018-10-26 10:43 alostale Note Added: 0107613
2018-10-26 10:43 alostale Type defect => design defect
2018-10-26 10:44 alostale Assigned To platform => dbaz
2018-10-26 10:44 alostale Status new => feedback
2018-10-29 10:23 dbaz Note Added: 0107631
2018-10-31 18:38 dbaz Status feedback => new
2019-02-22 12:44 alostale Relationship added related to 0040179

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker