This is the first part in a three-part series that will cover how the coreBOS reporting system works and where the limits are. You can read the second and third part if you are coming from the future :-)

Functionality on screen: buttons icons and quick actions

One of the first enhancements we made to the reporting system was to add quick action icons on the reports. At that time, the issue was that to be able to export the report you had to go IN to the report which would send the full contents to the browser. This massive amount of information would many times hang the browser so you couldn't get the information in any way.

With the quick action icons at least you could get the information out of the system.

Reporting quick actions

Today we have solved this problem with paged reports but the quick action buttons are still very useful.

Global variables that affect how reports act

Report_ListView_PageSize

This integer value defines how many rows of a report we will see in each page. The default value is 40 records

Report_MaxRows_OnScreen

When exporting a report to the browser in HTML it is easy to collapse the browser if too much information is sent, so we limit the maximum number of rows in HTML exports with this variable.

Report_MaxRelated_Modules

In the second step of the creation or customization of a report, we are given the option to select additional modules that are related to the main module of the report. When we relate many modules it is possible to create an invalid SQL command, so we limit the number of possible relations with this variable.

Report_Send_Scheduled_ifEmpty

By default scheduled reports are always sent even if they are empty. We can change this behavior with this variable

Report_HeaderOnXLS and Report_HeaderOnPDF

These variables will add the name of the Report to the output. This will complicate the spreadsheet automated processing but looks totally correct on the PDF.

Report Headers

Sharing

The information that appears in a report will always be restricted by the privileges of the user launching the report, but we can also define who can access the report itself in the penultimate step of the report customization.

We will be able to share the report with other users, groups or roles.

Programming regular send by email

We can program any report to be generated and sent by email at regular intervals to different application users.

The report can be sent in PDF, Excel or as a direct URL to the application

For this feature to work correctly we must have the scheduled report programmed task active and the coreBOS cron system correctly configured

Continue reading the next part here

Photo by Stephen Dawson on Unsplash unsplash-logoStephen Dawson

Next Post Previous Post