Released by redcap on 10/14/2016 Partners Healthcare to upgrade on 11/15/2016 redcap V. 15. 11 Full Release Notes Version 15. 11 (released 10/14/2016) bug fixes & other changes


Version 6.14.0 - (released 5/13/2016)



Download 230.05 Kb.
Page3/5
Date05.05.2018
Size230.05 Kb.
#48138
1   2   3   4   5

Version 6.14.0 - (released 5/13/2016)

NEW FEATURES & IMPROVEMENTS:

  • New page in the Control Center that allows all REDCap administrator requests to be processed in a single place. This includes approving production drafted changes, API token requests, create/copy projects (if applicable), and move projects to production (if applicable).

  • All requests will be listed in a table on this page and will include all associated information about the request, such as time of request, requestor, project, request type, etc.

  • If desired, email notifications can be disabled on this page if administrators no longer wish to receive the emails associated with these requests, but instead wish to solely use the To-Do List page without any email notifications.

  • NOTE: This page will always reflect the current status of all requests, whether or not they were processed using the tables below or using the link inside the email to the administrator (if email notifications are enabled).

 New action tag: @USERNAME - Sets a field's value to the username of the current REDCap user. If this is used on a survey, the value will be “[survey respondent]”. Once the value is captured, it will not be changed when visiting the page at a later time.

 New action tag: @DEFAULT - Sets a field's initial value.



  • This action tag allows a field to have a specified default value when viewing the field on a survey or data entry form that has not yet had any data saved for it (i.e., when the form status icon is gray or when a survey has not been started).

  • The format must follow the pattern @DEFAULT="????", in which the desired default value should be inside single or double quotes.

  • For checkbox fields, simply separate multiple checkbox values with commas - e.g., @DEFAULT='1,3,6'. NOTE: The default value does *not* get applied during any data imports (via API or Data Import Tool) but only operates when viewing survey pages and data entry forms.

  • For text fields, you may even perform Piping inside the default value to pipe data from another field in the project - e.g., @DEFAULT=”Name: [first_name] [last_name], DOB: [dob]”.

  • NOTE: If being used on a date or datetime field, the date value inside the quotes must be in Y-M-D format - e.g., @DEFAULT='2007-12-25'.

  • If this action tag is used on a survey question that is utilizing a survey pre-fill method (via query string or POST submit), then the pre-fill values supplied will override the default values provided by the action tag.

 New hook: redcap_every_page_top - Allows custom actions to be performed at the top of every page in REDCap (including plugins that render the REDCap page header)

 New hook: redcap_every_page_before_render - Allows custom actions to be performed by every PHP script in REDCap (including plugins) before the script itself begins to be formally processed.

 Improvement: When in production, users can now request that a project be deleted by an administrator. The request will be added to the To-Do List in the Control Center, and the administrator will be emailed (if email notifications are enabled).

 New method for hooks/plugins: REDCap::getCopyright - Returns the REDCap copyright text to be displayed on all pages - i.e., "REDCap X.X.X - © 20XX Vanderbilt University". This is recommended to be used if a hook is utilized to alter an existing REDCap page so much that the normal page footer that contains the REDCap copyright notice is no longer displayed. Thus you may use this method to display the copyright notice on that page but in a different way or in a different location. This is to conform to the REDCap license agreement that stipulates that the REDCap copyright notice should not be removed from any REDCap pages (this excludes plugins).BUG FIXES & OTHER CHANGES:



Change: To be more consistent and simpler with regard to how REDCap administrators are notified about user-submitted requests, the “Person who will approve changes for production projects” option has been removed from the system-level and project-level configurations. Instead, REDCap will now use the “Project Contact Person” name and email for *all* requests rather than using the two options for various requests, which can be confusing regarding which will be used for what type of request. This will keep things much more simplified going further.

Change: On the General Configuration page and Edit A Project’s Settings pages in the Control Center, the option “Project Contact Person” has been re-labeled as “Name of REDCap Administrator” to improve clarification regarding what this option refers to.

Change/improvement: Piping can now work recursively in case the initial data that is piped also contains variables that should then be piped.

Change/improvement: The mailto link at the bottom left of a project has now been replaced with a "Contact REDCap administrator" button that, when clicked, opens the user's default email client and pre-fills the email body with their username, the title of the current project, and a link to the project. This should help administrators in case this information is not provided by the user themselves, which is often the case.

Bug fix: When creating a new Data Quality rule that contains "<-", such as "[field]<-6", in which the "less than" character is followed immediately by a minus sign, it would mistakenly remove everything in the logic beginning with the "less than" sign and after it, and would thus cause the entire logic not to execute correctly.

Bug fix: When exporting a project's metadata and data as a project XML file on the Other Functionality tab of the Project Setup page, the title of the dialog would mistakenly say "Exporting 'report'" when it should instead say "Exporting 'Entire project (metadata & data)'".

Change: When adding a new field in the Online Designer, the Custom Alignment setting no longer resets back to "Right Vertical (RV)" alignment every time as it did in previous versions, but instead it now reverts to the alignment value of the previous field that was opened beforehand while on that page.

Bug fix: If using question auto-numbering on a survey that contains fields that utilize the @HIDDEN or @HIDDEN-SURVEY action tag, it would mistakenly not display the question numbers correctly but would appear to skip some because they belong to the questions being hidden.

Bug fix: A fatal PHP error would occur if calling the "Import Events" API method with the "override" parameter having a value of FALSE. (Ticket #1199)

Change/improvement: The Browse Projects page in the Control Center now displays a project's PID (i.e, its project ID number) next to the project title to allow administrators to more easily identify a project, especially when some projects are similarly named and thus difficult to tell apart.

Bug fix: When viewing the Project Setup page on a mobile device, the link to the My Projects page inside the navigation drop-down list at the top of the page would not be formed correctly, thus causing the link not to work correctly.

Bug fix: If a field references a checkbox field in its branching logic or its calculation (if a calc field), then if the checkbox field's instrument is copied using the Copy action in the Online Designer, the new copy of the checkbox variable would mistakenly not get updated in the branching logic or calculation. (Ticket #1206)

Bug fix: On some project pages, the page footer might mistakenly cover some content at the very bottom of the page. (Ticket #1204)

Improvement: Added an "Edit" link on the left-hand project menu in the "Project Bookmarks" panel to allow users to easily navigate to the Project Bookmarks page if they have Project Design/Setup privileges.

Improvement: When copying a user role on a project's User Rights page, the Edit Role popup now opens immediately after copying a role to allow the user to more easily modify the newly created role.

Bug fix: When creating or editing a report in a project, HTML tags used inside Field Labels would mistakenly get displayed in the field drop-downs on the page, thus causing it to be difficult to view all the Field Labels in the drop-down correctly. (Ticket #1203)

Bug fix: If a matrix of fields has matrix ranking enabled, in which one of the choices in the matrix contains a period/dot in its raw/coded value, then the ranking feature would not work and would mistakenly throw a JavaScript error.

Change: Small clarification in instruction text when a REDCap administrator is creating an API token for a user.

Change: If the REDCap web server already has a large value set for the "max_execution_time" setting in PHP.INI, then REDCap will not lower that setting's value if REDCap's required value is smaller than the system value.

Bug fix: When using the CDC's SAMS authentication, it was mistakenly reporting every page request as a login event in the redcap_log_view database table. This did not affect anything other than causing all logged web requests to be duplicated in the backend database.

Bug fix: The survey table of questions might mistakenly be too narrow (not full width) in some web browsers when taking a survey that is a CAT (computer adaptive test) or auto-scoring instrument downloaded from the REDCap Shared Library.

Bug fix: If the Dynamic Data Pull (DDP) module is enabled for a project, and a non-temporal field's value (e.g., last name) has been imported into REDCap from the source data system, then if the value in the source system ever changed afterward, it would mistakenly never get pulled into REDCap to allow the new value to be adjudicated by a user. Now if it detects that a non-temporal field's value has changed when pulling data from the source system again, then even though it has already been cached in REDCap, it replace the cached value with the new value received from the source system, and will prompt the user to re-adjudicate the new value.

Bug fix: Normal users were not able to do anything on the Record Locking Customization page in a project due to a JavaScript error. Bug emerged in version 6.13.0.

Bug fix: Live Filters on a given report will have no effect when viewing the "Stats & Charts" page for the report, but instead the report will mistakenly display all results as if a Live Filter had not been selected. (Ticket #1219)

Fixed a typo in some Twilio instructions. (Ticket #1209)

Bug fix: When clicking the [?] link for the option "Enable auto-complete for this drop-down" in the Add/Edit Field popup on the Online Designer, it would mistakenly make the browser go to a blank page in certain web browsers (e.g., Firefox).

Fixed typo for instructional text when moving a project to production.

Bug fix: When using the Randomization module in a project, if a super user uploads a new allocation table while in production in order to append those allocations to the existing randomization allocation table, it would mistakenly not log the event.

Change/improvement: The REDCap installation package now comes with the hook_functions.php file and a hooks directory, and the path to the hook_functions.php file is set automatically during the installation process.

Change/improvement: REDCap now uses the value of session.cookie_secure in the PHP.INI configuration file when setting the default cookie parameters. This allows for the "Secure" cookie attribute to be set to True if session.cookie_secure=On in PHP.INI. By default, the "Secure" cookie attribute is set to False.

Version 6.13.3 - (released 4/22/2016)

  • Major bug fix: If using the Randomization module in a project while viewing a data entry form of a record that had already been randomized, it is mistakenly possible to click the "Delete data for this form only" button and delete the form's data even when the randomization field or strata fields exist on the page. There should be no way to modify the value of the randomization field or strata fields once a record has been randomized. In this case, it now displays a message saying that the form's data cannot be deleted for the reasons above.

  • Major bug fix: If using the Randomization module in a project while viewing a data entry form of a record that had already been randomized, it is mistakenly possible to click the "Delete data for this event only" button and delete the whole event's data even when the randomization field or strata fields exist on that event. There should be no way to modify the value of the randomization field or strata fields once a record has been randomized. In this case, it now displays a message saying that the event's data cannot be deleted for the reasons above.

  • Major bug fix: If one or more data entry forms have been locked on a given event for a record in a longitudinal project, then it would mistakenly be possible to click the "Delete data for this event only" button at the bottom of the data entry form. There should be no way to delete values for a locked form. In this case, it now displays a message saying that the event's data cannot be deleted until all of the locked forms on the event have been unlocked by someone with locking/unlocking privileges.

  • Change: Added a compatibility notice for the embedded audio option for attachments for Descriptive fields on surveys and data entry forms. The compatibility notice informs the user that the embedded audio option for attachments is not 100% compatible for all audio file types across all web browsers. This is not a limitation in REDCap, but is simply a compatibility issue across web browsers. The most compatible audio file types to use are MP3 and WAV. Other audio types may work on some browsers but not in others. Unfortunately, there is not always an easy way to know what audio file will work for which browser, especially as operating systems and web browsers evolve over time.

  • Improvement: When a user opens the Data History popup or the Data Resolution Workflow popup for a given record/field, the popup should now open a bit more quickly than before if it had been slow in the past, especially for projects with many records and/or data changes.

  • Bug fix: Issue when using Twilio telephony services when using a proxy with the REDCap web server. (Ticket #1190)

  • Bug fix: When importing data via the Data Import Tool or API data import, the number of records that were created or modified during the import would mistakenly be reported as the number of values that were added/updated rather than the number of records that were created/modified. Bug emerged in 6.13.2. (Ticket #1189)

  • Bug fix: If a BMP image file was used as an inline image for a Description field on a data collection instrument, then a fatal PHP error would occur if a user attempted to download a PDF of that instrument, thus preventing the user from ever downloading the PDF successfully. It now simply omits the BMP file in the PDF because the third-party PDF software used in REDCap is not able to render BMP files. But at least the user will be able to download the PDF now.

  • Bug fix: For certain server configurations, the Configuration Check page might mistakenly say that the database structure is incorrect when there is actually nothing wrong, in which it would display a lot of SQL queries to fix the "issue" that would fail if they were run (although they would not harm anything).

  • Bug fix: If Automated Invitations have been set for a survey, in which it is using conditional logic to trigger the invitations, and if the logic contains the operator "<=", then when the Automated Invitations popup is reloaded at a later time, it would mistakenly insert a space into the operator ("< =") when displaying it in the popup. Although this issue does get caught by REDCap before allowing the user to save it (thus it should not cause problems), it still is rather annoying to have to manually fix every time prior to saving the logic again.

Version 6.13.2 - (released 4/19/2016)

Major bug fix: Some specific web server configurations might throw a fatal PHP error if a user attempted to use the API Metadata Import method or attempted to export/import a CDISC ODM file.



Major bug fix: When using the Randomization module in a project and saving data on the data entry form where the randomization field is located, it is possible in some rare cases that the value of the randomization field, despite being disabled on the page, might somehow get changed (i.e., as seen on the data entry form or reports/exports - although its value in the randomization allocation table will remain unchanged). This might occur due to unforeseen interaction with certain browser extensions, as well as due to unknown manipulation of the form when using certain tablets. More safeguards have now been added in order to prevent the randomization field's value from ever changing on a data entry form.

Bug fix: When importing data via Data Import Tool or API for a field with "vmrn" validation (Vanderbilt medical record number), it would mistakenly convert any blank values into the value "000000000" when importing.

Bug fix: If non-Latin characters (especially multi-byte characters) exist in a project title, then the project title would not display correctly on the My Projects page on a mobile device (small screen) but would instead be garbled. Bug emerged in version 6.13.0. (Ticket #1182)

Change: Disabled the backspace-goes-back "feature" of browsers, which could cause unexpected issues and confusion if a user accidentally clicked the backspace button on a page.

Bug fix: If using the Dynamic Data Pull (DDP) module with "Preview Fields" enabled, then if a value is entered for a source identifier field on a data entry form and then the record is saved after viewing the Preview Fields while a required field is left blank on the page, then it would mistakenly not display the DDP adjudication popup on the next screen but would instead show the required field popup. It now shows the DDP popup instead.

Change: Matrix fields are now no longer allowed to have a Field Label. (Ticket #1188)

Change: The width of date and datetime fields was increased on surveys with "Large" or "Very Large" text so that the entire value is always visible.

Bug fix: If a file is uploaded to a File Upload field or Signature field on a survey or data entry form and then another File Upload field or Signature field is opened within one second of closing the first one, then the second field's popup prompt would mistakenly close. This would require the user to have to reopen it.

Version 6.13.1 - (released 4/12/2016)

Change: The Configuration Check page now checks to make sure that the DOM extension in PHP is installed.



Bug fix: The table displayed on the Record Status Dashboard and Event Grid (in longitudinal projects) might get widened too far on mobile devices in certain cases or if the browser window is resized. This would make the page unusable.

Bug fix: When using the Quick Add feature when adding/editing a report, if an instrument begins with a Descriptive field, then it would mistakenly not display the instrument name and the "Select All/Deselect All" options in the Quick Add popup, thus making it impossible to select/deselect all fields in that instrument at once.

Bug fix: If the words "and" or "or" are used inside single quotes or double quotes in branching logic or a calculation (e.g., [text_field] = "x and y"), then it would not get parsed correctly and thus would not function as expected. (Ticket #1160)

Bug fix: When sending emails in a Google App Engine environment, REDCap would think the emails did not send even when they actually did.

Bug fix: It was not possible to move a project to Inactive status because the button on the Other Functionality did not do anything.

Bug fix: When using the REDCap::getPDF method in a plugin or hook, in certain circumstances it might mistakenly return a single instrument in the PDF even though the $instrument parameter is passed as NULL in order to force it to return all instruments. (Ticket #1177)

Bug fix: When performing a search using the Data Search utility on the Add/Edit Records page, it might mistakenly return results that belong to orphaned events that have since been deleted.

Change: The enhancement added in a recent version to prompt the user to have a text field's value automatically trimmed if the value begins or ends with whitespace was mistakenly being applied to Notes fields when it should have only been applied to Text fields.

Version 6.13.0 - (released 4/8/2016)

New feature: Responsive design of REDCap web pages

Now has a more flexible and responsive user interface to conform to and fit screens on devices of all sizes.

Major improvement for how surveys and data entry forms look on mobile devices (i.e., phones), including automatic font increase and forced left-alignment of questions for better user experience when screen real estate is limited.

REDCap now has the Bootstrap front-end framework embedded inside it, thus allowing plugin/hook developers to utilize all the Bootstrap UI elements and features.

Technical note: The “label” CSS class used for field labels in the question table on surveys and data entry forms has been replaced with “labelrc” to prevent conflicts with Bootstrap.

Improvement: Slider fields on surveys and data entry forms are now much easier to use on mobile/touch devices.



Improvement/change: When a user moves a project to production (or requests to have a project moved to production) on the Project Setup page, it now forces them to choose if they want to delete all project data or to keep all existing records. In previous versions, it would pre-check the “delete all data” checkbox, which could sometimes cause users to unwittingly lose all their data if not paying attention to what they are agreeing to.

Improvement/change: A new system-level setting allows administrators to hide the option where users can export an entire project as a single REDCap XML file (i.e., project backup). Because some institutions are wary of users feeling the need to download an entire project and its data, they may unwittingly download unencrypted project backups (containing data) to store on their local drive, which could be a security or privacy concern. This option can now be disabled on the Modules Configuration page in the Control Center.

Change: The Record Locking Customization page in a project now allows normal users to view the locking and e-signature information in read-only format when in production. In previous versions, only super users were allowed to view this page in production status.

Major bug fix: If the randomization module is enabled in a project and is using Data Access Groups to randomize by group/site (i.e., using DAGs as a strata field), then it is possible to delete any given Data Access Group and thus cause catastrophic issues with the randomization process, especially if the randomization allocation table has already been uploaded and/or users have already begun to randomize records in the project. It now prevents users from deleting DAGs if randomization has already been enabled and set up. (Ticket #1135)

Major bug fix: If the function min() or max() is used in a calculated field, then auto-calculations (via data import, Data Quality rule H, etc.) might mistakenly not get triggered for this field and thus might leave the existing incorrect value as-is. This is related to bug fix for these functions in the previous version.

Bug fix: If a survey has custom survey theme options set (as opposed to using a pre-built theme), then the custom theme options would mistakenly not be reflected on the Survey Completion Text page after a participant has completed the survey.

Improvement: The User Rights page in a project now prevents users from mistakenly assigning themselves to a role that does not have User Rights privileges, which could inadvertently cause them to be locked out of that page in their own project.

Bug fix: If the first field on a data entry form is a drop-down autocomplete field that has no value entered yet, then the drop-down's choices will not be displayed automatically when the page loads. This is done in order to simulate the behavior of real drop-down fields and also because the previous behavior it confused some users and might even cause the website to react in unexpected ways if the list was very long when displayed on smaller screens.

Bug fix: If a user has uploaded a WAV audio file as an attachment on a Descriptive field on a form or survey, then it would not be able to play the sound file in any version of Internet Explorer if the user has selected the file to play in an embedded player on the page. (Ticket #1158)

Bug fix: When attempting to import a REDCap project XML file when creating a new project, in which the XML file contains data for checkbox fields, it would display an erroneous error message and would prevent the user from creating the project. (Ticket #1154)

Bug fix: When attempting to import a REDCap project XML file when creating a new project, in which the XML file contains data and also contains Data Access Group assignments for the records in the data, it would throw an erroneous error and prevent the user from creating the project. It now ignores any DAG assignments in the XML data during the project creation process since no DAGs will actually be created in the new project during this process.

Bug fix: If a project has fields that contain UTF-8/non-Latin characters that have been encoded incorrectly (often due to Microsoft Excel not saving a data dictionary in the right character encoding), then the project might mistakenly not sync to the REDCap Mobile App when attempting to set up the project on a mobile device.

Bug fix: If a field in a project is selected to be the Secondary Unique Field and that field also has field validation (e.g., integer, email), then the field validation will mistakenly get removed when viewing that field on the data entry form or survey page, thus allowing data in any format to be entered without validation. (Ticket #1138)

Bug fix: If a field is hidden because of the action tag @HIDDEN, @HIDDEN-SURVEY, or @HIDDEN-FORM, then it would mistakenly not hide the section header belonging to that field's section if all fields in the section were hidden (due to either branching logic or due to @HIDDEN action tags).

Change: On the Survey Settings page in the Online Designer, the text for the "Delete Survey" button at the bottom of the page has been changed to "Delete Survey Settings" to reduce confusion regarding what the button does.

Bug fix: Due to changes in MySQL 5.7.4, a database table cannot have a date field with '0000-00-00' as a default, which was causing some issues during REDCap installation.

Bug fix: When utilizing the Randomization module in a project and using one or more strata fields, if a user is randomizing a record but does not have edit privileges to a data entry form on which one of the strata fields is located, then it would mistakenly allow the user to modify the value of the field during the randomization process despite not having edit privileges to do so.

Bug fix: When resetting the password of a user when using Table-based authentication, it might sometimes mistakenly lock the user out of REDCap for a limited period of time (as if they had several failed login attempts) after clicking the "Set your new password" link in their email. This was supposedly fixed in earlier versions but still persisted randomly in rare cases.

Bug fix: If new Table-based users are being created via uploaded CSV file on the "Create Users (Bulk Upload)" page in the Control Center and they have non-Latin/UTF-8 characters in their name, comments, or other attributes, it would not be able to display those attributes correctly when viewing the user's account on the Browse Users page if the CSV file being uploaded was not encoded correctly as UTF-8 encoding with a BOM (byte-order mark).


Download 230.05 Kb.

Share with your friends:
1   2   3   4   5




The database is protected by copyright ©ininet.org 2024
send message

    Main page