I have tried locking the instance belongs to a concrete class that has Allow Locking? selected in the class rule. But even the class (Concrete) that belongs to a class group is allowing lock on the corresponding instance of the class. how classes that belongs to a class group are allowing a lock?
how pega is handling locks in the case of class belongs to a class group (this will not have any lock option on the class rule form) Please suggest.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
I have tested whenever if we check the allow locking check box on the class and it will not allow us to save/delete the class instances without getting lock on that instance.
and also I have tested if we don't have any allow locking check box on the class and it will not allow us to save/delete the class instance without getting lock on that instance.
so what is the difference here to have allow locking feature on the class form and does not have allow locking feature on the class form?
one more thing why we have only "is allow locking option" for the class that does not belongs to a class group. why we don't have any option for lock on the class that belongs to a class group? please suggest.
I think there are security reasons to do so, also if we 'allow locking' on class group/workpool we can lock an object of the class/worktype belonging to that class group since it is certain that you are picking an object of the same workpool hence you need not check for 'allow locking' in all classes that already belong to a class group/workpool.
Posted: 6 years ago
Posted: 30 Oct 2017 14:19 EDT
Pardeep Sharma (Pardeep_Sharma)