We’re proud to announce that ReportWORQ 5 has now surpassed 1000 automated integration and regression tests that run every month before our official release. These tests include automation to ensure that new features continue to work and regression tests to make sure anything that required a fix stays fixed.
1022 Integration & Regression Tests Passing
Enhancements
- Support for dynamic burst sets using SQL or Excel.
- Support for overriding Adaptive parameters with List parameters.
- Enhanced Google Drive support for Impersonation, Drive Selection & Folder by name or id
Fixes
- Fix for correct credentials failing to authenticate a user.
- Fix for API call showing as Pending instead of Success / Failure on Job completion.
- Fix for ReportWORQ Cloud Integration enablement.
ReportWORQ 4 was not released this month since there were no changes. If you have not upgraded to version 5 yet and would like to discuss the path to upgrade, then please contact us at support to schedule a discussion. support@reportworq.com
Notes regarding Burst Sets
When it comes to bursting (creating and sending many copies of a reports based on different data filters) ReportWORQ has several options to choose from.
One option is in the parameters screen any parameter can be set to “One report per item”, this feature will automatically create multiple output files for each item in this parameter’s list. This works well with dynamic queries such as MDX, Planning Analytics Subsets or SQL Queries.
Another option is to choose “Enable for bursting” on one or more of the parameters. This will reveal the Bursting screen where a row can be added for each report output that you would like to create. Each row will indicate the parameter values to use for that copy of the report. While this is a simple and direct approach to report creation, it could be tedious to manage all of this information in a web page.
This brings us to the new feature which is using an Excel file or a SQL table to provide the information for how many reports to create and what parameter values should be used for each copy of the report. Now an Excel file can be maintained to supply this information to ReportWORQ, which makes it easier to supply and maintain this the configuration for a Report Bursting Job (especially if the information changes often). Details on this new feature are documented here: Support for dynamic burst sets using SQL or Excel.](Jobs)