Question
FPT Nearshore Japan Co., Ltd.
JP
Last activity: 28 Jun 2024 5:14 EDT
Allow multiple users access in case is locked by queue process
My Case Type is setting allow multiple users access. In case having Queue process in activity there is a problem, detail as then When user open task in work Case, queue process will run, until queue process complete, that user was not be able to any other manipulation (ex: back to previous screen, go to the next screen or change and save data)
How can I manipulate continuously while queue process is still running?
Maantic Inc
IN
Queue processor runs on background node, so you wont have control over its actions. Pega will run the process once it finds an available thread automatically.
FPT Nearshore Japan Co., Ltd.
JP
If select option of Locking is allow one users, there is no problem, but when select Allow multiple users, there is a conflict with the queue. Have you used queue with allow multiple users? any way to can use a queue and Allow multiple users together?
Maantic Inc
IN
Allow multiple users mean optimistic locking, so basically more than 1 user/browser requestor can access and update the case at the same time. So that means in your case the queue processor and several other users are updating the case at the same time leading to stale data.
Why do you need optimistic locking in your requirement?
FPT Nearshore Japan Co., Ltd.
JP
thank you for question in anwser, i found reasson of problem. my queue using Obj-Open to open class and checking lock. after do not check this item was solve this problem
Eclatprime Digital Private Limited
SG
correct me if i am wrong allow multiple user on a case is multiple browser requestors that are trying to access the case but where as in the description you mention about batch processor doing something inside case.
basically pega has different types of requestors and its significance is different in different scenarios.
so i want you to check your application configuration where you have a universal node or if u have seperate stream and batch nodes
based on that we can further debug and see what is the issue