Redcap Release Notes – Major lts release (Derby) Version 1 (released 05/29/2015) new lts branch


Version 6.2.2 (released 11/14/2014)



Download 218.62 Kb.
Page4/5
Date30.06.2017
Size218.62 Kb.
#22179
1   2   3   4   5

Version 6.2.2 (released 11/14/2014)

  • Minor security fix: A malicious user might be able to utilize SQL injection on certain pages to delete some or all of the fields from other projects to which they do not have access. This would not affect any of the saved data but only the metadata (fields, forms, etc.) in the project.

  • Bug fix: When sending a survey invitation from a data entry form using the "Survey options"->"Compose survey invitation" popup and manually providing an email address in the text box even though one or more existing email addresses are displayed as a drop-down choice in the popup, it would mistakenly not send the invitation to the email address that was manually entered but would instead send it to the email address originating from either the Participant List or (if applicable) designated survey invitation field.

  • Bug fix: When viewing the participant list of an initial survey (i.e., first instrument), the "Remove all participants" button was mistakenly removing participants who had already completed the survey (partially or in whole), which could incidentally cause some "ghost" participants to appear in the list afterward and cause confusion. It should only be removing participants that have not started the survey yet and thus do not have a corresponding record in the project.

  • Bug fix: If a project contains a field with the variable name "page", then if a user is viewing a survey response on the data entry form and clicks the "Edit response" button at the top, it will take them to a non-existent page (i.e. a 404 error).

  • Bug fix: If a user with "Full Data Set" data export privileges performs a data export on the "Data Exports, Reports, and Stats" page and checks the "Hash the Record ID field" checkbox option, it would mistakenly not hash the Record ID unless the Record ID field had been tagged as an Identifier field. In this case, it should always hash the Record ID if the checkbox is checked when the user has "Full Data Set" data export privileges.

Version 6.2.1 (released 11/07/2014)

  • New feature: Survey Invitation Reminders - In addition to sending or scheduling survey invitations, users may now set reminders for a given invitation to help remind respondents that they need to complete a survey if it has not been completed by a specified time. A single reminder may be sent at an exact date/time, or a user may schedule up to 5 reminders to be sent according to a set time schedule, such as a recurring time lapse (e.g. every 12 hours after the original invitation) or on a recurring day/time (e.g., every day at 10:00AM after the original invitation; every Monday at 4:00PM). If the survey is completed, then any unsent reminders will be erased and will not be sent. Survey invitation reminders can be set in the Compose Survey Invitations popup on the Participant List page, as well as in the Automated Survey Invitations popup on the Online Designer.

  • New feature: Survey Confirmation Email - On the Survey Settings page in the Online Designer, a survey administrator can now set up an email that will automatically be sent to the respondent when they complete the survey. They may optionally add one attachment to the email, if they wish. Also, piping can be used in the email's subject and message to help personalize the email. If the respondent's email address is not on file and thus the confirmation email cannot be sent automatically, then when displaying the survey acknowledgement text at the end of survey, it will display an option for the respondent to enter their email address so that they may receive the confirmation email.

  • New feature: The red Required field text (i.e., "*must provide value") can now be hidden on survey pages, if desired. So if you would rather your respondents not see that red text beneath all your required fields on the survey page, then you may use this setting to hide it. This setting can be found on the Survey Settings page in the Online Designer.

  • New feature: The "Previous Page" button (i.e. Back button) on multi-page surveys can now be hidden, if desired. Hiding this button may be useful if you wish to prevent respondents from going back to previous pages in the survey. The setting to enable this can be found on the Survey Settings page in the Online Designer.

  • Bug fix: When executing rules on the Data Quality page when the project contains data access groups, if a user excluded a particular discrepancy that was returned from one of the rules, it would mistakenly not deduct that excluded discrepancy from the DAG discrepancy counts when the rules were executed again (although the total discrepancy count would be accurate).

  • Bug fix: When viewing the Stats & Charts tab for a report that utilizes filters (i.e., Step 3 when creating a report), in which the project's record ID field is not included in the report's list of fields, then the Stats & Charts page will mistakenly be missing a lot of things, which will be empty, such as most of the statistical counts, plotted variables, and records in the record selection drop-down list.

  • Bug fix: When calling the REDCap::getData method inside a project-level plugin, in which the project_id is explicitly passed to the method and is different from the project_id of the current project context, then if the $filterLogic parameter is explicitly passed to the getData method, then it will mistakenly return empty results every time. However, if the $filterLogic parameter is not explicitly passed to getData, then the bug will not occur. (Ticket #734)

  • Bug fix: In very rare instances where Field Labels with special characters (e.g. non-Latin, UTF-8 encoded) are being displayed on certain pages, the Field Label's text might mistakenly not display on the page at all but appear as blank.

  • Bug fix: When viewing the Stats & Charts page for a report, the table of descriptive stats (e.g., mean, stdev) displayed for a given field might not always be accurate for longitudinal projects because it would sometimes mistakenly not include the data from all events for a given record.

Version 6.2.0 - codename "White Chocolate Macadamia Nut" (released 10/31/2014)

  • New feature: "Signature" field type - Allows a person to draw their signature on a survey or data entry form using a mouse, pen, or finger (depending on whether using a desktop computer or mobile device). Once captured, the signature will be displayed as an inline image on the survey page or data entry form. While this option appears as a "Signature" field type in the Online Designer, it is specified in the Data Dictionary as a "file" type field with validation type of "signature". Thus, it is essentially a special type of File Upload field. Note: The signature image for Signature fields cannot be imported via the API, although they can be downloaded or deleted via the API using the "Export a File" and "Delete a File" API methods, respectively.

  • Major bug fix: When using Automated Survey Invitations to send survey invitations, if the ASI's "Conditions" section only uses the conditional logic option and does not use the "when the following survey is completed" option, then on certain occasions invitations might be mistakenly re-sent to respondents even though they had already completed that survey, which would result in a "survey has already been completed" message when the respondent clicks the survey link in the invitation.

  • Change: When uploading a file for a File Upload field on a survey or data entry form, it now auto-closes the popup after a couple seconds as a convenience. It does this also when deleting a file for a File Upload field.

  • Change: In reports, any headers (i.e. field labels) that are over 100 characters long will be truncated to prevent the header row from getting too tall.

  • Change: Small aesthetic changes to the look and behavior of the Compose Survey Invitations popup on the Participant List page.

Version 6.1.4 (released 10/24/2014)

  • Major bug fix: If a user has user privileges of either "De-identified" or "Remove all tagged Identifier fields" as their data export rights, then when using the "Export Records" API method, in which no fields are explicitly provided in the API request, then it will mistakenly not perform the de-identification process or remove Identifier fields as is dictated by their user rights. However, in this situation, if instead some fields are manually provided as an array in the API request, this issue does not occur.

  • Major bug fix: When a user with "De-identified" data export rights performs a data export on the "Data Exports, Reports, and Stats" page, it would mistakenly hash the Record ID in the resulting CSV data file, even though the Record ID field is not an Identifier field. It should only do this when the Record ID field is an Identifier. (Ticket #729)

  • Bug fix: If Automated Survey Invitations are enabled for surveys in a project, and a survey invitation has been scheduled to send but has not sent yet, then if a user clicks the "Save and Mark Response as Complete" button on the data entry form, it mistakenly does not prevent the scheduled survey invitation from sending later on, even though the survey has already been completed. So the respondent will mistakenly receive the invitation to their survey that has already been completed. If the survey is completed on the survey page itself (rather than on the data entry form), then this issue does not occur.

  • Bug fix: If the designated survey email field was enabled in a project that uses surveys, then it would mistakenly allow the user to edit the email address in the Participant List of an initial survey when the email address displayed in the list originated from the designated survey email field. In this case, the email address should only be modifiable on the data entry form to which it belongs.

  • Bug fix: When adding a new field on the Online Designer, if the "Descriptive" field type had been selected in the drop-down list in the "Add New Field" popup window, after which the user saved or canceled that popup, then before leaving the page if the user clicked the "Add Field" button immediately afterward to re-open the popup window, it would mistakenly display the Required, Identifier, Custom Alignment, and Field Note sections. In this case, it should instead be hiding those sections in the popup since they do not apply to Descriptive fields. (Ticket #728)

Version 6.1.3 (released 10/17/2014)

  • Major bug fix: If using the "Export Records" API method, it sometimes would not hash the record name in the exported data set when it should if the user whose API token is being used has "De-identified" or "Remove all tagged Identifier fields" user privileges. If the user has "De-identified" rights, it would mistakenly hash the record name in all cases every time, regardless of whether or not the record ID field is an Identifier field. Also, if the user has "Remove all tagged Identifier fields" rights, it would mistakenly never hash the record name, even when the record ID field is an Identifier field. It now correctly hashes the record name if the record ID field is an Identifier field AND if the user has either "De-identified" or "Remove all tagged Identifier fields" user privileges.

  • Major bug fix: The "simultaneous users" check that prevents two different users from viewing the same record/instrument/event in the same project would not successfully stop a user from viewing the data entry form if they had been assigned to a user role, but *prior* to being assigned to the role, the user had either No Access or Read-Only user privileges for that instrument. This issue would not occur if the user possessed Edit user privileges for that instrument prior to being assigned to the role. (Ticket #723)

  • Bug fix: If a project is using the Custom Record Label, but it has been set up incorrectly in which no variable names are including in the custom record label at all, then it could cause some pages to crash (e.g., data entry page, record status dashboard) if a large amount of records exist in the project.

  • Bug fix: When viewing the Participant List in a project containing surveys, in certain situations it would mistakenly allow the user to remove a participant from the list even when the record exists. It should only let users remove it if the record does not exist yet. Also, it would mistakenly allow users to edit a participant's email address even if the email was missing and thus displayed the text "[No email listed]". In this case, it should not allow anyone to edit the email address since it is assumed to be pulling the email address from the designated survey email field.

  • Bug fix: When adding/editing a report that contains hundreds of fields, especially when the project itself contains hundreds or thousands of fields, the page may load very slowly or may not load completely at all.

  • Bug fix: Some pages in REDCap, such as certain survey pages, would appear as incorrectly formatted due to a compatibility issue specifically with Internet Explorer 10. Bug emerged due to a change in version 6.1.3 to address issues with Internet Explorer's Compatibility Mode.

  • Bug fix: When viewing the Participant List in a project containing multiple surveys while utilizing the "designated email field for survey invitations" feature, it would mistakenly not allow the user to click the checkmark icon in the "Responded?" column in order to navigate to the record on the data entry form (assuming the response is either partially completed or fully completed). This issue only occurs for the first instrument in the Participant List.

Version 6.1.2 (released 10/08/2014)

  • Major bug fix: The Survey Login feature was mistakenly being case sensitive with regard to the respondent's login credentials entered on the survey when it should instead have been case insensitive.

  • Major bug fix: If Data Access Groups are being used in a classic project (excludes longitudinal projects) when a given DAG does not contain any records yet, if a user assigned to that DAG navigates to the Add/Edit Records page, then the user will mistakenly see a list of ALL records in the project from all DAGs rather than an empty drop-down list. If they attempt to view a record in the list that is not in their DAG, they will not be able to access or view any data from it, but it could be confusing as to why records from other DAGs have their record names displayed. This bug would only cause data access issues if the record ID field for the project is an identifier field (i.e. PHI), which is always discouraged.

  • Bug fix: Some computers/networks were forcing Internet Explorer to always use Compatibility Mode when viewing REDCap, which would cause some functionality not to work properly. REDCap now disables Compatibility Mode in Internet Explorer to prevent such issues.

  • Bug fix: When saving the conditional logic in the Survey Queue for a given survey, it would mistakenly remove "<>" if it existed in the logic text. This could cause the logic not to get interpreted correctly and thus would prevent the survey from displaying in the Survey Queue when it should.

  • Bug fix: When using the REDCap::getData() method in a plugin or hook for a longitudinal project, in which the $combine_checkbox_values parameter is set to TRUE and the $return_format is *not* 'array', then for checkboxes that are unchecked that exist on instruments that are not designated for a given event, it would mistakenly return all the coded values for the checkbox (e.g. "0,1,2,3") when instead the field should have a blank value returned.

  • Bug fix: When using the REDCap::getData() method in a project-level plugin or hook, in which the method is used to pull data from other projects (using the $project_id parameter), it would mistakenly return an empty set of data from the other project unless the other project just happened to have the same record ID variable name as the original project. Note: This does not affect system-level plugins.

Version 6.1.1 (released 10/03/2014)

  • Improvement/change: The Configuration Check page in the Control Center now checks to make sure that the file upload directory is writable if using WebDAV or Amazon S3 as the storage method. In previous versions, it did not check file writability for those storage methods. (Ticket #706)

  • Improvement: When a user exports an instrument as a PDF file, it now displays the current date/time at the bottom left of each page in the PDF representing when the file was downloaded.

  • Improvement: The text boxes for Text field types are now 50% wider as displayed on data entry forms and surveys to allow for more text to be seen.

  • Major bug fix: If a data export file produced by the "Data Exports, Reports, and Stats" module (whether it be the data file or stats package syntax file) is sent to an email recipient using the Sent-It module, the file may download correctly but will not open successfully. This is due to the fact that the file was mistakenly not being decompressed during the download process. (Bug emerged in version 6.0.0.)

  • Major bug fix: When using the not_contain() function in logic, such as in a report filter, the logic would immediately fail. This would especially cause reports and custom exports to fail. (Ticket #716)

  • Major bug fix: When creating a new record in the Scheduling module in a longitudinal project, it would mistakenly allow users to add records whose record name began or ended with spaces, which causes various issues in other modules. It now trims the record name (client-side and server-side) when scheduling a new record. (Ticket #718)

  • Change: The "User Security" section at the top of the "Table-based User Management" page in the Control Center has been removed. It was originally added after version 5.8.0, which implemented a different password hashing algorithm. All users will have had their passwords upgraded by now, so it is no longer useful to display this section.

  • Bug fix: PROMIS CATs (computer adaptive tests) would not load on a survey page if the server was using a proxy for outgoing requests from the server.

  • Bug fix: In certain cases, the form name and form label of an instrument can get inadvertently lost, which either causes the instrument to become invisible and inaccessible or it causes the form label to be replace with an "[X]". It now does a better job of recovering the form name or label if it somehow gets lost.

  • Bug fix: In the user/role list displayed on the User Rights page, it would sometimes mistakenly show a user as not being suspended when in fact their account had been suspended. This would occur due to case sensitivity mismatching of their username as recorded for their REDCap user account compared to their username when it was added to the project's User Rights page.

  • Bug fix: Fixed a typo on the REDCap::allowUsers page in the Plugin/Hook Documentation, in which it mistakenly referenced the REDCap::allowProjects method in the Description box instead of REDCap::allowUsers.

  • Bug fix: In the Plugin/Hooks Documentation, the first example for the redcap_data_entry_form hook was mistakenly missing the parameters passed into the function.

  • Bug fix: When using certain non-English languages as the "Language Displayed for Global Pages" setting on the General Configuration page, it might cause a JavaScript error to occur on the Email Users page in the Control Center and would thus prevent administrators from sending emails to users on that page.

  • Bug fix: When using piping when doing the Post Pre-fill method to pre-fill survey questions (documented on the "How to pre-fill survey questions" section of the Help & FAQ page), the piping would mistakenly not work when the survey page loaded.

  • Bug fix: When adding a new field to a data collection instrument on the Online Designer when the project is in production status and in Draft Mode, if the new field is added as the first field in the instrument, it will mistakenly cause the instrument name (which is displayed on the left-hand project menu and in the Online Designer list) to get removed and thus end up as "[ ? ]" if that instrument does not exist in the project yet but only exists in Draft Mode.

  • Bug fix: If a REDCap installation contains many thousands of projects, then when a super user navigates to the "Manage All Project Tokens" tab on a project's API page, it might mistakenly not display the user table on that page.

  • Bug fix: When using the REDCap::getData plugin/hook method and nothing is passed into the $fields parameter (including NULL or an empty array), it would mistakenly output Descriptive fields in the returned data set, even though Descriptive fields cannot have any data. This would not occur if an array of fields (or a single field) was passed into the $fields parameter. It now removes any Descriptive fields from the data that is output by the method.

  • Bug fix: The Configuration Test page and main Control Center page should have been (but were not) alerting administrators if they were using an SSL connection when the REDCap Base URL value did not reflect this (because its value still began with "http:" instead of "https:"). This would cause all full URLs generated by REDCap, including links sent inside emails, to be incorrect and would mistakenly point to the non-SSL address. Now if using SSL, it will alert administrators to update the REDCap Base URL value so that it begins with "https:".

  • Major bug fix: When a respondent returns to a survey to enter their Return Code, it might take an extremely long time before it would display their survey after entering a valid Return Code.

  • Change: PROMIS assessments no longer display the REDCap copyright language at the bottom of the survey page, and they now only display the PROMIS acknowledgment text on the first page of the assessment.

  • Bug fix: When viewing the Survey Invitation Log in a project containing surveys, in the "Invitation send time" column it might mistakenly display the time that the email was scheduled to send rather than the time the email actually got sent, in which these two times might be slightly different due to various valid reasons.

  • Bug fix: If a date or date/time field is chosen as the Secondary Unique Field in a project, it would mistakenly display the value of the Secondary Unique Field in Y-M-D date format on the page even if that field had been designated to display as M-D-Y or D-M-Y format. It now displays its value according to its designated date format.

  • Bug fix: When using a Custom Record Label and/or Secondary Unique Field in a longitudinal project, it would mistakenly not display those values for a given record in the record drop-down list in the mobile web view of the project. For classic projects, however, it would correctly display the Custom Record Label and/or Secondary Unique Field in the mobile web view.

Version 6.1.0 - codename "Snickerdoodle" (released 09/16/2014)
1   2   3   4   5



The database is protected by copyright ©ininet.org 2024
send message
    Main page
user does
right amount
current list
control center
data back
database server
current form
drop-down list
participant list
processing speed
project title