Moving with the trend has always been considered progressive when it offers added functionality and usability benefits. Using ActiveReports encourages you to be progressive, offering different solutions to design reports, so you can choose the best option for your business requirements.
This blog will help you understand why migrating from Section reports to Page/RDL reports is a progressive step and when it is necessary.
The need for migration from Section to Page/RDL reports
Benefits from converting
How to convert your reports
Let’s say you are working as a Technical Analyst in a Call Center that handles customer service requests for different banks. At the end of every financial year, you need to prepare an Employee Performance Report depicting the overall performance of the employees based on the number of calls received and resolved. The management uses this report to assess the revenue generated by each employee.
In the past, you have designed these reports using Section reports:
This time, management is interested in knowing the annual work summary for all the banking clients from a single report. Management also wants improved analyzation of their employees' performance.
Management is requesting to:
To incorporate these changes, you could revise your existing report as follows:
Revising the report as described above, you would be required to manage two reports along with their links, and write extra code. This could be time consuming.
A different approach is to create a Page or RDL report that can easily meet all the requirements. To do this, you'll need to recreate the layout of existing Section report in the Page/RDL report, (either manually or by using ActiveReports Import tool).
After that, you can:
Use Iconsets data visualizer to highlight the employee details per their speed and performance.
A report using Page report might look like this:
This explains one report conversion scenario. Other requirements could be:
Let’s take a look at some of the benefits you get when converting your Section reports to Page or RDL reports. You can read more about the details and differences between the three report types.
The common report features like data aggregation, binding reports to JSON and Oracle data sources, Master reports, etc. are much easier to accomplish in Page/RDL reports, as compared to Section reports.
Let's take an instance from the original Call Center report where you want to display the total calls answered and take a count of employees at the end of the report.
If you were working with a Section report, you would need to set the following properties of TextBox controls:
While in Page/RDL report, this can be done simply by specifying the aggregate expressions in the 'Value' property of TextBox controls.
In addition, you'll find some of the features easily accessible in Page/RDL reports.
Using controls in Section and Page/RDL reports could be a different experience from the point of features they support.
Functional examples in Page/RDL report controls include:
Read more details about the Page/RDL report controls
Consider that you are working on a web-based application which provides its licensed users the flexibility to create or modify reports at run-time. In such a scenario, you can use the HTML5 Designer (will be available in AR13) to create/edit your Page or RDL reports. While the same will not be possible with Section reports.
In addition to the above benefits, you can use all Page/RDL report features in your converted reports as usual including:
Note: You can explore more about Page/RDL report features from ActiveReports 12 documentation.
During conversion, it's important to keep in mind that the converted Page or RDL report won’t support the following Section report controls/features:
It's recommended that you understand and prioritize your business needs before choosing to convert reports. Once you have made this decision, the next question comes is, how do you actually do the conversion.
There are two methods to convert your existing Section reports to Page or RDL report.
Using ActiveReports Import Wizard
This is an easy and quick way to convert your existing Section report layout to the corresponding RDL report.
By doing this, the layout of the Section report will be converted to the corresponding RDL reports, with the following resources:
Note: Conversion to RDL reports was added in ActiveReports 12, and conversion to Page report will be added in ActiveReports 13.
For more details, see Importing RPX topic in documentation.
The second method is to redesign the Section report layout manually in Page or RDL report, by adding and aligning controls, connecting report to the data source, adding related resources like parameters, and calculated fields.
In our next blog, we'll look at some guidelines to help you through the conversion process.
CallCenterReport.rdlx | CallCenterReport.rpx
CallCenterData.xml | ClientsData.xml