Izenda Product Release – v3.6.0 October 2019
TL;DR:
Pivot grid improvements are under way! We’ve introduced a new separator style for pivot grids as the first piece in functional improvements for grid-based reporting. We’ve also introduce a new API endpoint for user loading, added new logging values, and continued improving our Excel connector.
Consider the Following:
For Izenda users, separators can be a crucial element of their report design. How are they expecting the data to be broken out, and how should it be displayed? Previously, Izenda had a variety of separator styles that would always result in smaller pivot grids for each unique separator value. Now, with the Logical Separator Style, you can display all of your content within one pivot grid, while still displaying unique subtotals for each value, offering a new way for users to represent pivoted data.
We’ve introduced a new way to load one user’s data at a time, avoiding heavier API loads and speeding up the process when you want to access one specific user’s information. This is our second external endpoint in our ever-expanding library.
When it comes to logging, we have some customers that leave our behavior as it is out of the box, and those who adjust it to log into a database. In either scenario, determining what API interactions happened on a specific report, or within a specific tenancy was tedious and difficult. We’ve introduce two new elements to our logging that presents the Tenant’s name, or the report’s GUID for easier searching.
Developer’s District:
Pivots grids will have the new Logical separator available by default within the Separator Style dropdown. This enables the ability for larger pivot reports to show separators within the same grid structure while still enabling subtotals to be calculated for each separator. There is no additional configuration for this behavior, so as soon as the upgrade is done it’ll be available to all report creators.
Concerning our user endpoint, we added the api/external/user/loadUser endpoint into the application. This endpoint will accept a pairing of the username and tenant you are looking for and will return any information for that user, including their role information. The intent behind this is to allow a more prescriptive means for our users to access specific users to update or modify them as needed.
Our new logging parameters are present upon installation and require no further setup in order for these values to be displayed. In your logs, these parameters will be an empty bracket, or a bracket displaying null, depending on the types of requests being made. Often the internal system-centric actions display null.
For more information on our release in general, please see our release notes page: https://www.izenda.com/docs/release_notes.html
Continued Success,
Seth Hutcheson
Technical Product Manager, Izenda
