Some times, i observed that we need to pass certain default values to filter condition and needs to fetch those default values based on certain business logic.
Display User inactive bank account details for selected time period. Start date should be defaulted to 30 days prior to current date and End date should be defaulted to today.
As we don't have any Pre actions, to set up this date information or set default values based on biz logic, in Report Definition rule level, will be relaying on data page to achieve this.
It would be great if we have have pre data transforms for report definition to mitigate these issues.
***Edited by Moderator Marissa to change Content Type from Idea to Discussion due to Idea content type being deprecated; added Idea specialized tag***
***Edited by Moderator Marissa to change Pega Academy to Product***
@MS91781 I suppose that if you're looking for preprocessing instead of postprocessing, using subreports can be helpful with the correct where clause and maybe some functions to add spice. SQL first executes inner queries and then outer, so if you can filter the most rows in the subquery, that will improve your performance. Most of the time, however, I find that a postprocessing DT does an okay job by iterating on Primary.pxResults() and then do business logic.
I think the main reason why preprocessing is not available, is because the result set is not known yet before the query has run :)