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.
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.
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.