Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0006986Openbravo ERP08. Project and service managementpublic2009-01-19 12:132009-02-03 16:21
plujan 
iperdomo 
normalminorhave not tried
closedno change required 
30
pi 
 
Core
No
0006986: Autosave does not show a message when clicking New button
I am editing an existent record, then I create a new one by clicking the New button. New window is displayed, but I receive no message about saving the record I was working with.
Behavior is different if I click "Save and New" button. When clicking that button I get a message on New window "1 row/s updated". That should be the expected behavior also when clicking in new, since edited record was saved.
1. Edit a record.
2. Click on New
3. New window is displayed with no message.
4. Repeat the edition
5. Now click on Save and New button instead
6. New window is displayed and now there is a message
Show the message when clicking on New if autosave feature is enabled.
QA_review_pre_beta
Issue History
2009-01-19 12:13plujanNew Issue
2009-01-19 12:13plujanAssigned To => iperdomo
2009-01-19 12:13plujansf_bug_id0 => 2519468
2009-01-19 12:13plujanRegression testing => No
2009-01-19 12:14plujanversion => trunk
2009-01-19 12:14plujanTarget Versiontrunk =>
2009-01-19 12:14plujanTag Attached: QA_review_pre_beta
2009-01-20 06:38iperdomoStatusnew => acknowledged
2009-02-03 16:06rgorisNote Added: 0013090
2009-02-03 16:19iperdomoStatusacknowledged => scheduled
2009-02-03 16:19iperdomofix_in_branch => trunk
2009-02-03 16:21iperdomoStatusscheduled => closed
2009-02-03 16:21iperdomoNote Added: 0013091
2009-02-03 16:21iperdomoResolutionopen => no change required

Notes
(0013090)
rgoris   
2009-02-03 16:06   
We can get rid off the "1 row/s inserted" message bar in autosave mode. The reason is that the user will always be notified in case a record is not saved and the user tries to navigate away (for example to create a new record).
(0013091)
iperdomo   
2009-02-03 16:21   
The autosave process notifies the user if a problem occurs. All messages are useful in context of the current record, that's why it not makes sense to display a '1 row/s inserted' message on the *NEW* record.