Madhumita Singh (Madhumita_Singh)
Cognizant Technology Solutions

Cognizant Technology Solutions
Madhumita_Singh Member since 2015 1 post
Cognizant Technology Solutions
Posted: October 29, 2020
Last activity: November 18, 2020
Posted: 29 Oct 2020 14:10 EDT
Last activity: 18 Nov 2020 18:27 EST

Database triggers have executed but obj-save has failed from a service context


We have multiple obj-save in a service activity without write Now option selected, this saves the data in multiple database tables. Each table has an associated DB trigger. 

After the service is fired, data is saved and the database trigger gets fired which further updates the record, i.e there are two updates one from Pega end and another at database end through the DB triggers.

There is a final commit at the end of the service activity. If say, the 5th Obj-save operation fails in the service activity causing all transactions to rollback(as there were no commits in between), should we still see the effect of trigger on the database table for any of the earlier obj-save operations?

Could someone please help with this question. We are facing this issue in Production environment where the database triggers have fired but transaction has rolled back.

***Edited by Moderator Marissa to change type from Pega Academy to Product, update Product details and Platform Capability tags****
Pega Platform Data Integration