What is better practice Process API to use rather than Obj-Save & Commit
Hi,
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?
Thanks,
Accepted Solution
Pegasystems Inc.
IN
Please find my answers below.
1) commitWithErrorHandling API is just used to commit all the changes. It won't do any work object saves. You can use either of these APIs depending on your use case.
2)Correct. I am assuming that button (which calls custom activity) is in Review harness so that you don't end up in locking issues.
Pegasystems Inc.
IN
It is always suggested to use Work-.Save activity to save and commit work when it comes to process related APIs.
Save activity internally takes care of commit also along with error handling and releasing lock.
Let us know if you need more information :)
IT Solution Service
SG
Thanks for the info. Two questions:
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?
Thanks,
Accepted Solution
Pegasystems Inc.
IN
Please find my answers below.
1) commitWithErrorHandling API is just used to commit all the changes. It won't do any work object saves. You can use either of these APIs depending on your use case.
2)Correct. I am assuming that button (which calls custom activity) is in Review harness so that you don't end up in locking issues.