We want to create a report with multiple tables. So, i am thinking of using a section with multiple grids sourced from various data pages. But in this case, i will have to schedule the reports using an agent activity and also take care of sending emails, pdf and excel conversions, etc. I like the OOTB feature of scheduling the reports using report viewer with notifications and pdf/excel conversion built-in. So, my question is can i use either one report definition to create multiple grids/tables or many different ones combined together into a single RD that i can export to report viewer? Or may be, a single report definition with header table, a footer table and a chart? Or is creating this in a UI section is my best option?
Could you describe some of the requirements around the reporting and outline the requirements around the scheduling?
If you want to create a view with multiple reports, that sounds like a widget or a series of widgets you can just place in a dashboard when the user logs in.
Regarding the scheduling of the sending, why do you need to do this? Are these external users that you want to send report data to?
Finally, if they are just looking for weekly metrics, you could create a correspondence rule that leverages all of the different data pages you make, and come up with a meaningful display of the metric data for them, and then send that corr on a frequency.
I think I could advise better if I had a little more info.
I need to create 1 report (without any drill downs) that I can convert to PDF and email it out. This report needs to be a combination of multiple summary reports and list reports. Is it possible to do something like this with Pega?