pxLockHandle population in prpc 7.x
Hi All - I am trying to figure out when and how value for pxLockHandle is populated for a top level case when we create top level case from case designer in prpc7.x. Till now my understanding was that it would be populated only if we have child parent relationship for a covered object but I am seeing some of the top level cases having value for pxLockHandle and some do not. Can someone provide some info what could be the situation or scenario when it is populated for few cases but not the other. I don't see customized version of DetermineLockString activity.
Pegasystems Inc.
IN
pxLockHandle property should populate for any case. for work pages it will be populated with DetermineLockString activity.
Check whether DetermineLockString activity is fired or not in non working scenario
JPMC
US
Thank you for your response Prajendra! I am not sure if I can agree with you on this. If you look at addwork, it doesn't call WorkLock activity if it is not a cover object and in 7.1.9 I can see the reference of DetermineLockString only in worklock activity in work layer.
CA
Hi @DPSSingh, Please see attached screenshot showing XML of pyWorkPage. I couldn't find pxLockHandle anywhere. Can you trace when creating a new work object and check if Param.CoverHandle!="" turns to true and then check the value of CoverHandle?
JPMC
US
Sure Nikhil, I can do that. But in my original post that is why I mentioned that this is happening for some cases(toplevel) only i.e. Top-Level case type without any spawning any child case. As per my understanding we should not see pxLockHandle for TopLevel cases as per this condition in addwork activity.