5.6 Release Notes
PopMedNetTM Distributed Query Tool
Release Notes
Based on Release 5.6
6/26/16
Releases
| Date of Release | 6/26/16 | Not Released | **Not Released | Not Released | Not Released | |
|---|---|---|---|---|---|---|
| Networks Updated | Sentinel | NIH DRN | HDC | MDPHnet | PCORnet | |
| DataMart Client Update | *Required | *Required | *Required | *Required | *Required |
*DataMart client version 5.0.5+ will still function after the upgrade, but users are strongly encouraged to update as many new features are not compatible with older versions, and certain known issues (listed below) may cause an error when attempting to run a request in the 5.0.5 DataMart client.
** A 5.6.1 patch was released before HDC was upgraded to 5.6.0, thus HDC received version 5.6.1 rather than version 5.6.0.
Introduction
These release notes cover PopMedNet version 5.6. Enhancements, bug fixes, and any known issues as listed below.
A new desktop DataMart Client is strongly recommended and required to use many of the new features
Version 5.6 brings several enhancements that should result in increased speed and ease of use for administrators and end users. Specific enhancements are listed below.
*Not all features are available on every network or to every user. Contact your PopMedNet Network Administrator for more information. Bug Summary Table query types querying wrong table for descriptions Multiple password errors causing users to become locked out of the portal including: All three items have been addressed: If users wish to make use of the flexible, menu driven interface (first introduced in 5.2), for constructing queries, summary tables databases that are currently stored in Microsoft Access will need to be converted to Microsoft SQL server. The question engine infrastructure that supports the menu driven interface is not compatible with Access.Enhancements
Update Description Add Request ID to the task panel The request ID field is now visible in the task panel on the home screen of the PopMedNet Query tool. It was previously only visible on the request panel. Notification updates Administrators can now view the level at which security level notifications are assigned to each user so they can better troubleshoot issues with notifications. DataMart Routings The DataMart routing status of incomplete routings can now be modified manually in the query tool by users with appropriate permission Request Metadata Fields Request Metadata fields can now be set to be hidden, optional or required by administrators at the project and security group level. Edit Request Metadata Users with appropriate permissions can now edit request metadata after the request has been submitted Source and Funder Fields Added The Task Order Matrix / PopMedNet sync has been updated. PopMedNet now displays separate source and budget fields for task order information in a request. Personal notifications In question engine, users now have the ability to subscribe to notifications for specific requests, rather than all requests in a project Previous Login Notification Users and administrators can now see history of all previous logins and on users profiles. Bug Fixes
History time stamp gets displayed incorrectly for DataMart Routings added after original submission Previously, when a user added a DataMart routing to a previously submitted request and checked the history for that routing on the web portal, an incorrect time-stamp was displayed. This has been corrected so the correct timestamp is displayed for all routings. Filtering on "Equal To" for dates in the all grids in the portal does not work The "equal to" filtering functionality did not work on any date field in the PopMedNet portal, as all date fields include both date and time. Therefore, "equal to" was removed as a filtering option for date fields and replaced with "contains" which will allow users to find a request submitted on specific date without the need for a time value. The summary table query types used the ICD_PROCEDURE table to fill in the description field in the results window in the DataMart client. This resulted in incorrect descriptions being returned for each row in the results table; counts for all summary table requests were still correct. This has been corrected so summary table query types use the correct tables for the description values. SAS datasets set via the SAS Distribution query type were corrupted when automatically downloaded The automatic download of SAS datasets caused corruption of the file. This resulted in the SAS distribution query failing as the SAS dataset it was trying to import was unusable. This has been corrected so an automatic download no longer corrupts the file. Known Issues
Issue Workaround The 5.6 DataMart Client is designed to work with Microsoft .NET version 4.6.1 and above. Previous versions of the DataMart client were designed to work with .NET 4.5.2 and below. In rare instances, users who have .NET 4.5.2 and below may experience an error when attempting to run a Summary Table request sent to the 5.0.5 DataMart client after the Sentinel Query Tool is updated to version 5.6. Question engine requests, and therefore the new menu driven interface first introduced in 5.2, require the configuration of an additional DataMart. If a user wants to run a request using the menu driven interface, the Data partner receiving the request must set up an additional DataMart that is configured to receive question engine requests. A network administrator must also configure the portal so that users are able to distribute question engine requests. Legacy requests can still be sent to Data Partners' existing DataMarts. This only impacts the PCORnet network as they are the only network utilizing the question engine request types. Summary table queries can continue to be run via the legacy interface against an Access database. The "configuration settings" screen in the DataMart client shows selectable settings for modular program request types, even though no settings need to be configured. This is due to the nature of the question engine infrastructure and will be addressed in a future release. No settings need to be configured for modular program requests. The process to configure a DataMart client to accept modular program requests is unchanged. Click "ok" to exit the configuration settings window, do not apply any settings. The DataMart client security certificate must be updated to use question engine requests. TBD