Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0028349Openbravo ERPB. User interfacepublic2014-12-04 17:162022-02-01 08:05
airaceburu 
Triage Platform Base 
normalminoralways
acknowledgedopen 
5
3.0PR14Q3.3 
 
Core
No
0028349: Save button is disabled when saving a sales order without Scheduled Delivery Date
The mandatory field "Scheduled Delivery Date" is not mandatory if the transaction document selected is "POS Order". The save button is disabled but if the user clicks the "x" and close the form view the record is saved without warnings.

This was found in Q3.3 but is also in pi.
1 Go to Sales Order Window
2 Press Ctrl + D to create a new record
3 Select a business partner
4 Save the record
5 Delete the content of the field "Scheduled Delivery Date"
6 Change the transaction document field to "POS Order"
7 Change the order date
8 Close the record with the "x" button, as the save button is disabled

Now the record has the new order date set
No tags attached.
Issue History
2014-12-04 17:16airaceburuNew Issue
2014-12-04 17:16airaceburuAssigned To => dbaz
2014-12-04 17:16airaceburuModules => Core
2014-12-04 17:16airaceburuRegression level => Production - QA Approved
2014-12-04 17:16airaceburuTriggers an Emergency Pack => No
2014-12-04 17:28alostaleRegression levelProduction - QA Approved =>
2014-12-04 18:27airaceburuSummaryUser can save orders without Scheduled Delivery Date => Save button is disabled when saving a sales order without Scheduled Delivery Date
2014-12-04 18:27airaceburuDescription Updatedbug_revision_view_page.php?rev_id=7218#r7218
2015-01-14 16:13dbazNote Added: 0073495
2015-03-11 11:08alostaleStatusnew => acknowledged
2015-03-17 14:38alostaleAssigned Todbaz => platform
2022-02-01 08:05alostaleAssigned Toplatform => Triage Platform Base

Notes
(0073495)
dbaz   
2015-01-14 16:13   
In this case (with "POS Order" set and empty "Scheduled Delivery Date"), since all the mandatory fields you are viewing in the form are filled, you can think that the "Save" button should be enabled (that's true), the problem is that in the grid view you continue viewing in this column a not filled mandatory field (even if you have a display logic).

So, just avoid the current "X" button behavior doesn't solve the underlying issue. To properly solve the situation, a new "Mandatory Logic" feature should be implemented.