How can I eliminate Commit guardrail warning?
Hello,
I know using Commit method in an activity is a bad practice in general. If the activity is in the flow processing we should rely on PRPC as system will automatically commit the changes implicitly. However, if we are updating data instances outside of work flow (ex. Job Scheduler), we still need to do commit by ourselves. When I use Commit method, system throws below warnings right away.
The warning is severe, and I want to eliminate this message. What is the most common alternate approach? I know there is an OOTB activity called "commitWithErrorHandling" but it is only available in Work- class.
What if the activity is outside of Work- class?
Also, another approach I know is to change the activity type from "Activity" to "Utility" in Security tab, but I don't think it is a good practice to change this uniformly if it is not really a utility, only for the purpose of eliminating the warnings.
Regards,
IT Solution Service
SG
No, there is no such activity called "pySaveAndCommit" in the latest version 8.8.
Pegasystems Inc.
CA
@CloeW938 , I totally understand. Why don't you justify the warnings and move forward as this is required in your use case?
Another thought - If this is being used widely in your application, Create a wrapper activity to do a commit and call the wrapper activity whenever commit is required. Justify the guradrail warning for Wrapper activity.
I agree with your thoughts masking the warning is not a best practice (by changing the activity type).
Thanks,
Anamata
NL
@RameshSangili If you believe that masking warnings is not the best practice, then why suggest wrapping it up? Yes, you will only get one warning. But the thought counts.
@CloeW938 Why not use saveble data pages to begin with and select the Database save in the Data save options section or use the Save Data Page smart shape if you're processing from a flow. Both options don't require an activity to begin with.
IT Solution Service
SG
Thanks for the reply. When I change the scope from My Current Application to All Applications, I was able to see the instance as below.
However, when I click the instance from "A" above, I get an error. Something is wrong.
On the other hand, when I click "B", I am somehow able to open the instance (I don't know why it behaves differently). This is strange.
Anyways, this rule is in Pega-DecisionManager ruleset. Are you sure you can call it from your application built on top of PRPC? At least I can't. Any thoughts?
Thanks for the reply. When I change the scope from My Current Application to All Applications, I was able to see the instance as below.
However, when I click the instance from "A" above, I get an error. Something is wrong.
On the other hand, when I click "B", I am somehow able to open the instance (I don't know why it behaves differently). This is strange.
Anyways, this rule is in Pega-DecisionManager ruleset. Are you sure you can call it from your application built on top of PRPC? At least I can't. Any thoughts?
Regards,