How to have Persistent Data in DB without using commit in an activity called in a flow
What are the methods/how to have persistent data save in an activity called in a utility shape in flow (before automatic commit) without using explicit commit/ commitwitherrorhandling.
Thanks!!!
Accepted Solution
Pegasystems
US
If the object you are saving to is the primary work object (the one whose flow the utility shape is in), then don't save at all. Just update the property. The system will save it for you.
If the object you are saving to is another object, then use obj-open with locking and then use write-now on the save.
It is important not to save or commit the primary work object, because if the system ever has to roll back, it will cause errors such as "flow not at task" or "flow removed".
The general difference between save with write-now and commit is that the first saves only one specific object, whereas commit saves ALL the objects that have data waiting to save.
/Eric
Accepted Solution
Pegasystems
US
If the object you are saving to is the primary work object (the one whose flow the utility shape is in), then don't save at all. Just update the property. The system will save it for you.
If the object you are saving to is another object, then use obj-open with locking and then use write-now on the save.
It is important not to save or commit the primary work object, because if the system ever has to roll back, it will cause errors such as "flow not at task" or "flow removed".
The general difference between save with write-now and commit is that the first saves only one specific object, whereas commit saves ALL the objects that have data waiting to save.
/Eric