Major bug fix: When using the mobile web view on an iOS device, it would mistakenly not be able to display the page at all but would instead display some CSS style text. Bug emerged in version 6.3.2.
Major bug fix: Users in a project that did not have Project Design/Setup privileges would mistakenly be able to move a project to production if they knew how to navigate to a specific, undocumented URL in their web browser. In addition, they would also be able to do this even when the Control Center setting "Allow normal users to move projects to production?" was set to No.
Version 6.3.2 (released 01/16/2015)
New feature: REDCap administrators can now transfer an API token from one user to another user within a given project. This is useful in certain situations, such as if the user possessing the token will have their access revoked from the project or from REDCap altogether, after which their token needs to be maintained by another user in the project (often because the token is already being used by a program or script and needs to be used on an ongoing basis). So if the token needs to maintained as-is in the project, an administrator can transfer the token to another user as a means of maintaining its current value without having to lose it. Whenever an API token is transferred to another user, it will automatically email both of those users to notify them of this token transfer.
New feature: In the Add/Edit Field popup on the Online Designer page, there is a new "Choose existing choices" link for multiple choice fields that will display a popup containing the options of all other multiple choice fields in the project to allow the user to quickly choose one set of options to use for a new field. This can make the process of creating fields quicker if there happen to be several fields that will have the same multiple choice options.
Improvement: When viewing a REDCap page in the Mobile Safari browser on an iOS device, drop-down menus would appear as text fields on the page, which is the default style for Mobile Safari. This could be confusing to users or participants since you cannot tell that it is a drop-down until you tap it. The style of all drop-downs in Mobile Safari has been changes so that they are now displayed with a right-aligned triangle background image to make it more clear that they are drop-downs.
Major bug fix: In longitudinal projects containing calculated fields in which a user is saving data on a survey or data entry form, the Auto-Calculation feature would mistakenly set some calculated values as blank/null if a calculated field used a cross-event calculation that utilized another calc field that itself did *not* use a cross-event calculation.
Major bug fix: If the advanced functions "isnumber" and "isinteger" were used in branching logic or a calculation for a calc field, it would mistakenly display an error on a survey or data entry form and thus not execute successfully.
Change: The Help & FAQ page was updated with minor changes.
Bug fix: If the Secondary Unique Field or Custom Record Label is enabled in a project, then they would not display correctly on a report in a classic project or in a longitudinal project that contained only one arm. Bug emerged in version 6.3.0.
Version 6.3.1 (released 01/09/2015)
Major bug fix: In certain specific situations where calculated fields are used, in which a user is importing data via Data Import Tool or API or is saving data on a survey or data entry form, the Auto-Calculation feature would mistakenly go into a very long loop (or sometimes an infinite loop) and would take many minutes to actually save all the data and finish.
Major bug fix: If a user was uploading a data dictionary with branching logic or a calculated field's equation that was malformated in a certain way, or if a user was attempting to add such logic/calculation to a field in the Online Designer, then it would mistakenly go into an infinite loop and never fully process the action. Bug emerged in version 6.3.0.
Major bug fix: When using the DDP (Dynamic Data Pull) module in a project, in which some repeating, temporal source fields (e.g. labs) have been mapped from the source system to fields in the REDCap project, when the REDCap cron job is pulling more data for that record in the background every 24 hours, it would mistakenly not pull any of the temporal data (although it would correctly pull one-time, non-temporal data). So temporal data would be fetched in real time when users are accessing it on the front-end web interface (i.e. DDP adjudication popup), but the temporal data would mistakenly not get fetched by the cron job at 24 intervals if more data appeared in the source system for that record.
Bug fix: If a user downloads an instrument from the Shared Library and then later attempts to download another instrument that is similarly named for that same project, then on certain occasions REDCap will mistakenly go into an infinite loop and will not be able to successfully add that new instrument to the project. (Ticket #771)
Change: Some outdated language on the longitudinal event grid was updated.
Bug fix: If a user was setting up the Survey Queue in a project and setting conditional logic for a given survey in which the logic contained a < operator followed immediately by a character other than a space, then it would mistakenly truncate the logic string at the < character and save it incorrectly, thus causing the Survey Queue not to display correctly.
Bug fix: The Data Import module was mistakenly returning an error message if a user attempted to import a value for a calculated field. While this was normal in older versions, it should no longer do this for version 6.3.0 and later and should instead display an allowable warning. Bug emerged in version 6.3.0.
Bug fix: On the Activity Log page in the Control Center, it was mistakenly displaying auto-calculation events in the Aggregate Counts table at the bottom of the page. It should not have been displaying those specific type of events because they are secondary events caused by a user instigating the original logged event.
Change/improvement: When using the DDP (Dynamic Data Pull) module in a project and viewing a data entry form for a given record, even if the record has no new items from the source system, it will now display a "View" link at the top of the page to allow the user to open the DDP adjudication popup to allow them to view any already-imported values or to modify the day offset value in order to fetch new data from the source system. In previous versions, the "View" link was only displayed at the top of the data entry form if there were some new items to adjudicate.
Bug fix: When using the DDP (Dynamic Data Pull) module in a project and viewing a data entry form for a given record, if data is adjudicated from the source system on that page for a YesNo or TrueFalse field, then although it will import and save the value for the field, it will not pre-select the YesNo/TrueFalse field value if the field is visible on that page. Thus if the user saves the form after importing the value, it would mistakenly reset the value back to a blank value again. (Ticket #778)
Bug fix: When viewing the Stats & Charts page for a given report, in which a filter is used in the report (with selected fields, advanced logic, or using the Additional Filters section), then if the report returns zero results, then it would mistakenly display incorrect counts for the descriptive stats for the fields on the page and would also display bar charts and scatter plots of data on the page when the charts/plots should not even be displayed.
Version 6.3.0 - codename "Ginger Snap" (released 12/18/2014)
NEW FEATURES & IMPROVEMENTS:
New feature: Auto-calculations - When performing a data import (via Data Import Tool or API), REDCap will now perform the calculations for any calculated fields that are triggered by the values being imported. For example, if you have a BMI field whose calculation is based off of a height field and a weight field, then if you perform a data import of height and weight values, it will automatically calculate the BMI for each record that is imported and also save those calculations (and thus log them too on the Logging page). Auto-calculations are now also triggered when using cross-form calculations in the case where the calculated field exists on a different instrument than the fields being entered that are used in the calculation. So while in previous versions users would have to go to the instrument where the calculated field existed and would have to click Save to store the calculation, users now no longer have to do that because the calculation is performed and saved automatically at the time when the trigger fields are initially entered or changed. So essentially, users never have to worry that calculations are not being performed or saved in certain situations. They should expect that calculations are now always being saved silently in the background.
New feature: New data quality rule to fix all incorrect values for calculated fields - New Data Quality rule (rule H) will help users find and fix all incorrect values for calculated fields in a project. If any calc fields have ended up with incorrect values (whether due to field changes in the project or due to previous data imports), users can now run rule H not only to find any incorrect calculated values, but it will additionally display a button that, when clicked, will auto-fix ALL of them for the user. This is very powerful, and we have made it as easy as the single click of a button to fix all calculations in an entire project.
New feature: Filter data quality rules by a specific record - In the Data Quality module, users can now choose to execute a data quality rule for only a specific record in the project (rather than for all records) by selecting the record from a drop-down list.
Improvement: New log() function for logarithms has now been added as a new advanced function for calculating the logarithm of a number for a specified base. It can be used in calculations, report filtering logic, data quality rule logic, etc. For details, see the table of advanced functions at the bottom of the Help & FAQ page.
Improvement/change: When a user is logging in to REDCap on a mobile device in which the page is a project URL (as opposed to logging in at the My Projects page), it now takes them to that project in the mobile web view rather than taking them to the mobile web view's My Projects page, which it did in previous versions. (The only exception for this is when a super user is logging in directly to a project's Project Modification module for viewing/approving production changes, in which case it will always take them to the desktop web view after logging in.) Additionally, when a user is on a mobile device and is viewing a project in the mobile web view, it now displays the "Desktop Site" button at the top right of the page to allow them to easily jump to the desktop web view for that project. Previous versions did not display this button.
Improvement: On the Browse Users page in the Control Center, the View Users drop-down list now contains the options "Table-based users only" and "LDAP users only" for institutions using "LDAP & Table-based" authentication to help distinguish between those two categories of users when viewing users.
Improvement: When performing the setup/mapping step for the DDP (Dynamic Data Pull) module, there is now a new preselect option for temporal fields: "Nearest value (based on timestamp)". If a temporal field has this option selected, then when displaying the source system data in the DDP Adjudication popup, it will preselect the value whose timestamp is closest (whether occurring before or after) to the REDCap date/time.
Improvement: When performing the setup/mapping step for the DDP (Dynamic Data Pull) module, the new maximum value that can be set for the Default Day Offset value is ±365 days, whereas in previous versions it was only ±30 days.
BUGS & OTHER CHANGES:
Improvement/change: When using the DDP (Dynamic Data Pull) module in a project and entering a value for the Source Identifier Field for a record on a data entry form, in which it prompts the user to save the value to reload the form, it now automatically re-opens the DDP adjudication popup after the page reloads, which is bit more convenient. Also, some of the language has been changed in the DDP Preview Fields popup for greater clarity when no DDP preview fields have been selected during the DDP setup process in the project.
Change: The form status icons that appear on the Record Status Dashboard, left-hand project menu, and longitudinal event grid now behave slightly differently for the gray status icons. The gray icons denote that no data has been entered on the data collection instrument, but due to the new auto-calculation feature in 6.3.0, calculated values can get stored on other forms even though a user has never navigated to that form. This could cause confusion if the icon is red when no one has ever entered the form. So now calc fields are excluded when determining if an icon should be gray. This allows the behavior of the colored icons to remain the same as it did in prior versions with regard to user experience and workflow.
Change: Changed the language and added a detailed explanation in the User Access section on the Create New Report page that more clearly explains how a report's user access controls work and how they are different from a user's user rights.
Change: The disclaimer text for calculated fields that was displayed on data entry forms, on the Online Designer, and on the Data Dictionary Upload page has been removed from those pages due to the introduction of newer features (e.g. the auto-calculation feature and Data Quality rule H) and is additionally due to a general ideological softening of extreme prejudice against calc fields by the REDCap development team.
Change: When new Table-based users have their account created, in which an account expiration date is set, in addition to listing the date/time of expiration in the email text, it now also specifies how many days from now that will be. This provides greater clarity of when the expiration will occur for some users.
Change: When a user receives an email letting them know that their REDCap account will expire soon, the following text has been added to the email to explain why their account will expire: "Your account has been set to expire because a REDCap administrator has chosen this date as the expiration date for your account."
Improvement/change: A "print page" button was added to the top of the User Access Dashboard page to allow users to print the page in order to review it offline.
Bug fix: Signature fields would not work correctly on a survey or data entry form for iOS versions lower than version 7.0. Signature fields now work on iOS 5 and up.
Bug fix: When using the DDP (Dynamic Data Pull) module and performing Step 2 of the Setup process, it would mistakenly not allow you to add new fields if some fields had already been mapped. This only occurred in the Safari web browser.
Bug fix: When performing the setup/mapping step for the DDP (Dynamic Data Pull) module, if a source field from the external system was mapped to several different temporal REDCap fields (e.g., labs) but those REDCap fields had different date/time fields associated with each of them, then although it would save the mappings correctly when clicking the Save button, when the user returned to the page to view the mappings again, it would mistakenly clump all those fields together, thus causing their associated date/time fields to overwrite each other and mess up their mappings. So if the user then saved the mappings a second time, it would save it incorrectly, thus causing the mappings to change unexpectedly from their initial configuration.
Bug fix: When viewing a report containing over 1000 rows, in which it displays the "displaying record" drop-down to allow paging, then in some particular cases it would mistakenly not load the desired page of the report after being selected due to a JavaScript error.
Bug fix: Users whose username contains only numbers would mistakenly not be able to be assigned to Data Access Groups.
Bug fix: When viewing a user's information on the Browse Users page in the Control Center and then clicking the "Edit user info" button, if the user being viewed already has an account expiration time defined, then it will mistakenly not display the time component correctly but will instead display it with AM/PM-formatted time. This will cause it to throw an error if a REDCap administrator attempts to modify the expiration time, and if the expiration time is not modified but the user re-saves the page, then the expiration time will not get saved correctly, which could prevent the user's account from actually expiring at the desired time.
Bug fix: When using Table-based authentication and also when the "Force users to change their password after a specified number of days" setting is enabled on the Security & Authentication page in the Control Center, if a user logs in for the first time, they get an incorrect message telling them that they need to change their password because they have not logged in to REDCap in X days, which is confusing. It no longer does this and does not force them to change their password when they log in the first time.
Bug fix: When clicking the Add Signature link or Upload Document link in order to capture a signature or upload a file on a form or survey, respectively, it would mistakenly not employ piping in the field's label when displaying it in the popup that appears.
Bug fix: When using a numerical field validation where a comma is used as the decimal character, the Add/Edit Field popup on the Online Designer would mistakenly not display the min and max text fields to allow one to enter range values for the field.
Bug fix: If a checkbox field has an option label that contains a double quote, then it would prevent that field from being displayed on the Stats & Charts page of a report and would thus cause all other charts below it not to display as well.
Bug fix: When hosting REDCap on a Mac server, it would mistakenly think that it was a Windows server when viewing the Cron Jobs page in the Control Center, in which it would thus display the cron job setup information for a Windows server rather than a Unix system. (Ticket #761)
Bug fix: When performing the setup/mapping step for the DDP (Dynamic Data Pull) module, if the Default Day Offset value was set as a floating point number instead of an integer, then it would fail to save it correctly and would often round it down to the nearest integer value after saving it.
Bug fix: For a longitudinal project containing more than one arm, in which either the Custom Record Label or Secondary Unique Field is enabled, it would mistakenly only display the Custom Record Label and/or Secondary Unique Field that belongs to the first arm when viewing a report, and if the record did not exist in the first arm but did exist in another arm, then the label would not display at all in the report. It now displays the label that belongs to the current arm for the row of data being displayed in the report. Also, in this case, the Record Status Dashboard would mistakenly display the Custom Record Label and/or Secondary Unique Field for only one of the arms (often the last arm containing data for the label) even when the record existed on multiple arms. It now displays the label for every arm for a given record on the Record Status Dashboard.
Bug fix: If a user that is not assigned to a Data Access Group is viewing the Stats & Charts page of a report where one or more Data Access Groups have been selected as a filter via Additional Filters, then although the report table would display all data correctly, the Stats & Charts page for that report would mistakenly display *all* records instead of displaying only the records from the selected DAGs. (Ticket#766)
Version 6.2.5 (released 12/16/2014)
Major bug fix: For longitudinal projects where records *do not* have data saved in the first event but *do* have data saved in one or more later events, those records - if created after upgrading to version 6.2.4 - would mistakenly not appear in the drop-down list of records on data collect instruments, thus appearing in some places as if they do not exist. Bug emerged in version 6.2.4.
Version 6.2.4 (released 12/05/2014)
Major bug fix: When a user is viewing a partially completed or fully completed survey response on a data entry form, it would mistakenly display the Save buttons at the top right of the page even if the user did not have "Edit survey response" user privileges. This would not allow the user to modify any responses on the form because all the fields would remain locked and read-only, but if they clicked one of those Save buttons, it would inadvertently cause some of the data values on that page to get erased.
Medium security vulnerability: It is possible that a malicious user might be able to inject a specially crafted string of text on one specific page in REDCap to exploit a Cross-Site Scripting vulnerability.
Change/improvement: Small improvements to speed up the sending of survey invitations when sending large batches (i.e., thousands) of invitations all near the same time.
Change/improvement: On the Configuration Test page and on the Install module, it now displays a red warning if the InnoDB table engine is not enabled on the MySQL database server.
Bug fix: When uploading a file for a File Upload field on a data entry form on an iOS device, it would not upload successfully but instead return an error message. This would not occur on survey pages but only on forms.
Bug fix: In some cases, it will not allow a user to save a signature for a Signature field when using Internet Explorer 8.
Bug fix: When using the Real Time Execution aspect of a custom Data Quality rule in a longitudinal project, then when a rule violation occurs on a data entry form, in which one of the fields in the rule's logic occurs on that instrument but on a different event, it would mistakenly make the data value into a clickable link in the violation popup. And when that link is then clicked, it puts focus on that field on the current instrument, which can be confusing because it really refers to a different event. It now only makes the data value into a clickable link in the violation popup if the field exists on that instrument on that same event. (Ticket #754)
Version 6.2.3 (released 11/21/2014)
Major bug fix: When using the datediff() function inside branching logic, calc fields, Data Quality rules, Automated Survey Invitations, etc., it would not work correctly if "TODAY" was used in capitalized form inside quotes (single or double quotes) for either of the two date parameters in the function. It would work, however, if not surrounded by quotes (in either upper case or lower case) and also if lower case surrounded by quotes.
Major bug fix: When using the datediff() function inside branching logic, calc fields, Data Quality rules, Automated Survey Invitations, etc., it would not work correctly if "today" (in upper or lower case, either surrounded by quotes or not) was used as the second date parameter when the first date parameter in the function is today's date as a literal value (e.g., "2014-11-18").
Bug fix: For super users, the link "REDCap Mobile App" mistakenly appears on the left-hand menu of a project. This link should not appear yet because that feature has not yet been released. (Ticket #747)
Bug fix: On the "Stats & Charts" page, the descriptive stats for "counts/frequency" would mistakenly display as "0, 0.0%" for any choices of a multiple choice field where the choice's coded value was non-numeric. (Ticket #746)
Bug fix: When importing XML data in an API data import request when the XML data is not formatted correctly, it could sometimes throw a fatal PHP error, thus mistakenly returning a HTTP 500 or 200 error rather than a 400 error with an appropriate error message.
Bug fix: When creating or editing a report that contains an "SQL" type field as a filter in the report, it would mistakenly not display a drop-down of the SQL field's choices after choosing it as a filter but instead would just display a text box for entering the filter value. It now displays a drop-down with the field's choices.
Bug fix: When creating or editing a report in Internet Explorer 8 or 9, if the user adds a couple fields in Step 2 or selects an instrument in the "Add all fields from selected instrument" drop-down, then it would often mistakenly append one extra row to the table of fields in Step 2. (Ticket #750)
Bug fix: When a user in a project has no access to any of the data collection instruments, it would still mistakenly display the "Add/Edit Records" link on the left-hand menu, and whenever they clicked that link, it would mistakenly take them outside the project to REDCap's Home page. It now no longer displays that link on the left-hand menu if they do not have access to any instruments.
Bug fix: If a user in a project has no access to the first data collection instrument, then it should display "View/Edit Records" for the link text on the left-hand menu, but instead it mistakenly displays the link text as "Add/Edit Records" if the user has "Record Create" rights but has no rights to the first instrument, which is the only place a record can be created in the web interface.
