Locking Strategy for our business scenario
I have a business scenario where the user create child cases (implemented using pxaddchildwork from an activity) from the parent case and each parent case may have around 75 child cases.So 75 members should work on these cases simultaneously .
My understanding is if I use default locking the child case takes a lock on the parent case so if another user opens a different child case pega throws an error that we do not have a lock on parent case. So we are planning to use optimistic locking.
Is my understanding correct?
What are the disadvantages of using Default locking with do not lock parent on child case i know it does not update properties like covered count open .Has anyone faced any issue with this configuration as it is not recommended by pega?