Question
Wells Fargo
IN
Last activity: 6 Jul 2023 7:41 EDT
Commit method is considering last iteration in loop
Hi, I have a requirement where I have to commit each loop once all iterations are done. I am trying to update WO1 and WO2 which available in loop. Within the loop I am saving the data using Call ObjSave. It should save all pages on current thread once we come out from the loop but commit is happening only last for last WO2. Still WO1 is not commit to the data base. Is there any way we can commit all saved pages at end once all looping is complete.TIA
Updated: 22 Jun 2023 5:16 EDT
JPMC
IN
@Vinay Lakka Commit method commits all the deferred(obj-save) saves of that particular thread. It would help if you can post the screenshot of the logic.
Updated: 6 Jul 2023 7:15 EDT
Wells Fargo
IN
Yes i agree but when it comes to our scenario its failing below are the Act steps, we identified the issue but coming from OOTB activity pxDeleteAssignment.
Steps to Reproduce issue:
1.We need to take the cases which have assignments.
2.In each loop through pxFlow and try deleting each assignment using pxDeleteAssignment.
Added my act steps below.
Updated: 22 Jun 2023 4:40 EDT
Coforge
IN
As you are trying to update different Workobjects in a loop. Each iteration will override the steppage with pyWorkPage of current WO in the loop. As a result you will finally have only last WO data into your step page.
Since you have used commit outside the loop, it will only commit the changes done on last WO. As that's the only step page commit is getting.
In order to make it work, you must have to perform commit inside loop itself after the obj-save.
Also you can refer this thread with similar issue raised.
After a loop, commit method lost data in activity | Support Center (pega.com)
Ordina
NL
@abhirajg@abhiraj
I just did a test run with this, for a list of two cases both cases are updated with the contents of the Property-Set step. The Obj-Save inside 2.3 is creating a list of deferred saves and the commit is commiting all deferred saves.
@abhiraj 
However, I would argue that if you commit case-by-case, you can also do error handling case-by-case. We may want to rollback just a single transaction instead of exiting / doing a rollback if any errors arise at all.@abhiraj
Coforge
IN
thanks, agreed with your last point. committing inside the loop helps us in better error handling.
Wells Fargo
IN
Above scenario works fine. My scenario added above