|
(0020853)
|
|
alostale
|
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/ [^]
|
|