Error handling in database operations
Hi,
I usually write database operation as below - Pega-New, Property-Set, Obj-Save, and Commit. I don't know how to write error handling if anything goes wrong during these steps, but I think this is not great. For example, shouldn't I always include Rollback steps? If so, where and how? Or, if there are any more standard practice to handle error, please let me know. Screenshot helps.
Thanks,
***Edited by Moderator Marissa to updat General to Product; update platform capability tags***
Updated: 4 May 2020 22:18 EDT
Pegasystems Inc.
IN
Hi ,
Thanks for posting the query.
You can use OOTB activity CommitWithErrorHandling which will take care of the rollback if any error during the commit operation and it will also do the necessary work objects unlocking if you select the commit on release option in Obj-open or Obj-open by handle during the current transactional process.
IT Solution Service
SG
Hi,
Thanks for the info. What if the target object is a Data instance instead of Work instance? This commitWithErrorHandling API is placed at Work- class, and therefore I am not able to call it for Data instance?
Thanks,
Updated: 14 Jun 2021 7:38 EDT
Pegasystems Inc.
IN
For Data instances, you can call "commitWithErrorHandling " by using Call Work-.CommitWithErrorHandling.
Updated: 14 Jun 2021 7:38 EDT
Pegasystems Inc.
IN
We can use JUMP condition to check "StepStatusFail" and when it's true we can jump to later steps as per requirement.
Pegasystems Inc.
IN
Hi,
You can use jump condition to check the step status on obj-save step. If stepstatus is good then you can continue to the next step. Else you can log a message or set the error(using @pxAddMessageToPage function). Generally, the log message is used in agent activities. And one more best practice is to remove the temppage.
IT Solution Service
SG
Thanks. Since I want to establish the standard for my team, could you please review below screenshot is what you meant?
Using pxAddMessageToPage is more informational purpose, right? My other questions are:
(1) Even without using this function, wouldn't Pega record error in clipboard anyways if Obj-Save fails?
(2) I was more concerned if I should do some kind of database operation like Rollback. Or any of these are not required as Obj-Save operation was not even successful?
Thanks,
Pegasystems Inc.
IN
Hi,
1. Without using this function, Pega will not record the error implicitly. You can also use the Page-set-messages method to set the error. But without using any method or function Pega will not record the error implicitly.
2. Instead of the commit method, you can call CommiwithErrorHandling.If this activity is used and the commit fails the activity itself takes care of rollback.