Need some insights before we recommend the Reports to our biz customer
We are using PRPC V722 in our current application. Our application is running on desktop and mobile versions. Of course, we have BIX reporting feature in it. Our BIX process is running on a different DB and is a separate instance altogether. We have archive DB for retrieving the old data from another DB instance. Currently, the biz is heavily using the BIX reports for their monitoring of data perspective though our biz is enough matured on Pega features since long time. Now we are planning to show case the Pega reporting feature to biz and for that we are using our functional DB from one of our non PRD environments. Before we go to biz, we would like to know the pros & cons of recommending the Reports feature from the application against current BIX reports in the current sys. The main area what we are looking is the performance impact while accessing the DB data (of course we have huge data in our functional DB) in terms of I/O access after we start using Reports feature from the application.
I would like more insights from the Pega experts to chime in our recommendation on Reports usage in our application. By the way, we don't have any Reports section so far or any reports created/used in our application since we started working on this application. But we have a RDE created to capture the daily data based on our biz logic and is being sent out from an agent in a nightly job fashion. I am familiar with Reports functionalities and the advantages of reports in the application based on my past experience. But I would like some advises from the experts to proceed further in this context. If any nice articles to recommend Reports feature from the product then that would be a great help for me.
The rule of thumb is that the reporting capabilities in the Pega platform are for generating interactive reports. These reports should be "reasonable" in size. What that means is they should be friendly to the end user.
For instance, having so many columns that the user has to do excessive horizontal scrolling is not user friendly. Having a report that returns thousands or tens of thousands of rows is also not user friendly. Even if paging is enabled, with a reasonable page size that doesn't require much or any vertical scrolling, the number of pages will be excessive.
Then there are the negative performance aspects of very large interactive reports. Even getting a total result count for a report with a large number of rows can be problematic (necessary for presenting the paging interface). In database terms it requires a full table scan, which for large tables will be slow.
Basically, if the report is too large to be used effectively as an interactive report, you are better off generating the report in BIX. This includes reports that are generated in Pega just to be exported into Excel and used there.