| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Technical Name |
concurrency |
| Website | http://www.microcom.ca |
| Versions | 8.0 9.0 |
Concurrency
Intercept concurrent access to prevent data loss.
Prevent data loss
Keep last modification's timestamp of current form to verify that no other user have changed it since last loading.
When saving the edited form, the user is warned of the changes that have been made on the meantime. The user must reapply the changes on the updated form.
The payment term changed while the user was trying to modify a field.
A closer look
Limitations
- Only save buttons and of the type object (calling a model's function) are protected.
- Planned actions and other server tasks could overwrite users changes that have been applied at the same time.
- Some business rules are implemented in the user interface making fields as readonly on certain conditions. A concurrent access allows prohibited modifications. XML should be examined to extract these rules.
- Messages, Followers and binary files (images) aren't tracked.
- Child records are tracked and parent's saving is prevented if a child's modification occurs. (e.g. Sale Order Line changed)
- Changing the format of write_date to include microseconds as stored in BD, so that we can manage conflicts happening within the same second.
- Changing the format of write_date to include microseconds as stored in BD, so that we can manage conflicts happening within the same second.
Remaining Points
- Workflows don't pass the context to the server, in this case, conflicts aren't detected.
- Checking the list of Access rights when editing a User and add those changed to the displayed message.
- Adding 'Manage changes within the same second' in the configuration to prevent problems caused by changing the format of write dates (see limitations).
Maintainer
This module is maintained by Microcom.
Please log in to comment on this module
There are no ratings yet!
Do you have 11 version?