Question
Pegasystems Inc.
HK
Last activity: 19 Apr 2016 2:58 EDT
How to conditionally add a condition in a defined report definition
I have a requirement on case related search and a report definition has been created to achieve this.
Sometimes, based on the user input, there will be additional conditions addend to extend the search , but in current report definition ,you have to have these criteria predefined.
In ListView, this is can be done in getContent activity, but how can we do the same in report definition by adding new criteria entry in where clause so the posted SQL can be altered.
Thanks very much for anyone who answered this.
Cheers,
Accepted Solution
Pegasystems Inc.
IN
Hi Frank, Good morning!
- we need to build the filter criteria dynamically on a user defined filter page in a wrapper activity...
- and leverage the parameter 'pyReportParamPageName' to refer this page...
- in RULE-OBJ-ACTIVITY RULE-OBJ-REPORT-DEFINITION PXRETRIEVEREPORTDATA
- and leverage the parameter 'pyReportParamPageName' to refer this page...
- adv: One Search RD will serve the purpose for all possible search criteria.
- dis-adv: Need to understand internals of how to property-set the filter criteria dynamically like
- .pyFilterSettings.pyFilter(1).pyFilterName=
- .pyFilterSettings.pyFilter(1).pyFilterOperation=
- .pyFilterSettings.pyFilter(1).pyTextFilterValue(1)=
- which changes based on datatype of filter value
- example for DATE: .pyFilterSettings.pyFilter(1). pyDateTimeFilterValue(1)=
- which changes based on datatype of filter value
- instead - would it be convincing to create another report definition ...
- and call appropriate RD via ONE data page based on WHEN conditions of search inputs? to retrieve search results?
- adv: readability or debugging the code for a new/peer engineer might be easy
- dis-adv: multiple RD's will be created for the same search functionality because of possible search parameters...
Please share your thoughts/comments, Thank you!
psahukaru
Pegasystems
IN
You should go with the pxRetrieveReportData activity. Please see the following help document for details - https://community.pega.com/sites/default/files/help_v72/procomhelpmain.htm
Pegasystems Inc.
HK
Hello Phani,
Thanks for your reply. Creation of a new RD will be the most straightforward one. Well the first approach that you mentioned, seems we need to handle a lot of meta data in the report defintion rule. I will take a look at this approach and see if it's easy to implement and to maintain.
Thanks,
Process 360
IN
Hi Frank,
I have observed that pega will ignore the filter criteria if the param value is null . So can't we build a RD with exhaustive search criteria using param as filter values and only pass the params which will be used as a filter criteria and the remaining filter criteria where the param value is null will be ignored in the generated sql.
Pegasystems
IN
Hi Bhanu,
Wouldn't that be confusing to the report developer to add a fairly large set of filter conditions on the report and carefully manipulate the parameter page entries to ensure only the required part of the report fires? This also means testing this report for the various combinations (code paths) will be tricky and possibly lead to missing scenarios.
-Rajiv