Obj save writenow Vs Commit
Hi,
Maybe it's a basic question, as per my understanding the data which is in the differed list will get override by data at commit step
Please refer to the screenshot attached for a better understanding.
I strongly believe the value should be 10, how it can be 5? Please make me understand.
Thanks
***Edited by Moderator: Pallavi to update platform capability tags***
Accepted Solution
Updated: 12 May 2020 21:14 EDT
Pegasystems Inc.
US
I just verified that this image is correct with an activity as follows: 1. Set properties on OperatorID
- Set .pyLabel to "first label"
2. Obj-Save on OperatorID 3. Set properties on OperatorID
- Set .pyLabel to "second label"
- Set .pyDescription to "new description"
4. Obj-Save with write now on OperatorID 5. Commit
Why? It's important to understand that the OperatorID page IS saved in step 4. That save to the database happens first. However, the Obj-Save in step 2 is put into a queue which is only emptied when a "Commit" is called. So, when Commit happens a message goes out saying: "send all outstanding requests to the database" which will overwrite the successfull obj save on step 4. Interestingly, at the end of this pyDescription is not "new description." It is whatever it was during step 2.
CBA
AU
Thank you PICADA, for the detailed explanation very helpful. :)
Updated: 14 Jun 2021 7:38 EDT
JP Morgan Chase & Co.
IN
Please find the below article which has the same question.
https://collaborate.pega.com/question/regarding-obj-save-and-commit-operation
Cognizant
IN
Hi Sam,
Please refer following link for more information
https://community.pega.com/sites/default/files/help_v63sp1/Content/methods/obj-save/obj-save.htm
Thanks
CBA
AU
Thanks much everyone for the replies.