We have a business ask, where they want to allow multiple users to update a case at any point of time. We are looking at options. It will be helpful if anyone suggests any ideas.
We looked at multiple assignments (in parallel). But with any approach, we are getting into a state, where when one person commits, other persons updates to the case are lost (as expected though). Any suggestion is greatly appreciated!
@RAJESWARAN check for optimistic locking strategy. It allows multiple users to update a case . Whoever submits 1st then the other user gets a message stating that changes have taken somewhere else please refresh the case to see updated data.
Note : In this method the second user looses his changes , he has to enter all the details again.
You can make use of optimistic locking. But the problem here will be when multiple users accessing the case at a same time and when 2nd user tries to submit the case, they will get the error message and system will ask them to refresh the screen. During this refresh data will be getting loaded from DB and 2nd user data will get flushed out.
In-case if you don't want 2nd user data also not to get flushed out, then based on business logic you can try to change the logic which Pega will do in refresh button, you can take back-up of 2nd user data and then you can do page compare with DB data and then reframe the case data. For comparing 2-page data and to find what all data modified you could make use of pxComparePages OOTB activity.
Posted: 2 months ago
Posted: 31 Oct 2022 0:47 EDT
Rajeswaran Srinivasan (RAJESWARAN)