Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0039437Openbravo ERPB. User interfacepublic2018-10-11 13:132022-02-01 08:07
Reporterplujan 
Assigned ToTriage Platform Base 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusnewResolutionopen 
PlatformOS5OS Version
Product Versionmain 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0039437: [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.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0040179 closed alostale Validations defined at column level must display an appropriate message to the user 
related to defect 0041821 closed jarmendariz Messages in header tab should disappear when a child tab record is edited 
Attached Filespng ErrorSalesOrderLine.png (84,761) 2018-10-11 13:13
https://issues.openbravo.com/file_download.php?file_id=12261&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2018-10-11 13:13plujanNew Issue
2018-10-11 13:13plujanAssigned To => platform
2018-10-11 13:13plujanFile Added: ErrorSalesOrderLine.png
2018-10-11 13:13plujanModules => Core
2018-10-11 13:13plujanTriggers an Emergency Pack => No
2018-10-26 10:43alostaleNote Added: 0107613
2018-10-26 10:43alostaleTypedefect => design defect
2018-10-26 10:44alostaleAssigned Toplatform => dbaz
2018-10-26 10:44alostaleStatusnew => feedback
2018-10-29 10:23dbazNote Added: 0107631
2018-10-31 18:38dbazStatusfeedback => new
2019-02-22 12:44alostaleRelationship addedrelated to 0040179
2019-09-17 11:19dbazNote Edited: 0107631bug_revision_view_page.php?bugnote_id=0107631#r19383
2019-09-17 12:37gorkaionIssue cloned0041821
2019-09-17 12:37gorkaionRelationship addedrelated to 0041821
2019-09-17 13:03dbazAssigned Todbaz => platform
2022-02-01 08:07alostaleAssigned Toplatform => Triage Platform Base

Notes
(0107613)
alostale   
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?
(0107631)
dbaz   
2018-10-29 10:23   
(edited on: 2019-09-17 11:19)
If in the header you leave a mandatory field empty, and you move to the child, an error is shown in the header. If you go back to the header, and start editing, the message dissapears. The same behavior should apply in the opposite case, which is the one reported in the issue.