Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

DB Lock on the record handling

SA-4671

Summary



User has a requirement to select the value of a database record, perform some logic to calculate a new appropriate value, then update the database record in a synchronized manner. Meaning, perform all three steps essentially in the same transaction such that other users/process don't inappropriately change the value while the logic is being run and the update is made. This is quite similar to the functionality of SPPC_DATA_UNIQUEID stored procedure used to get the next available work object ID. 

Resolution



The explanation for this behavior is as follows: RDB rules run in succession will not be in the same transaction, and thus cannot be used to solve this problem. A stored procedure would be the best and most appropriate solution from several perspectives (simplicity, performance, security, etc.). If this is not possible, a small custom java application could be called via Connect-Java potentially, though this would be a distant second in terms of preferred solutions.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us