Are there clear best practices in regards to commits ?
Hello,
There is a lot of contradicting information that is circulating in the community in regards to commits.
As a general rule, it's accepted that commits are "bad" and we should almost always let Pega handle commits through flow or case processing.
That lead to some weird practices like using wait shape to force a commit during flow processing.
So here is my question :
- What is the danger in calling "CommitWitherrorHandling" in a utility shape in a flow?
- What is the danger in calling a "manual" call to commitwithErrorHandling in an activity that is executed during case processing?
- Finally, if you have no other choices and have to make a manual commit outside of a case, so you have no access to commitwithErrorHandling activity. What should you pay attention to? What kind of error handling / rollbacking should you put in place?
Kind regards
Pegasystems Inc.
FR
I think the main issue with manual commit is to generate transaction issues.
So yes it isn't recommended to add commit operations inside your lifecycle. In theory the next assignment or wait shape will commit your saved processes.
I guess if you have to work with a manual commit anyway, you will need to the lock back on your object because the commit will release it for sure.