The information in this article applies to:
Product: Metastorm BPM (e-Work)
Version: 6.x 7.x
Issue
- Folders in the Services Manager are shown as being locked even though the folder lock timeout has expired.
Discussion
- This is expected behavior. The locks placed on a folder are not actively removed by the Process Engine just because the folder lock timeout has passed.
- Once the timeout has expired, a user other than the one who locked the folder can take an action on the folder even though it shows as being locked. If that happens, the lock shown in the Services Manager will have a new timestamp and new locking user.
- The eActionTime, eActionName, and eActionUser columns in the eFolder table are populated when a folder is locked, and they stay populated after the timeout has expired. They are updated when a user takes an action and creates a new lock.
- Here is an example that assumes a folder lock timeout of 60 minutes:
11:00 - Ed takes an action on Folder99. Folder99 is now locked by Ed.
11:59 - Kim attempts to lock Folder99. She is told the folder is locked for Ed.
12:15 - Ed can submit the form without a problem. If Ed has not submitted the form, the Services Manager will still show Folder99 as being locked by Ed even though the timeout has expired. However, Rodney is able to open the folder and take an action as more than 60 minutes have passed since the folder was locked. The folder is now locked by Rodney for 60 minutes and the Services Manager would show the locking details with Rodney as the user and with the new timestamp.
