Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0015664
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] A. Platformmajoralways2011-01-15 19:442011-03-10 00:00
ReporterrgorisView Statuspublic 
Assigned Tomtaal 
PriorityhighResolutionfixedFixed in Versionpi
StatusclosedFix in branchFixed in SCM revisionadba00c40947
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0015664: User gets stuck in an error - No user exit!

DescriptionOpenbravo´s field validation and error messaging works very well. When a record cannot be saved, a message is fed back to the user about the issue. Mostly it is about a mandatory field that the user forgot to fill. In this case the user fixes it, or decides to close the form and hereby losing the changes ( an interstitial message prompts the user to choose an option ).

However, sometimes the record CAN be saved but one of the values is not correct or causes a conflict. For example: not choosing a payment method. The record is saved and an error appears. In this situation, trying to close the form leads to a repeated error but the dialog (Continue and lose changes or cancel?) does not appear. The user is stuck: document is faulty but can´t be saved either.

The only way to roll back the changes and leave this situation is to use the UNDO button. This is too much to ask from the user.
Steps To ReproduceCreate a sales order and keep the Payment Method empty. Save and close (X) the form.
Proposed SolutionProvide an easier user exit than the UNDO button

Clicking the Close (X) button in a form while having an error should at all times provoke a dialog or possibility to roll back to the last OK state, not only for situations where the record could not be saved.

Clicking the X should prompt the user something like this: "This document contains an error. Click Cancel to go back to the form and solve the problem or OK to continue and roll back the document to the previous state"
TagsNo tags attached.
Attached Filespng file icon Error-Stuck.png [^] (94,837 bytes) 2011-01-15 19:44

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0033667)
hgbot (developer)
2011-01-17 00:09

Repository: erp/devel/pi
Changeset: adba00c40947871307f3720f23d8b33581e1407b
Author: Martin Taal <martin.taal <at> openbravo.com>
Date: Mon Jan 17 00:09:22 2011 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/adba00c40947871307f3720f23d8b33581e1407b [^]

Fixes issue 15664 User gets stuck in an error - No user exit

---
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/ob-standard-view.js
---
(0033668)
mtaal (manager)
2011-01-17 00:10

See also this changeset:
https://code.openbravo.com/erp/devel/pi/rev/aaa5eb1c735e [^]

- Issue History
Date Modified Username Field Change
2011-01-15 19:44 rgoris New Issue
2011-01-15 19:44 rgoris Assigned To => alostale
2011-01-15 19:44 rgoris File Added: Error-Stuck.png
2011-01-15 19:44 rgoris Modules => Core
2011-01-15 19:50 rgoris Assigned To alostale => mtaal
2011-01-15 19:50 rgoris Proposed Solution updated
2011-01-17 00:09 hgbot Checkin
2011-01-17 00:09 hgbot Note Added: 0033667
2011-01-17 00:09 hgbot Status new => resolved
2011-01-17 00:09 hgbot Resolution open => fixed
2011-01-17 00:09 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/adba00c40947871307f3720f23d8b33581e1407b [^]
2011-01-17 00:10 mtaal Note Added: 0033668
2011-03-09 11:12 rgoris Status resolved => closed
2011-03-09 11:12 rgoris Fixed in Version => pi
2011-03-10 00:00 anonymous sf_bug_id 0 => 3204738


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker