Release notes

In this section, you can find the release notes for Reporting.

Version 5.7.0 (04/17/2026)

New Features

Standard Assets permissions for System Administrators

System Administrators can now import, share, and delete Standard assets.

Password strength

Global settings now include a new set of settings that help define the user password strength.

Two new custom variables

We’ve added two new custom variables (_assetUuid and _datasourceUuid) to the variables list. The former is a globally unique identifier used to reference a specific asset in the system, while the latter is a globally unique identifier used to reference a specific data source in the system.

Right for Information report

Reporting Suite now has a new report called Right for Information that provides a complete overview of all available information related to a contact and all interactions associated with it.

Bug fixes

Asset title visualization issue due to top-right button overlapping.
Resolved redundant owner sharing option.
Fixed login error message for SSO.
Password reset not working for user in multiple tenants.
Prevented users from logging in via SSO if their username does not match the ERS internal user constraints.

Known Issues

The percentage text format always uses three decimal places.
Column sorting: When data is sorted by column, sometimes the user’s default filters and settings are restored.
First chart visualization: The first time a report is submitted, sometimes charts are shown empty.
Database cache not properly working. Always set USE_VIEWER_DB_CACHE and USE_DESIGNER_DB_CACHE to “false” to prevent unexpected reports behaviors. Database cache settings are now disabled by default.

Upgrade Notes

Upgrade is possible from any previous version of Reporting for Linux. Upgrading from Reporting versions older than that is not supported, as they require manual porting of custom reports.

Version 5.6.0 (01/23/2026)

New Features

Editable JWT shared secret

You can now edit the shared secret when using Single Sign On via JSON Web Token (JWT).

Validation

Validation is a new feature a Data Designer can set up that is used to define and validate the content a user introduces in the filters or settings.

Kubernetes installation

The official documentation now includes a new document detailing the installation and management of Reporting Suite in a Kubernetes environment.

New subscription setting

We have added the new subscription setting which allows the system manager to set the maximum number of subscriptions to be executed simultaneously.

Two new custom variables

We’ve added two new custom variables (_reportTarget and _reprotType) to the variables list. The former is used to specify the delivery format for an asset, while the latter indicates what type of element (DATASOURCE, REPORT, REPORT_VIEW, or DASHBOARD) is represented in the data model or assets

System – Schedules report

Reporting Suite now has a new system report called System – Schedules that delivers a clear, role‑based snapshot of all scheduling data within the environment.

Exporting dashboards in the email format

You can now export dashboards in email format. The dashboard contents are now delivered as an image.

Interactive filtering in dashboards

Certain elements, such as table and chart, support interactive filtering, enabling users to filter related data by selecting a value within the element itself. When those elements belong to the same group, a single selection propagates across the entire dashboard, keeping the displayed data synchronized.

Trusted user

A new feature now lets you label a user as a trusted user. This means their license requests will be approved automatically, meaning that the System Administrator won't need to act.

NodeJS 24

We’ve upgraded NodeJS version to 24 for all ERS NodeJS modules.

SecondsToTimespan

We’ve added the new SecondsToTimespan custom function to convert an integer to a timespan.

Third party libraries update

Dependencies and libraries used for various segments of the Reporting app have been updated to ensure better performances, provide vulnerability fixes, and to stay up-to-date with the newest technologies.

Bug fixes

Fixed dependent variables that did not work when depending on the date range variable.
Prevented users from logging in via SSO if their username does not match the ERS internal user constraints.

Known Issues

The percentage text format always uses three decimal places.
Column sorting: When data is sorted by column, sometimes the user’s default filters and settings are restored.
First chart visualization: The first time a report is submitted, sometimes charts are shown empty.
Database cache not properly working. Always set USE_VIEWER_DB_CACHE and USE_DESIGNER_DB_CACHE to “false” to prevent unexpected reports behaviors. Database cache settings are now disabled by default.

Upgrade Notes

Upgrade is possible from any previous version of Reporting for Linux. Upgrading from Reporting versions older than that is not supported, as they require manual porting of custom reports.

Version 5.5.0 (10/15/2025)

New Features

Database connections

When creating a new tenant, the UI now includes an expanded Database Connections section. The brand‑new feature lets you name the connection string, while the existing options, namely selecting the tenant’s database type and specifying the connection string used for standard reports, have simply been moved into this section.

Compressed attachments

You can now export scheduled reports and dashboards you are subscribed to as compressed attachments. The export works for PDF, Excel, and CSV formats, letting you receive the files in a smaller, zip‑packed bundle.

Undo/Redo button

The updated UI of the data model editor now includes new Undo and Redo buttons. These buttons let the Data Designer step backward or forward through modification history before saving.

Kubernetes deployment improvements

We’ve introduced extensive configuration options, making the Kubernetes deployment far more flexible and customizable.

Docker‑Compose repository change

The Bitnami image repository has been replaced with the Bitnami Legacy repository. Because of this licensing shift, older Bitnami images can no longer be pulled automatically. To continue using Docker‑Compose, you must upgrade to the latest version of our stack, which references the new Bitnami Legacy repository.

Existing deployments that already have the legacy Bitnami images installed will continue to work, but you cannot create new instances of those older images.

Bug fixes

First database initialization no longer fails in a new installation.
Fixed the SSO JWT roles support issue. You can now assign the proper user role (instead of just viewer) to an authenticated user.
Fixed tenant isolation issue when same username is used in multiple tenants.
Fixed the deleted style issue that caused an error to appear when a report view used a deleted style. Because of global styles, this error no longer exists.

Known Issues

The percentage text format always uses three decimal places.
Column sorting: When data is sorted by column, sometimes the user’s default filters and settings are restored.
First chart visualization: The first time a report is submitted, sometimes charts are shown empty.
Database cache not properly working. Always set USE_VIEWER_DB_CACHE and USE_DESIGNER_DB_CACHE to “false” to prevent unexpected reports behaviors. Database cache settings are now disabled by default.

Upgrade Notes

Upgrade is possible from any previous version of Reporting for Linux. Upgrading from Reporting versions older than that is not supported, as they require manual porting of custom reports.

Version 5.4.0 (07/10/2025)

New Features

Dashboard control buttons

Dashboards now have two control buttons. These are the Reset All Filters button and the Download button. The former removes all filters on a chosen dashboard, while the latter shows a dropdown menu where you can choose a format in which to download your chosen element.

Automated report and dashboard delivery improvements

Reporting Suite now has additional settings when exporting the reports in the Excel format as well as the option to export both your reports and dashboards in the CSV format. Additionally, you can now choose whether to export the whole dashboard or just a relevant widget in the Element section.

Tenant settings

An administrator can now choose when to warn a user about a license expiring and set up the starting day of the week.

Global settings

A system administrator can now specify the maximum failed attempts before lockout and also adjust the lockout duration.

Dashboard interaction buttons

Dashboards now have four new interaction buttons - edit, share, duplicate, delete.

Report hyperlinks open in the same tab

Previously, clicking a hyperlink to open a report would open it in a new tab. Now, reports open in the same tab.

Added support for EKS deployment

We now support the deployment of Kubernetes on Amazon Elastic Kubernetes Service (EKS).

Bug fixes

First database initialization no longer fails in a new installation.
Fixed the SSO JWT roles support issue. You can now assign the proper user role (instead of just viewer) to an authenticated user.
Fixed tenant isolation issue when same username is used in multiple tenants.
Fixed the deleted style issue that caused an error to appear when a report view used a deleted style. Because of global styles, this error no longer exists.

Known Issues

The percentage text format always uses three decimal places.
Column sorting: When data is sorted by column, sometimes the user’s default filters and settings are restored.
First chart visualization: The first time a report is submitted, sometimes charts are shown empty.
Database cache not properly working. Always set USE_VIEWER_DB_CACHE and USE_DESIGNER_DB_CACHE to “false” to prevent unexpected reports behaviors. Database cache settings are now disabled by default.

Upgrade Notes

Upgrade is possible from any previous version of Reporting for Linux. Upgrading from Reporting versions older than that is not supported, as they require manual porting of custom reports.

Version 5.3.0 (04/16/2025)

New Features

Kubernetes deployment improvements

Infrastructure and monitoring components were removed from the Reporting Suite deployment. Support for EKS has been added.

API enrichment and improvements

Reporting Suite now has better support for managing tenants and reviewing error handling through APIs.

New groups management API

The Reporting.API now provides group management.

Added support for HTML documentation deployment

It is now possible to deploy the documentation in HTML format with the product.

Popup message on license expiring

If your license is about to expire, a message notifying you about the exact date will now pop up when logging into Reporting Suite.

Online documentation search bar

Our online documentation now has a search bar. This makes it easier to find any topic that mentions the terms you're looking for.

Include/exclude users that are not supervisors in Supervisor Monitoring report

The Supervisor Monitoring report now includes the option of including or excluding non-supervisor users.

Bug fixes

First database initialization no longer fails in a new installation.
Fixed the SSO JWT roles support issue. You can now assign the proper user role (instead of just viewer) to an authenticated user.
Fixed tenant isolation issue when same username is used in multiple tenants.

Known Issues

The percentage text format always uses three decimal places.
Column sorting: When data is sorted by column, sometimes the user’s default filters and settings are restored.
First chart visualization: The first time a report is submitted, sometimes charts are shown empty.
Database cache not properly working. Always set USE_VIEWER_DB_CACHE and USE_DESIGNER_DB_CACHE to “false” to prevent unexpected reports behaviors. Database cache settings are now disabled by default.

Upgrade Notes

Upgrade is possible from any previous version of Reporting for Linux. Upgrading from Reporting versions older than that is not supported, as they require manual porting of custom reports.

Version 5.2.0 (01/28/2025)

New Features

Deleting a tenant

Currently, Enghouse Reporting Suite doesn’t allow you to delete a tenant completely but just disable it. When a tenant is disabled, tenant’s users are no longer able to access the web application. We have added information on how a System Manager can disable a tenant.

System reports

Previously, Reporting Suite offered using Standard reports. We have now introduced System reports. System Reports are typically tabular data reports that show you either a summary or detailed overviews of the relevant data. Usually, they can be adjusted to suit your needs using a variety of filters and settings, so that you can focus precisely on the data you need, while also having multiple options available. Only a System Administrator role has access to system reports.

System - Reports Check

Reporting Suite now includes its first system report, the System - Reports Check report. It was created to allow detecting inconsistent sharing of reports and their datamodels and missing parent assets.

Multi-tenant licensing model

Multi-tenant licensing model allows the license to be applied on a system-wide level and manages licenses allocation per tenant on a system administration level.

Each license now has an expiration date, meaning that licenses now expire.

Previously, the licenses had a limited combined number of users for the Designer and Data Designer user roles and an unlimited number of users for other roles. Now, the licenses limit the number of users for each role. When allocating licenses in multi-tenant mode, a system administrator can now see how many licenses have been allocated and how many they can still allocate.

Callback Summary report

A new Callback Summary report has been added to help contact center supervisors access data about the callback requests that occurred in each time, and to optimize the interaction handling by reviewing the time the agents respond to and spend on each callback request. Find out more information about their individual purposes and use in the standard reports documentation.

Improved API documentation

There are new sets of APIs (user management APIs, license management APIs, and report elements APIs) that provide a description, parameters, and examples of APIs for users who integrate with Reporting Suite. User management APIs allow products that integrate with Reporting Suite to create, update, and delete users. License management APIs make it possible for the integration to allow completely managing the license, while report element APIs allow for assets to be shared with users automatically.

Changed features

Updated the “Creating a new tenant” procedure

There is now a Dashboarding enabled option that makes it possible to select the checkbox to enable Dashboarding.

When creating a tenant administrator, you must now also fill out the Confirm password field.

License settings

License settings now include a new table detailing the status of the license, its expiration date, and whether the license is valid or not. You can also now see the number of users and licenses per each role.

New features when uploading a license

When uploading a new license, you can now click the “Choose file” option. Before uploading, a pop-up now appears, detailing the information about the license.

Bug fixes

First database initialization no longer fails in a new installation.

Known Issues

The percentage text format always uses three decimal places.
Column sorting: When data is sorted by column, sometimes the user’s default filters and settings are restored.
First chart visualization: The first time a report is submitted, sometimes charts are shown empty.
Database cache not properly working. Set always USE_VIEWER_DB_CACHE to “false” to prevent unexpected reports behaviors.

Version 5.1.0 (10/15/2024)

New Features

Uploading (fonts as) resources for report designers

Previously, if you used a font that was available on your computer rather than the server, you would see the report correctly, but other users who did not have the font installed could not see it. Now you can add a new resource by dragging and dropping a .ttf font file. This makes the font available to all users.

Adding and editing transformations in reports

The data transformation editor was previously available only to the Data Designer in the data model, while it is now available in the report model as well. The Report Designer can see the data aggregation created by the Data Designer in the data model they are using. However, they cannot edit or delete it. The Report Designer can, however, create a new data transformation to use certain aggregations that may be useful in the table view of a report.

Administrator users can configure Look and Feel

Administrators and System Administrators can choose which style and theme will be used for all the assets (such as report views) in a tenant.

Changed Features

Added Enghouse logo to login page

The Enghouse Interactive logo was added to the Reporting Suite login page.

Values filtered in view are sorted in the same order as in the original report

Previously, the values displayed in a View were sorted in the order in which they were selected by the designer of the view. This has been changed, and the values are now displayed in the same order as in the original report (without the unselected values).

Full compatibility with EIS specifications

Some changes have been made in the integration with EIS in order to apply the latest technical choices defined in the newest version of EIS.

Added warning message with unsaved View changes when trying to leave Editor

A warning message will now pop up if you try to leave the View editor without having saved the changes that you wished to apply.

Increased style name field width in style designer

On the Styles tab, the style Name field has been fitted to the size of the screen to make longer style names easier to read.

Review API documentation with Swagger

If a developer needs a list of APIs to integrate with Reporting Suite, they can use the Swagger page, which has been updated to include additional useful details for some of the APIs.

Standard reports changes

The following changes have been applied to existing standard reports:

• In the Outbound Campaigns report, new columns and filters have been added.

Bug fixes

Fixed issue created by allowing System Administrators to rename the System tenant. This is no longer allowed.
Fixed tenant licensing issue with users that use the same email address in various tenants.
Fixed the issue created by allowing the creation of multiple tenants with the same name. This is no longer allowed.
Removed the Report Snapshot option from the Download options in the Reports view.
Fixed issue that allowed Viewers to see reports shared in the Can create view.
Fixed issue that displayed the hidden filters after selecting the Restore default filters button.
Fixed the paper orientation bug so that the portrait orientation is shown if you select portrait.

Known Issues

The percentage text format always uses three decimal places.
Column sorting: When data is sorted by column, sometimes the user’s default filters and settings are restored.
First chart visualization: The first time a report is submitted, sometimes charts are shown empty.
First database initialization can fail in a new installation; it may be required to restart the application to properly initialize the application database.
On first tenant initialization, after configuring a new tenant, you sometimes need to restart the application for it to work properly.
Database cache not properly working. Set always USE_VIEWER_DB_CACHE to “false” to prevent unexpected reports behaviors.

Upgrade Notes

Upgrade is possible from any previous version of Reporting for Linux. Upgrading from Reporting versions older than that is not supported, as they require manual porting of custom reports.

Version 4.6.0 (05/29/2024)

New Features

Bulk actions in Data and Reports tabs

New bulk actions have been added to the Data and Reports tab where users with the appropriate access level can now switch to a list view of the assets and then perform bulk actions (delete, export, share, unshare).

Third party libraries update

New built-in function: TimestampDiffForDb

A new built-in function has been added to the Dictionary in Reporting which enables users to convert timestamps for different database types.

New logging centralization with Fluentd

Centralized application logging has been achieved through using Fluentd, and now there are no duplicate timestamps in messages that already include the timestamp. This is applicable to installations on Kubernetes environments only.

Changed Features

Sharing permissions

When sharing assets in Reporting, the sharing options have now been modified so that they include the following options when sharing reports:

Can read: Users can read (and interact with) an asset the same way Viewer users can. Additionally, if they have the appropriate user role, they can also duplicate the asset, or, for example, create a report view based on a report shared with this permission level.
Can create view: Users (primarily Power Viewers) can use the shared report as a base report for their report views, but they cannot see the report in their Reports tab, and they cannot interact with the report in any other way.

Furthermore, if a Power Viewer copies a report view and tries to edit it, but does not have the relevant access level for the base report of the copied view, an error message is now shown to indicate that they do not have the needed access level for the base report.

Check for duplicate names when creating assets

Previously, a check for duplicate names was performed only during the data model creation procedure. Now this check is performed when creating all assets, including reports, report views and styles.

Field name visualization using display names when creating view

During the report view creating procedure, report column (field) names are now displayed using the name of the field as shown in the report, and not as shown in the database, as was previously the case. If a translation is available, the field is shown in the selected user language.

Standard reports changes

The following changes have been applied to existing standard reports:

Standard reports now include Call Survey Data.
The Survey Metric column and filter have been added to the Survey Answer Detail report.
The Survey Description filter has been added to all survey standard reports and CCaaS views.
The Survey Question index has been added as a data grouping level to the Survey Summary standard report, while the Survey Metric filter has been changed to multi-select in the same report.
The Survey Summary report now contains more columns related to survey answers.
In the Queue Performance standard report, columns have been added to count handled and rejected interactions.
In the Agent Interactions report, the “Show rows with 0 handled interactions” setting has been added.
The HH:MM:SS format is now set as the default duration display format (in the settings) for all standard reports.

Data model creation steps

The data model creation steps have been slightly modified so that they are the same as the report creation steps.

Change in UI for improved viewing

Changes have been applied to the report viewer UI to ensure an improved viewing experience of reports and report views.

OIDC config role mapping

The EnghouseBILite_ prefix in OIDC config role mapping has been replaced with the ERS_ prefix. The previous prefix can still be used, but will be deprecated in upcoming versions of Reporting.

Bug fixes

Fixed button overlap issue with dropdown list that occurred in some cases, e.g., when creating a report view.
Fixed formatted date in all standard reports.
Fixed issue with the end timestamp for “Callback Response” in the “CCaaS - Queue Interaction Detail” report.
Fixed error related to permissions with report view continually refreshing after changing the base report.
Fixed issue with changing the application language not working in the report editor.
When configuring a tenant, it is no longer necessary to specify both the FQDN and the https:// prefix of the host, just the FQDN is now needed.

Known Issues

The percentage text format always uses three decimal places.
Column sorting: When data is sorted by column, sometimes the user’s default filters and settings are restored.
First chart visualization: The first time a report is submitted, sometimes charts are shown empty.
First database initialization can fail in a new installation; it may be required to restart the application to properly initialize the application database.
On first tenant initialization, after configuring a new tenant, you sometimes need to restart the application for it to work properly.
Database cache not properly working. Set always USE_VIEWER_DB_CACHE to “false” to prevent unexpected reports behaviors.

Upgrade Notes

Upgrade is possible from any previous version of Reporting for Linux. Upgrading from Reporting versions older than that is not supported, as they require manual porting of custom reports.

Version 4.5.0 (02/15/2024)

New Features

Kubernetes Deployment Support

Kubernetes support has been introduced in this version, which has also resulted in high availability and scalability improvements. The Docker-compose deployment will be deprecated in the upcoming versions (End-of-Life date TBD).

Added reports and views features

Now when attempting to delete a report that has dependencies, such as views, you are given a warning that the dependencies need a new base report, which you can either choose then or select later. Additionally, when working with a report view, if you have the appropriate access level, you can change the used base report from within the view UI.

Added Email Server settings to UI

Administrators can now manage the email server settings, which was previously not available in the Admin tab.

Redirection on missing or unauthorized page

Users are now redirected to their home page if they attempt to open a page that is missing or that they do not have the appropriate access level to.

SSO standard role definition and more robust features

ERS Admins can now redefine the default role of users added to the system via SSO. Furthermore, the SSO integration is now more robust in terms of unexpected errors, such as timing out or similar.

Filter dependency support

This version includes the option to work with filter dependencies in reports and report views. Dependent filters are filters the options of which change based on what is selected in another filter (for example, if a country is chosen, then in another filter only the cities from that country are available as options).

Added visual improvements to filter tab

Visual improvements have been added to the Filters & Settings pane, so that now it is easier to understand which and how many values have been selected for the individual filters.

Added multi-metric support to Survey reports

The new version allows users to define multiple metrics used to evaluate the overall survey score within the report.

Changed Features

Changes to assets in the left pane

Assets such as reports are now sorted alphabetically by default in the left-hand pane of BI Reporting. Additionally, corporate (standard) reports are shown by default in the left pane.

Filter validation check added to subscription

When creating a new subscription to a report, a filter validation check is run to ensure all the relevant filters are entered as necessary.

Multiple submit prevention

Mechanisms have been added to prevent multiple concurrent submits in assets to ensure a proper functioning of the system and less load.

Bug fixes

Fixed a number of errors and unwanted behavior in standard reports.
Performances optimized to prevent report loading failures due to high volumes of user data being loaded at the same time.
Fixed an issue with Firefox compatibility.
Fixed session expired message not displaying.
Fixed bookmark, now loading properly.
Fix labels not correctly applying latest translations on the report view filters to now applying the proper translations.

Known Issues

The percentage text format always uses three decimal places
Column sorting: When data are sorted by column, sometimes the user’s default filters and settings are restored
First chart visualization: The first time a report is submitted, sometimes charts are shown empty
First database initialization can fail in a new installation; it may be required to restart the application to properly initialize the application database
After configuring a new tenant, you sometimes need to restart the application in order for it to work properly
Rows are not automatically expanded on longer strings, resulting in semi-visible data in report rows
Database cache not properly working. Set always USE_VIEWER_DB_CACHE to “false” to prevent unexpected reports behaviors

Upgrade Notes

Upgrade is possible from any previous version of Reporting for Linux. Upgrading from Reporting versions older than that is not supported, as they require manual porting of custom reports.

Version 4.4.3 (10/02/2023)

Bug fixes

Fixed time zone issue for UTC-x time zones when selecting the date from the calendar. Before the fix, the calendar worked for UTC+x time zones, but for UTC-x time zones, the date applied to the report was a date before the one selected by the user. Now the correct time zone and date are applied.

Known Issues

The percentage text format always uses three decimal places
Column sorting: When data are sorted by column, sometimes the user’s default filters and settings are restored
First chart visualization: The first time a report is submitted, sometimes charts are shown empty
First database initialization can fail in a new installation; it may be required to restart the application to properly initialize the application database
After configuring a new tenant, you sometimes need to restart the application in order for it to work properly

Upgrade Notes

Upgrade is possible from any previous version of BI Reporting for Linux. Upgrading from previous BI Reporting versions is not supported, as they require a manual porting of custom reports.

Version 4.4.0 (08/10/2023)

New Features

Standard reports

The following standard reports have been added:

Concurrent Agents
Survey Answer Summary
Survey Detail

Find out more information about their individual purposes and use in the standard reports documentation.

Changed Features

Agent Availability Standard Report

Changes have been made to the report fields and the expressions used for them. Find out more in the related standard report documentation.

Added Dashboarding enabled elements to System Administrator UI

For System Administrator Users, in the Tenants section of the Admin tab, UI elements have been added that show whether a tenant has the Dashboarding feature enabled:

A column in the Tenants table titled Dashboarding enabled, indicating if the feature is enabled or not, and
a checkbox in the Tenant details window, when editing a tenant, where the System Administrator can choose to enable or disable the feature for the specified tenant.

Removed future dates from relative time frame filter selection

In Standard Reports, the option to use future dates in the relative time frame filter has been removed. Future dates can still be applied as filters by using the to and from Date Interval filter, i.e., the calendar date selection.

Bug fixes

Fixed dividing by zero issue in the Agent Availability standard report

Known Issues

The percentage text format always uses three decimal places
Column sorting: When data are sorted by column, sometimes the user’s default filters and settings are restored
First chart visualization: The first time a report is submitted, sometimes charts are shown empty
First database initialization can fail in a new installation; it may be required to restart the application to properly initialize the application database
After configuring a new tenant, you sometimes need to restart the application in order for it to work properly

Upgrade Notes

Upgrade is possible from any previous version of BI Reporting for Linux. Upgrading from previous BI Reporting versions is not supported, as they require a manual porting of custom reports.

New Documentation

Created new standard report documentation
Created new documentation for the standard reports listed in the first section of these Release Notes.
Updated existing user guides and Management Guide
Clarified the described new features in the appropriate documentation.

BI Reporting Version 4.3.0 (02/01/2023)

New Features

Standard reports

The following standard reports have been added:

Outbound Campaigns
Supervisor Monitoring

Find out more information about their individual purposes and use in the standard reports documentation.

Changed Features

Removed download button from Reports tab

The download button that forwards users to the report viewer has been removed from the following locations:

Reports tab tiles
Reports side pane

Modified available System Administrator related actions

System Administrator users, i.e. their information, such as default email or password, can no longer be modified by other (Administrator) users in the Users section of the Admin tab. System Administrators can still perform the standard actions users can do for their own account, such as change their password or UI language.

Bug fixes

Element export did not work properly if the element (report, data model, view…) was shared with a user via group. With this fix, users can now export elements when they are shared with them through groups.
Fixed the evaluation of “% Status Time of Break” in the Agent Availability standard report.
Some charts were not working as intended. With this fix, charts can now be properly visualized. Note that due to this, when upgrading from Version 4.2, you may need to run the import CLI tool with the forceReimport option enabled.
When installing BI Reporting from scratch, all users of the “System” tenant were not included in the “Everyone” group. With this fix, this is now done automatically.

Known Issues

The percentage text format always uses three decimal places
Column sorting: When data are sorted by column, sometimes the user’s default filters and settings are restored
First chart visualization: The first time a report is submitted, sometimes charts are shown empty
First database initialization can fail in a new installation; it may be required to restart the application to properly initialize the application database
After configuring a new tenant, you sometimes need to restart the application in order for it to work properly

Upgrade Notes

Upgrade is possible from any previous version of BI Reporting for Linux. Upgrading from previous BI Reporting versions is not supported, as they require a manual porting of custom reports.

New Documentation

Created new standard report documentation
Created new documentation for the standard reports listed in the first section of these Release Notes.
Updated existing user guides and Management Guide
Clarified the described new features in the appropriate documentation.

BI Reporting Version 4.2.0 (01/13/2023)

New Features

Power Viewer user role

New role has been added to BI Reporting. Power Viewers are Viewers with extended access rights to work with report views. They can create report views based on reports shared with them, import and export the views, and share them with other users. They cannot create, edit, own or share full reports.

Styles

The Styles tab has been added and is available to both Designer user roles and Power Viewers. In this tab, users can work with the style designer tool to create new style sets and collections, which can be applied to reports and report views, exported and imported.

Time zone support

The Time zone report setting is now available in standard (and other) reports. This feature allows report users to choose which time zone the data, filters and other elements are used and shown in. In order to do so, the database data that is imported into the standard data warehouse needs to be prepared in a specific manner.

Show empty columns

The Show empty columns setting has been added to reports. This feature is used to choose whether or not you want to show rows with no data in your report.

Standard components import and update tool

A new tool has been added which allows you to import and export standard data models, reports and views for all tenants. This is a new command line tool which facilitates the process, as opposed to performing the same actions manually through APIs.

Standard reports

The following standard reports have been added:

Self-service Checkpoint Detail

Find out more information about their individual purposes and use in the standard reports documentation.

Changed Features

Importing and exporting reports and report views

The report export and import feature has been improved with the following additions:

Exporting and importing views
Functionalities to facilitate use, such as selecting only views or only reports

Report view editor

The report view editor has been enhanced with the option to choose a style to be used with the report view.

Changed Admin SSO settings interface

For Administrator and System Administrator users, the JTW Validation Key setting is no longer required for Single Sign On via OpenID Connect.

Features currently disabled

The following features are disabled in this version of BI Reporting, but should be available in the upcoming releases:

Connections manager
Custom functions
Designer debugging
Mail server configuration UI
“Shared network file server” support for report scheduling

Bug Fixes

Tenant host has to be specified, both when providing just the host and providing protocol and host, to work properly. This fix now allows the user to specify just the real tenant host.
Trying to login to an unknown tenant host returns a generic “wrong username or password” error. The fix now returns a proper message that explains that the provided host is unknown.
Slow reports don’t work due to internal short timeouts. The fix now increases report timeout from 10 minutes to 1 hour.
Changing the database type for a tenant doesn’t properly apply the change to standard the data models. The fix now properly updates all the standard data models.
Once a filter is marker as “background filter”, it is no longer possible to remove the flag. The fix now allows the view editor to clear the “background filter” selection.
When BI Reporting is installed, the license is not properly checked. The fix now enables the tenant licensing check.
Pulling the images upgrades pgpool to version 4.4, which is not compatible with the existing version of the database. The fix now blocks pgpool version to 4.3.3 Security enhancement.
It is allowed to access the master and slave instances of PostgreSQL directly from external clients. The fix now disables direct access from external clients to PostgreSQL instances, which can now be accessed just through the db.service container.
PostgreSQL database doesn’t require password. The fix now disables unauthenticated access.
OIDC SSO configuration requires to specify the JWT key. The fix now removes this parameter, as it is automatically provided by the identity provider.
Reports requiring many parameters with many values result in a HTTP 414 error and no result is returned to the user. The fix now resolve the “414 URI Too Long” error, sending parameters in the request body.

Known Issues

Column sorting: When data are sorted by column, sometimes the user’s default filters and settings are restored
First chart visualization: The first time a report is submitted, sometimes charts are shown empty
First database initialization can fail in a new installation; it may be required to restart the application to properly initialize the application database
After configuring a new tenant, you sometimes need to restart the application in order for it to work properly
When installing BI Reporting from scratch, the “System” tenant doesn’t include the “Everyone” group. It has to be manually created and existing users have to be manually added directly in the application DB
Some charts are not working as intended.

Upgrade Notes

Upgrade is possible from any previous version of BI Reporting for Linux. Upgrading from previous BI Reporting versions is not supported, as they require a manual porting of custom reports.

New Documentation

Created Power Viewer user guide
Created a new user guide for the Power Viewer role, explaining all the role’s capabilities and features.
Created new standard report documentation
Created new documentation for the standard reports listed in the first section of these Release Notes.
Updated existing user guides and Management Guide
Clarified the described new features in the appropriate documentation.

Note

For older release notes, see the Release notes PDF.