Posted: 19 Nov 2018 3:22 EST Last activity: 19 Nov 2018 10:10 EST
What is better practice Process API to use rather than Obj-Save & Commit
I know it is a best practice to let Pega to handle Save & COMMIT but sometimes developer needs to do the same anyways. In that case, I have been using Obj-Save and COMMIT method but I heard that there are better Process APIs to use. What is it?
1. Work-.Save really won't need Commit operation? How about Work-.commitWithErrorHandling API? I thought this is more Commit operation and better be used along with Work-.Save API.
2. Flow action does implicit Save / Commit operation by Pega Platform but if I want to save Work Object from a button that calls a custom activity on a section, I guess this is a valid use case to use these Work-.Save operation. Am I right?