I wrote about the roadmap for solving the record locking requirement in "http://forums.vtiger.com/viewtopic.php?t=20680&highlight=record+locking." in August 2008 with 424 views to date, alas no responses.
However, this link "http://forums.vtiger.com/viewtopic.php?t=5368&highlight=record+locking" goes to some length providing a potential solution which appears NOT to have been taken up.
I completely understand the discussion concerning timing out of the record locks.
The difficulty is for how long, might the requested record be locked for?.
In seeing the record change indicator "http://forums.vtiger.com/viewtopic.php?t=34491&highlight=record+change"; it prompted me to think further on this.
I propose a "Record already in use" indicator be flagged to any subsequent users who "Edit" the record where an earlier user has the record open in "Edit" mode.
A dialog box would prompt "Request Write privilege in n seconds" to the second and subsequent users with a dialog box of "Confirm Yes/No"
A corresponding dialog box "Write privilege in n seconds received for this record" would pop to the first user with "Accept/Deny"
"Accept" would allow the request (second user) to be written with any changes waiting to be committed by the first user being lost. They would have their view refreshed with the new data.
"Deny" would not allow the second user's request to be written, any changes waiting to be committed by the first user would be committed. The second user would lose any uncommitted changes and would have their view refreshed with the new data. The second user would then make their changes if still required.
Where there is no response from the "Write privilege in n seconds received for this record" ie. the first user, then the requestors update will proceed after the nominated seconds have passed.
Where the first user has say left their workstation, or been working in another application past the nominated "n seconds", they will have a dialog box saying "Write privilege in n seconds received for this record - expired" and the record will be written to by the second user. The first user will then have to reenter their changes if still required.
Indicating to both parties there is a potential conflict is the essential function of this process.
I believe this will get round the problem of actually locking records over the web connection.
click (http://forums.vtiger.com/viewtopic.php?t=38502) to go to the post on vtiger forums
check this link below it will help you to solve all the problems
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.