Optimistic locking for data instance
What is the standard Pega way to implement optimistic locking for data instances?
I know that Pega checks UpdateDate time and other props in order to check fo conflicts for updating of work objects (in case of optimistic locking).
Is there any standard API or activities or approaches to implement similiar mechanism for data instances?
Pegasystems Inc.
IN
>>> locking for data instances. please share your thoughts/comments, Thank you!
Sberbank
RU
What do you suggest?
I am familiar with this setting.
Pegasystems
US
So, in answer to your question about data instances, can you use the checkbox illustrated above, plus check the "optimistic locking" box as well ? Does that work ? /Eric
Sberbank
RU
Hello.
I tried to uncheck "Allow locking" on data instance.
Processing of this data instance is done by Obj-Open / Obj-Save activity methods.
Also tried to use activity Save and ListItemSave instead of Obj-Save.
Expected to get message like: Object was modified by other user, please resubmit.
> check the "optimistic locking" box
Never saw this checkbox for data classes. Only for work classes.
Pegasystems Inc.
IN
8<---------------------------------------------------------------
I tried to uncheck "Allow locking" on data instance.
Processing of this data instance is done by Obj-Open / Obj-Save activity methods.
Also tried to use activity Save and ListItemSave instead of Obj-Save.
Expected to get message like: Object was modified by other user, please resubmit.
----------------------------------------------------------------------------------------------------------------->8
Please share the observations with 'Allow locking' option enabled. Thank you!
Sberbank
RU
'Allow locking' option enabled means that save operations requires lock. So this is default locking.
In this topic we discuss optimistic locking.