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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0010896
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajorhave not tried2009-10-07 13:202009-10-24 00:00
Reportereduardo_ArgalView Statuspublic 
Assigned Toalostale 
PriorityimmediateResolutionfixedFixed in Version2.50MP8
StatusclosedFix in branchpiFixed in SCM revisionad129c7d1b62
ProjectionnoneETAnoneTarget Versionpi
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

0010896: Save action should not take into account elements that can not be updated by user (Example: buttons)

DescriptionSave action should not take into account elements that can not be updated by user (Example: buttons)
Tagsmain
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0020853)
alostale (manager)
2009-10-07 15:36
edited on: 2009-10-07 15:38

The solution for this issue cannot be not saving not updatable fields when the save action is performed, this would cause not saving read-only fields that could be modified by callouts and therefore should be saved.

Here the problem appears when the user opens a record in a tab and before saving it there is a modification on it (it can be done by another user or by a process). In this case when the record is tried to be saved, it's updated with obsolete information.

Therefore the solution for this issue would be to implement a locking mechanism for WAD windows. This locking mechanism at this stage will be quite light. It will just read the last updated time for the record when it is opened and before saving it again it will check the actual updated value in database is the same that was read at the beginning, and in case they differ no save action will be allowed.

**Note for QA**
This new feature is needed to be deeply tested because it affects the way records are saved. To facilitate the isolation for this testing, this implementation is going to be developed in a separate hg repository:

https://code.openbravo.com/erp/devel/pi-locking/ [^]

(0021345)
hgbot (developer)
2009-10-22 18:17

Repository: erp/devel/pi
Changeset: ad129c7d1b6285797d48188320a26d51bffbefbe
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Thu Oct 22 18:16:52 2009 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/ad129c7d1b6285797d48188320a26d51bffbefbe [^]

fixed bug 0010896: Implemented locking mechanism

---
M src-db/database/sourcedata/AD_MESSAGE.xml
M src-wad/src/org/openbravo/wad/Configuration_Edition.xmlxml
M src-wad/src/org/openbravo/wad/Template_Edition.html
M src-wad/src/org/openbravo/wad/datasource.xsqlxml
M src-wad/src/org/openbravo/wad/javasource.javaxml
M src/org/openbravo/base/secureApp/HttpSecureAppServlet.java
M src/org/openbravo/erpCommon/utility/NavigationBar.java
M web/js/utils.js
---

- Issue History
Date Modified Username Field Change
2009-10-07 13:20 eduardo_Argal New Issue
2009-10-07 13:20 eduardo_Argal Assigned To => alostale
2009-10-07 13:20 eduardo_Argal Status new => scheduled
2009-10-07 13:20 eduardo_Argal fix_in_branch => pi
2009-10-07 15:36 alostale Note Added: 0020853
2009-10-07 15:38 alostale Note Edited: 0020853
2009-10-13 10:31 alostale Status scheduled => resolved
2009-10-13 10:31 alostale Fixed in SCM revision => https://code.openbravo.com/erp/devel/pi-locking/rev/1ffa395af0f7 [^]
2009-10-13 10:31 alostale Resolution open => fixed
2009-10-22 11:23 plujan Status resolved => closed
2009-10-22 18:17 hgbot Checkin
2009-10-22 18:17 hgbot Note Added: 0021345
2009-10-22 18:17 hgbot Status closed => resolved
2009-10-22 18:17 hgbot Fixed in SCM revision https://code.openbravo.com/erp/devel/pi-locking/rev/1ffa395af0f7 [^] => http://code.openbravo.com/erp/devel/pi/rev/ad129c7d1b6285797d48188320a26d51bffbefbe [^]
2009-10-22 19:26 psarobe Tag Attached: main
2009-10-23 16:04 plujan Status resolved => closed
2009-10-23 16:04 plujan Fixed in Version => 2.50MP8
2009-10-24 00:00 anonymous sf_bug_id 0 => 2885057


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker