Question
Knowledge Expert
FR
Last activity: 4 Jan 2019 7:15 EST
Automatic commit doesn't happen on end of Utility or Flow
I have following setup:
Case Type with 3 Stages:
- On 1st I have an assignment with post activity where I do Obj-Save (without write now) on some Data Type
- On 2nd I'm checking that Data Type, using Data Page, and based on the check - skip or no few steps
- On 3rd - another assignment (doesn't matter what)
Problem that after post activity on 1st step instance of Data Type hasn't got committed to database. It got committed only before Assignment on 3rd step, so check on 2nd step failed. I can see it clearly from Tracer.
Why is it so? As far as I know Pega should commit everything automatically after every Utility shape, Assignment and end of flow.
Pegasystems Inc.
FR
Hello,
I'm not completely sure but I don't think you should be expecting a Commit after each Utility shape or each End of flow.
On assignments yes for sure.
Knowledge Expert
FR
My assumption is based on responses from Pegasystems employees:
https://collaborate.pega.com/question/does-pega-save-or-commit-pyworkpage-end-every-flow - "Yes, Pega commit at the end of each flow"
Or based on published documentation:
https://community.pega.com/knowledgebase/articles/how-correct-commit-warning-activity-rules - "Flow processing performs commits automatically when the flow ends and when an assignment is created or completed"
Pegasystems Inc.
FR
All right,
Maybe I'm wrong then. Having said that nothing, nothing about Utility shape.
Knowledge Expert
FR
That's fine, not on Utility shape then.
But my Obj-Save happens on the end of Assignment and after it - end of the flow. But still - no commit. Only before next Assignment.
Cognizant
SE
Knowledge Expert
FR
Good guess, but I tested it now with pyWorkPage as well - commit happens only before next Assignment, not after current or flow end.