Guardrail Warnins in Report Definition and Activity
I have below two questions related to guardrail warnings.
1. If I have to call an activity (in let's say post-processing of a flow action), should I create another activity and call it but it will generate a severe warning or should I call it from Data Transform using pxExecuteAnActivity function and avoid that warning. Is using the function pxExecuteAnActivity frequently to avoid creation of Activities recommended?
2. I have a parametrized Data Page sourced from a report definition which has filters. If no filter is being passed I need to get all the values. However for that I need to uncheck "use null if empty" but that will again add a moderate warning. So I should let it be or create additional report definition and use it as a second source with condition to trigger only if params are empty. There will be no filter in the report definition so no warnnig, however I will have to create an additional rule.
***Edited by Moderator Marissa to update Platform Capability tags****
Updated: 14 Jun 2021 7:38 EDT
Pegasystems Inc.
IN
For 1, whichever activity you are calling from Data Transform, you can call the same activity in the Post-processing of flow action right, anyways the activity which you want to call is already created.
Updated: 21 Apr 2020 1:06 EDT
Northbridge
CA
Hi Piyush,
Guardrails are unavoidable in some cases. Try justifying them whenever possible.
You can definitely use 'pxExecuteAnActivity' in a DT instead of creating a new activity if it's purpose is just to call another activity.
For second question, I think you have a wrong understanding of what "Use null if empty" option means. The filter will be ignored and not the results.
About "Use null if empty" option from Help doc
This option is important only when there is no value at run time specified in the Value field. By default, when the Value field is empty at run time, the criteria defined by this row is ignored, and processing is the same as if this row is not present.
-Shruthi
Capgemini
NO
Thank you for your reply for the fist question.
But for second one I don't observe this behaviour. Just rechecked. Had checked "Use Null if Empty" for all the filters but didn't receive a single result. See below. According to this system should display all those records where HideValue="No" which is plenty in my case.
