Jeff,
The workflow lock should be set when a work item is launched from Change Notification. Since the event causing the new work item is queued, there may be a minute or two before the work item is actually launched. Once that work item arrives at a manual activity that is configured to be linked to EPIM, then the lock should be set. If it is not set, then I suggest you open a support ticket so it can be investigated - especially if it can be reproduced consistently. If the work item does not arrive at a manual activity, then it's possible it won't have the lock set. Or if the record has more than one work item launched for it and one of them ends, the record will likely become unlocked even though there's still an active work item for it.
One thing I have observed is the completion of a work item not clearing the workflow lock flag. This was in a test environment and priorities were such that the underlying cause was not investigated, but in that case, the Unlock Workflow activity was added to be the last activity in the workflow to ensure the lock was released. There is no corresponding activity to lock the record.
In general, a given repository record should only be anchored to one work item at a time. The UI will not allow a second work item to be launched if there is a lock on the record. However, this mechanism will not prevent a work item being launched from Change Notification or one of the Create Work Item activities within a workflow - it is the responsibility of the implementer of these mechanisms to ensure a second work item isn't launched.
-Brian
------------------------------
Brian Zupke | Senior Technical Support Engineer
Winshuttle North America | 9099009179
------------------------------