Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Abhishek Choubey (AbhishekC1725)
Zensar Technologies Ltd
Abhishek Choubey
Zensar Technologies Ltd
IN
AbhishekC1725 Member since 2021 127 posts
Zensar Technologies Ltd
Posted: Jul 6, 2023
Last activity: Jul 7, 2023
Posted: 6 Jul 2023 13:36 EDT
Last activity: 7 Jul 2023 10:27 EDT
Closed
Solved

Guardrail Warning On Using Commit

Use of the Commit activity method interferes with the PRPC transaction model and may result in stale database records. Consider removing; In most cases, PRPC already does a commit at the end of the transaction How to remove this Guardrail warning.

 

Any other activity we can use in place of Commit

 

Activity warning

 

 

***Edited by Moderator Marissa to add Capability tags***
To see attachments, please log in.
Pega Platform 8.7
Data Management
Security
Dev/Designer Studio
Java and Activities

  • Vitor Alcantara de Almeida

Accepted Solution

Posted: 1 year ago
Updated: 1 year ago
Posted: 6 Jul 2023 17:11 EDT
Updated: 7 Jul 2023 10:27 EDT
Bas Groeneveld (BasRulesMatter! )
Ordina
Pega Developer
Ordina
NL

@AbhishekC1725 You could consider using the OOTB Work- commitWithErrorHandling activity or wrap the commit method in your own activity that is then re-used everywhere. In any case, this shouldn't be about not generating the guardrail warning - it should be about carefully considering if you need an activity and if / how you want to handle transactions and errors. 

To see attachments, please log in.
  • Joyashish Sircar Abhishek Choubey Akshith Reddy Thalla Vitor Alcantara de Almeida

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

Pega Collaboration Center 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