We’re always getting better.
With Logi Report 18, we’ve made several enhancements that help your software team deliver a superior user experience while reducing development costs and accelerating your product roadmap.
Keep reading to learn about the pain points we’ve identified and how we’ve addressed them with our recent enhancements.
Delivering a Superior User Experience
Report-Level Data Security
Software teams are faced with the challenge of empowering end users with access to the right data and tools without complicating their workflow or compromising security. Finding the right balance can be an ongoing pain point for many developers.
In Logi Report 18, you can restrict the data sources that end users can apply at runtime. End users can only access data from the constrained business view and create visualizations based on that data, delivering them a greater guided experience with focused data views.
Custom Axis Hints
You may have heard that data without context is meaningless. What you may not have heard (though you may have realized) is that data can always have more context. Your end users know this as well.
Logi Report 18 comes with the data marker function allowing users to customize the names of data fields on axis values, enabling them to provide more contexts and meaningful information. With the ability to offer more report customization options, you can ensure that your application meets the needs and use cases of various users through clear, informative reports.
Reducing Development Costs
Business View Accessibility
As your business and user-base grow, so does the demand on administrators to deliver the right amount of access to each user. Creating an easier and more efficient workflow for this process can help reduce costs and improve productivity.
For Logi Report 18, we’ve released a business view security page for server administrators in your team to easily specify permissions to access business views for each use or group.
Another by-product of business growth is changes in personnel. To help promote smooth transitions and reduce bottlenecks, Logi Report 18 no longer makes report ownership permanent.
With the new report permission setting, you can easily assign and transfer ownership of a report when there are changes in personnel to avoid recreating reports and saving developer time. The assigned owner of the report will be allowed to perform several types of actions such as edit or share the report without any permission limitations.
Custom Aggregations for Group Levels
As we mentioned, your data can never have enough context. With Logi Report 18, users now have the option to show specific values such as the maximum or minimum value from different types of group aggregations in their reports. This gives users them better control over how their data is framed and lets content authors calculate new metrics and KPIs.
To do so, users specify the columns that will be used as variables and use formula editor to calculate the desired values of data groups.
Accelerating Your Product Roadmap
Dynamic Page Setup for Prints
Speaking of the varying needs and use cases of your end users, it’s likely that in a given report, not all the information is relevant for all your users. The ability to specify which information is included on a report would not only improve the quality of the report, but also help deliver more concise information to the recipient.
In our recent enhancement, Logi Report now supports users to dynamically specify whether to include a specific data column in an export format (PDF, Excel, HTML, etc.) but exclude it from other report formats. You can also allow your end users to dynamically generate reports with different layouts for different audiences across the world, ensuring user satisfaction.
Other functionality enhancements include:
- Engine performance optimizations
- Support MongoDB APE modification
- Enhanced exporting option when selecting Excel
- Support for Query in “Bind with Column” parameters
- Option to show or hide Sub Reports in Page Report Studio
For more information on Logi Report 18, please see our documentation