/
Reporting Module Release Notes 0.6.x

Reporting Module Release Notes 0.6.x

By Mike Seaton
Aug 12, 2011
3 min

Known Bugs

List of known issues in the current reporting module release which potentially result in incorrect data

  • REPORT-166 - Ensure that all date-based queries are appropriately handling boundary conditions

Version 0.6.2 released July 19, 2011

Bugfixes:

  • REPORT-246 - Display a more user-friendly message when required fields are blank "report.userEnteredParams"

  • REPORT-262 - Modify behaviour of global property reporting.preferredIdentifierTypes

Features/Improvements:

  • REPORT-122 - Allow CohortDefinitions to have a user property that is restricted to providers

  • REPORT-258 - Support hiding the base cohort selector on the run report page if a base cohort definition is already configured on the report

  • REPORT-163 - Remove (or indicate) retired locations for Report parameters

  • REPORT-221 - Support limiting parameters to only a subset of available options

  • REPORT-257 - Support rendering of multi-row datasets with Excel Templates

  • REPORT-264 - Support message translations as definition names when rendering reports

Version 0.6.1 released May 27, 2011

Bugfixes:

  • REPORT-216 - Edit and Delete icons don't perform desired action when clicked when editing a period indicator report

Version 0.6 released May 26, 2011

Bugfixes:

  • REPORT-5 - Exception "Failed to schedule task Delete Old Reports" in Logfile for every Report

  • REPORT-43 - Data Set Viewer - SQL Datasets are not limited (attempts to preview all)

  • REPORT-77 - Need Manage Definitions Privilege

  • REPORT-84 - Create Initial Queries creates queries that are missing parameters

  • REPORT-86 - Report History page displays a 404 error

  • REPORT-92 - In the Analysis & Reporting header, Data Set Viewer is not bolded when that page is selected

  • REPORT-136 - Ensure that missing REPORT_RESULTS does not cause an error

  • REPORT-175 - Coded Obs Cohort Definition - trying to specify the "In" answers as a parameter does not properly save and render on the page.

  • REPORT-180 - NPE when trying to evaluate a custom data set definition

  • REPORT-206 - NPE execption is thrown if any of the parameters of a definition is not set

  • REPORT-214 - Download in "web" format not correct

  • REPORT-217 - Subclasses of DefinitionService need to declare @Transactional(readOnly=true) on their evaluate methods

  • REPORT-218 - If a scheduled report run fails, the only way to know is from the server log

  • REPORT-224 - Evaluating SQL Data Sets does not produce any results

  • REPORT-226 - ReportDefinitionType needs equals() method to be null safe

  • REPORT-229 - DataSetDefinition evaluation happens without setting evaluation context parameters

  • REPORT-235 - Aliases do not work in SQL Data Set definitions

  • REPORT-236 - Reporting Permissions Issue

  • REPORT-238 - Excel Template Renderer should support multiple datasets

  • REPORT-248 - character matching in isSelectQuery method in SqlUtils should match on any whitespace, not just a space

  • REPORT-249 - Change renderers to use OutputStreamWriter (set to UTF-8) instead of PrintWriter

Improvements:

  • REPORT-119 - Fix header on History of Indicators page

  • REPORT-120 - Mandatory fields not enforced on the edit cohort queries page

  • REPORT-121 - Replace all references to class names (PeriodIndicatorReportDefinition) from the UI

  • REPORT-128 - Edit Logic Data Set Definition page should allow you to test logic statements without having to leave the page

  • REPORT-144 - Improve handling of "No available Data Set Definition" use case in the Data Set Viewer

  • REPORT-171 - Indicator History - Allow user to specify the date range looked at (rather than just 12 months, etc)

  • REPORT-195 - Refactor ReportRequest to have a Mapped<ReportDefinition> instead of a ReportDefinition and a Map<String, Object> of parameters

  • REPORT-234 - Gender cohort definition should have Boolean properties rather than boolean

  • REPORT-239 - Add feature to delete old report requests from UI

  • REPORT-243 - Compress persisted report data and exception files on disk

  • REPORT-176 - Confirm and add necessary code to ensure that sql cohort definitions and sql data set definitions can't perform updates or deletes

  • REPORT-186 - Complete design of tickets that are in the "Design Review" state

  • REPORT-240 - Ensure it is not overwhelmingly slow to serialize report data to disk

New Features:

  • REPORT-56 - Reporting module: Enable more complex parameter calculation like ${endDate-1m-1w}

  • REPORT-61 - Improve error message when a report tries to use a sub-element that has been deleted

  • REPORT-71 - Need options to allow which cohort to use in the Run Report Page

  • REPORT-98 - Debug and implement Cohort Definition validation

  • REPORT-107 - Allow user to configure a scheduled task that runs a time/CPU intensive report

  • REPORT-158 - Add Time Modifier to EncounterCohortDefinition

  • REPORT-182 - Saving an Report based on Cohorts should also save the underlying Cohorts for later viewing

  • REPORT-189 - Support hour-based calculations in date parameter expressions

  • REPORT-210 - Sort list of reports

  • REPORT-219 - Reduce loglevel for evaluateParameterExpression