here, I am seeing that parent.change is having 2 tasks. I go and open a task associated to the change and another operator logs in and selects the second task associated to the same change . He is prompted with the message, the record is locked by another user .
Is this behavior, because both the users trying to access the cm3t record from the same parent change ?. The users have selected individual records in a different file and why this behavior ?.
The object record of cm3t says, the locking is done on the record and the parent change also . Has an1 faced this before ?. Please guide.
In order to modify a module record, the user has to be able to establish a lock. If User 1 locks C12345, then User 2 would be unable to modify that record because the lock attempt would fail. In this example, there is only one lock for the work-flow to check.
When Parent Locking is enabled, two locks are created when a user modifies a child record. If User 1 locks T1, then it will also lock C1. There will actually be two locks in System Status: cm3t;T1 and cm3r;C1.
When User 2 attempts to lock T2, it will fail because the Parent Change is locked. By design, the lock workflow prevents User 2 from modifying T2 because it can't establish both locks (cm3t;T2 and cm3r;C1).
Note: If the lock attempt occurs when accessing/displaying the Tasks, then this implies that Lock on Display evaluates to true (also found in the cm3t Object record but not enabled OOB).