Izenda continues to add features to our 7 Series embedded BI and analytics platform to extend its value for software companies and its use for their customers.
Some of our most recent updates improved the usability of subreports, added custom time period values for filters and add more complex joins.
Subreports Inherit Filters and Values
With our v1.24.0 release, Izenda added the ability for subreports to inherit filters and their values from parent reports. So users can pass filters to the subreport as long as those filters come from the same data sources.
- The data sources for the parent/subreport must be exactly the same
- The inherit filter checkbox must be checked when setting up subreports
- These filters will not have to be present on the subreport ahead of time
Create Custom In Time Period Values
Another new feature adds the ability to create custom in time period values for filters. Now you can add any time period relevant to the business use cases to quickly filter data based on a predefined value range.
Create these custom time period filters for various datatypes by overriding the LoadCustomTimePeriod in your DefaultAdHocExtension implementation.
Custom Formats for Field Properties
Perhaps your customers need special currency symbols not typically available. Or you need additional financial symbols that don’t come pre-installed. Recognizing this need, Izenda’s team extended the ability for customers to add custom formats for field properties.
Now you’ll be able to add those currency symbols, the “tilde” (~) symbol or other symbols. And numeric formats can be set to your needs.
Add Logos by Tenant in Reports
While you want your application to display your company’s brand, your customers want to see their own brand identified on their reports. One of our recent updates added a setting at the tenant level to add logos by the tenant for the header image.
For each tenant, you can add in settings a relative path or URL for a default header image. This automatically adds the tenant (customer’s) logo, but they can still change it. The logo only shows up if the customer adds the header, but when it’s added the logo appears automatically.
Your team sets this at each tenant level, with one default for each tenant. You’ll find this setting located in System Configuration > Report.
More Complex Joining Capabilities
Izenda added new conditions to joins in our embedded BI and analytics platform. Previous versions of our analytics solution had more limitations, offering standard left, right and inner joins.
With the addition of these new join conditions, users can create more complex joins with logic to include items which are null/not null, equal to, greater than/less than a value or another field. This reduces the reliance on creating views for these more intricate joins.
Remembering that filters are always added to the where clause of a query, which reduces overall results. Join conditions can either increase or decrease the result sets depending on the required data.
Any user whose role allows access to joins in the report designer can make use of this added functionality.
Currently, this feature is only supported for single database queries. A future update will add this feature for cross database joins with an additional option for an in comparison.
Simplified Property Panel for Non-Power Users
Not every analytics user wants or needs to see every possible option when designing reports or editing them. All of the added options clutter up the screen when they aren’t needed, and could confuse the user. To this end, property panels of the report designer and the quick edit mode show fewer options by default for simple data source users. (We define these as users without the ability to add joins in the report designer.)
These users can still access additional features using the “More” option on the property panel. And full access users can select “Less” to collapse the property panels to a minimal view.
Lazy Loading Improves Performance
Traditionally, when working with large datasets, all of the data had to be loaded before the user could do anything. This diminishes the user experience and reduces performance. To address this issue, Izenda virtualizes the data in the UI. Virtualization means that the process of showing a specific item is postponed until the item is required in the viewport. In addition to virtualization, “lazy loading” has been added to key areas where large data sets are needed.
Instead of loading all of the data at once, only a smaller set of data is loaded initially. This initial set loads quickly and as the user scrolls down, more data is loaded as needed.
Add Multiple Fields at a Time
The more fields added to a report, the more time it takes to create it and load the resulting data. For every field added, your analytics platform needed to make another trip to the dataset to pull back that data.
Izenda added the ability for the user to add more than one field at a time in the report designer or in quick add mode. By using the “+” symbol or the link to add a field from the report part, the user can add multiple fields at one time. Rather than making multiple trips to the dataset, the platform just makes a single trip to pull all that data. The larger the dataset the more effective this feature becomes.
Additional Features from Recent Updates
- Users can now use PostgreSQL functions as stored procedures. All functions which return a set are added as stored procedures
- Added new filter operators for date time fields. Now a date, date-time or time only option are provided
- Added context menu to dashboard tile so the user can flip the tile using the context menu like the report part tiles
- Property panel items with gear icons to show additional setting options now show the green check box when used and also display a red X to remove the additional settings and reset back to default state
- Added options to the Render Report API to show/hide navigation, filter panel and toolbar
- Data Setup > Advanced Settings > Others: Added settings to define Common Filters for Dashboard
- Same field of the same data object from the same Database Schema
- Same field name regardless of the Database Schema or connection string
- Same alias name in Data Model regardless of Database Schema or connection string