Upgrade 8.11.0 LTS Detailed Features Changes list New

Version 8.11.0 - (released 1/22/2019)

NEW FEATURES, BUG FIXES, & OTHER CHANGES:

• New feature: Microsoft Azure Quick Start – Method for quickly deploying a full, production-ready REDCap server environment on Microsoft Azure Cloud Platform. This includes a completely automated way for deploying the server infrastructure as well as a fully automated installation of REDCap. For details, see the top of the pagehttps://projectredcap.org/software/requirements/ (Note: The REDCap “Easy Upgrade” feature does not yet work with Azure but is expected to in a later REDCap version).

• New feature: The "Survey Link Lookup" external module was integrated into REDCap

  • This feature allows administrators to take a survey URL and find and navigate to the corresponding project, survey, record and data entry form. The Survey Link Lookup page is located under the “Projects” section on the left-hand menu in the Control Center.

  • If this external module was already enabled on the REDCap installation, it will automatically be disabled during the upgrade process to prevent any possible conflicts.

• New feature: The "REDCaptcha" external module was integrated into REDCap

  • This feature allows users to utilize the Google reCAPTCHA functionality to help protect public surveys from abuse from “bots”, which are automated software programs that might enter trash data into surveys. The feature must first be enabled at the system level on the Modules/Services Configuration page in the Control Center since it requires an administrator generate a new Google API pair of keys that will be used for this functionality. Once the site key and secret key are set, users will then be able to choose to enable the Google reCAPTCHA functionality on the Public Survey page in their project, after which the public survey will display the reCAPTCHA checkbox and “I’m not a robot” text on a survey page prior to allowing the participant to view the public survey. This feature is not employed on any private survey links because those are unique to a record and thus would never be made publicly available like a public survey link would.

  • Note: A survey participant will never have to pass the reCAPTCHA test more than once per day on a given device/computer.

  • Additional note: If this external module was already enabled on the REDCap installation, it will NOT automatically be disabled during the upgrade process. Thus you may consider disabling the module after the upgrade if you wish the utilize this new integrated feature.

• New feature: The "Sticky Matrix Header" external module was integrated into REDCap. This feature will cause matrix headers to float and stick to the top of a page on either a survey or data entry form so that the matrix headers are always visible, which is helpful for matrices with many rows. If this external module was already enabled on the REDCap installation, it will automatically be disabled during the upgrade process to prevent any possible conflicts.

• New feature: The "Codebook Concertina" external module was integrated into REDCap. This feature will display Expand and Collapse buttons for each instrument listed on the Codebook page in a project. If this external module was already enabled on the REDCap installation, it will automatically be disabled during the upgrade process to prevent any possible conflicts.

• Minor security fix: A Cross-Site Scripting (XSS) vulnerability was discovered on certain pages, in which a malicious user could potentially exploit it by manipulating the query string of an HTTP request.

• Improvement: When enabling an instrument as a survey or editing an existing survey's survey settings, it now displays a "Save Changes" button at the top of the page (next to the Cancel button) so that the user does not necessarily have to scroll all the way to the bottom to submit the page.

• Change: PHP 5.5 is now the minimum required PHP version. In previous versions, the minimum required PHP version was PHP 5.3.

• Change/improvement: When viewing a survey response on a data entry form that had been completed using the E-consent Framework, users with Record Locking privileges will now be able to Lock and E-sign the instrument. Previously in all versions of REDCap version 8.10.X, the entire instrument was read-only, including the Locking and E-signature options. (Ticket #54874)

• Improvement: If a URL is included in a message posted on REDCap Messenger (including those sent via General Notifications from an administrator), the URL will be displayed as a clickable link to the user in the Messenger panel.

• Change/improvement: The Custom Record Label and Secondary Unique Field values are now displayed with the record name in the table on the "PDF Survey Archive" tab in the File Repository if the "PDF Auto-Archiver" is enabled for one or more surveys in a project. In previous versions, it did not display them next to the record name.

• Change: For projects in production, the settings on the Record Locking Customization page can now be edited by any user that has "Record Locking Customization" privileges in the project. In previous versions, only REDCap administrators could modify this page's settings while in production. This change will alleviate the burden of administrators for many production projects needing to make changes on this page.

• Bug fix: In server environments with PHP error reporting enabled, it would display a deprecation notice regarding the constructor of several PHP classes. (Ticket #55557)

• Bug fix: When viewing an individual user on the Browse Users page in the Control Center, if the user is a Table-based authentication user and their secondary or tertiary email address has not yet been verified, then it would mistakenly not display the buttons to auto-verify the address or re-send the verification email to the user. This only occurs if the user is a Table-based user.

• Bug fix: When a form or survey is submitted, in which there do not exist any fields on the instrument that are used in a calculated field anywhere in the project, then it would mistakenly trigger the calculation of all calc fields in the project. It should instead only trigger calculations if a field being submitted is used in a calculation. (Ticket #55192)

• Bug fix: The "Export Survey Participants" API method would mistakenly not include some participants in the resulting API response if those participants had not first been viewed by a user either on the Participant List page or on the data entry form for the survey instrument that was passed as a parameter in the API request. Once a user had viewed the data entry form or Participant List for that instrument, the participants would then appear in the API export. (Ticket #55517)

• Bug fix: When creating a project and selecting the option to upload a REDCap Project XML file, if the user fails to upload an XML file and then clicks the "Create Project" button, it would mistakenly create an empty project. It should instead give a warning to the user to upload an XML file and prevent the user from submitting the page. (Ticket #55731)

• Bug fix: When a user makes a request to an administrator that a project be copied, it would mistakenly not check off some of the checkboxes on the Copy Project page when the administrator loads the page via the link in the email or via the To-Do List. This includes the following options: All report folders, All data quality rules, All project bookmarks, and All custom record status dashboards. (Ticket #55751)

• Bug fix: When attempting to rename a record to "0" on the Record Home Page, it would fail and return an error message to a user. (Ticket #55723)

• Bug fix: When using the Smart Variables form-link, form-url, survey-link, or survey-url to create links/URLs either to or from a repeating instrument or repeating event, it might mistakenly add the instance number of the current context to the URL when instead it should evaluate whether or not the instance number makes sense to be added to the target URL. (Ticket #54776)

• Bug fix: When using Twilio telephony services for surveys, U.S. phone numbers having the area code "463" would mistakenly not work for SMS or voice calls unless the number has a "1" prepended to it. (Ticket #55668)

• Change: The System Statistics page in the Control Center would load very slowly for large installations, especially if they had DDP Custom or DDP on FHIR enabled. The page has been reconfigured to fetch all DDP-related stats asynchronously.

• Bug fix: When adding/editing/deleting a Report Folder or assigning/unassigning a report to a Report Folder and then closing and re-opening the Report Folder popup, the user would mistakenly no longer be able to perform any actions inside that popup (as if its elements were locked). (Ticket #55878)

• Bug fix: When a user enters an incorrect password on the login page, it might mistakenly cause some of the custom login text (if any) to become disproportionally enlarged. (Ticket #55945)

• Bug fix: When creating/editing a record on a data entry form, in which the record name contains a forward slash or back slash, it may cause a Data Quality rule with Real Time Execution not to get triggered correctly or cause the Required Field popup alert not to display correctly. (Ticket #56093)

• Bug fix: If a participant partially completes a survey using the "Save & Return Later" feature, in which there is no email address associated with that participant (either via the participant list or via the designated survey email invitation field), then the page that gets displayed immediately after clicking the "Save & Return Later" button might mistakenly display the text "You have just been sent an email containing a link for continuing the survey" for a moment and then suddenly disappear, which could be confusing.

• Bug fix: When inline images are used for Descriptive fields on a survey or form, then if the user is viewing the page on a mobile device and the image's native width is smaller than the width of the page, it would mistakenly not resize it correctly and would make it too small on the page. It now makes the image wider on the page for better viewing of it.

• Bug fix: When printing a page in the Control Center, the left-hand menu would mistakenly not be removed from the print-out when using Firefox. (Ticket #56340)

• Bug fix: The "Announcement text to display at top of Home page and My Projects page" would mistakenly not get displayed at the top on the REDCap Home Page if the "Additionally display text on login page?" option is set to "No". (Ticket #56618)

• Bug fix: If the biomedical ontology auto-suggest functionality is disabled as the system level, it would mistakenly prevent users on the Online Designer from setting a min or max limit for a Text field in the "Add Field"/"Edit Field" popup. (Ticket #56499)

• Bug fix: When entering a number- or integer-validated text field on a form or survey on an Android device, it would mistakenly open the full keyboard when typing in the field rather than displaying a more appropriate number-centric keyboard. (Ticket #56447)

• Bug fix: When entering a number-validated text field on a form or survey on an iOS device, it would mistakenly open the full keyboard when typing in the field rather than displaying a more appropriate number-centric keyboard.

• Bug fix: "event_id" was mistakenly not listed as a reserved field name to prevent users from using it as a field's variable name. (Ticket #56627)

• Bug fix: When an administrator is approving a "Move project to production" request on the To-Do List page, the To-Do List popup would mistakenly not automatically close after the request was approved or if the admin clicked Cancel to close the request. (Ticket #56457)

• Bug fix: When using the @MAXCHECKED action tag for a checkbox field, if a user clicked on the checkbox’s label (rather than on the checkbox itself), it would appear to keep the checkbox unchecked if the @MAXCHECKED limit has been reached, but it would mistakenly save the checkbox as checked. (Ticket #56658)

• Bug fix: For specific screen widths, the nav items at the top of the page on the Home page, My Projects page, etc. would mistakenly not be visible.

• Bug fix: When performing a data import in projects with repeating instruments or repeating events, the "redcap_repeat_instance" field could mistakenly be imported with a value of "0", which should never be allowed because it must always be an integer larger than "0". (Ticket #28842)

• Bug fix: If a required field is changed to be a Descriptive field, it would still mistakenly display the "must provide value" text below the Descriptive field's label on a survey page or data entry form. (Ticket #56719)

• Bug fix: After selecting the "Export Reports" API method in the API Playground, the "Report ID" drop-down list would mistakenly not get rendered correctly, thus preventing users from utilizing it on that page. (Ticket #56707)

• Bug fix: When using the survey-link or survey-url Smart Variable in the email message for an Automated Survey Invitation, in which the instrument name is appended to the Smart Variable (e.g. [survey-link:survey_2]), then if the appended instrument name is different from the survey instrument for the current ASI, it would mistakenly replace the Smart Variable with the link to the current ASI survey rather than with the explictly specified one. (Ticket #55400)

• Bug fix: When using the first-event-name or last-event-name Smart Variable in branching logic or in a calculated field, in certain cases it might not get interpreted correctly, thus mistakenly resulting in a branching logic error message on a survey page or data entry form. (Ticket #56583)

• Bug fix: When setting the conditional logic for an Automated Survey Invitation in a longitudinal project, if any fields are prepended with the Smart Variable [event-name], it would cause the ASI not to send the invitation if step 2 had the "Ensure logic is still true before sending invitation?" option selected while Step 3 was set to "Send immediately". (Ticket #55919)

• Bug fix: When setting the conditional logic for an Automated Survey Invitation in a longitudinal project, if any fields are prepended with the Smart Variable [event-name] and the user selected a record from the "Test logic with a record" drop-down, it would mistakenly return "False" even when the condition is actually True.

• Bug fix: When setting the branching logic for a field in the "Add/Edit Branching Logic" popup on the Online Designer, if a user selected a record from the "Test logic with a record" drop-down, it would mistakenly return "False" even when the condition is actually True. (Ticket #56623)

• Bug fix: When a repeating instrument is being used as a survey and is being displayed in the Survey Queue, then it may mistakenly display the text "All surveys in your queue have been completed" on the Survey Queue if only 6 surveys have been completed in the queue (including all instances of the repeating survey), which could be confusing to respondents who might want to keep taking the repeating survey. Since a repeating survey is by definition open-ended and can be taken over and over again without end, the Survey Queue should never state "All surveys in your queue have been completed" if the queue contains at least one repeating survey. (Ticket #56540)

Version 8.10.1 - (released 12/20/2018)

BUG FIXES & OTHER CHANGES:

• Improvement: New options added to Secondary Unique Field functionality - In the "Additional Customizations" popup on the Project Setup page, users may now choose to optionally display the Secondary Unique Field's value in conjunction to displaying a record name on various project pages (in previous versions it was always displayed regardless). If left unchecked, the uniqueness of the value will still be checked during data entry or import, but the Secondary Unique Field's value will not be displayed next to the record name anywhere (e.g., in record lists, record status dashboards, reports). A second option has also been added that dictates whether or not the field label of the Secondary Unique Field will be displayed next to the value (if the value is set to be displayed next to a record name).

• Improvement: The External Modules Framework now has a new "Update All" button in the Control Center to allow administrators to easily upgrade all their installed modules to the latest version of each module with a single button click.

• Change/improvement: The "Help & FAQ" page was updated with new content.

• Change/improvement: Super API Tokens can now be used for the "Export REDCap Version" API method. In previous versions, only project-level API tokens could be used for this method. This will allow users to be able to obtain the REDCap version number outside the context of a project.

• Change: Dashes/hyphens can now be used as the raw coded value for multiple choice fields.

• Bug fix: When clicking the "Close Survey" button after completing a survey, in certain cases REDCap will not be able to close the tab, and certain browsers might mistakenly redirect the user to the page where survey access codes are typically entered. (Ticket #54305)

• Bug fix: The "Test URL" buttons have been removed from the "DDP on FHIR" page in the Control Center because they did not work most of the time, thus giving administrators the impression that the URL entered was incorrect.

• Bug fix: When accessing REDCap using DDP on FHIR while in an EHR-embedded window, if the session ended and the user logged back in, it would mistakenly not remember that the user is inside the embedded window and would thus not hide all appropriate elements from the user interface that it should.

• Bug fix: For DDP on FHIR, the coded multiple choice options for sex, race, and ethnicity were not complete and, in some cases, incorrect for certain EHR configurations. During the upgrade process, these choice options for existing DDP on FHIR projects will have both their data and metadata translated into the new options. The field sex will now have options M, F, and UNK, while ethnicity and race will be replaced by a long list of LOINC codes to represent them properly.

• Change: The "email" field was removed from the "DDP on FHIR" field mappings list due to potential privacy issues related to the possibility of users obtaining patient email addresses.

• Bug fix: When the system is performing the back-end process of caching a record list in a project, if a record name contained a special character, it might cause the record list caching process to silently fail. This would go unnoticed, with the exception of viewing a specific Data Access Group's records, in which it would mistakenly display all records in the project rather than just the records assigned to that DAG.

• Bug fix: When an administrator is viewing the "API Tokens" page in the Control Center or the "Manage All Project Tokens" tab on a project's API page, the "Last Used" column for a given user might mistakenly display "Never" instead of the last time the user made an API request for the project. This appears to occur due to a case sensitivity issue with the username, in which the case of the user seen on the Browse Users page in the Control center does not exactly match the case of the username with which the user logged in or with which the user is listed on the project's User Rights page. (Ticket #54748)

• Bug fix: The auto-logout warning displayed to the user after a period of inactivity on a page would mistakenly display the wrong text after their session has officially expired. Once expired, it would mistakenly say "You will be automatically logged out of REDCap in 30 SECONDS due to inactivity..." when instead it should say "Due to inactivity, your REDCap session has expired...". It was displaying the 30-second warning twice. (Ticket #54746)

• Bug fix: When using the "Preview" and "Test email" functionality when composing a survey invitation in a multi-arm project, if any fields are being piped into the email, in which the field being piped is prepended with the unique event name of an event from an arm other than specifically Arm 1, then it mistakenly would not replace the field with the text "PIPED DATA" as expected but would instead replace it with "______". (Ticket #54559)

• Bug fix: When creating a new record in a non-longitudinal/classic project that only contains one data collection instrument, if the user clicks the Cancel button on the data entry form before saving/creating the record, it would mistakenly just reload that form rather than redirecting the user back to the "Add/Edit Records" page. (Ticket #54752)

• Bug fix: When calling the API Method "Export Project XML", it might mistakenly not include all files from File Upload and Signature fields even though the exportFiles parameter had been set to TRUE (assuming that returnMetadataOnly=FALSE). (Ticket #54301)

• Bug fix: When calling the API Method "Importing Repeating Instruments and Events" for a classic/non-longitudinal project, it would mistakenly return an error stating that the event name was not included in the request. The event name is actually not required when using this method for classic/non-longitudinal projects.

• Change: General updates and fixes for the External Modules Framework.

• Bug fix: When viewing a record on a data entry form in a project that contains one or more repeating instruments, it would mistakenly only display the number of repeating instances of a form on the left-hand instrument menu if the user was currently viewing any form that had been set as a repeating instrument. It should always display the number of repeating instances next to each repeating instrument on the left-hand menu for a given record. (Ticket #54846)

• Bug fix: When viewing a record on a data entry form in a project that contains one or more repeating instruments, for all repeating instruments displayed on the left-hand instrument menu, it would mistakenly display the form status stack icon representing the status color of the first instance of the repeating instrument rather than displaying an icon representing all the instances (e.g., red stack icon representing all instances having "complete" status, blue stack icon representing mixed status types). This excludes the icon displayed for the currently selected form/instance, which was correctly displaying the form status icon of the currently viewed repeating instance. (Ticket #54846)

• Bug fix: When using the data search feature on the "Add/Edit Records" page in a project, in which no results are returned from a given search, in some cases the "Searching..." text might mistakenly still be displayed afterward (instead of the text being hidden), thus incorrectly implying that the search has not yet finished. This could be confusing and mislead the user. (Ticket #54818)

• Bug fix: When using an SQL field that contains a comma in the results for the data values that are returned from the SQL query, after selecting and saving an option with a data value that contains a comma, it will save the value correctly but in certain cases may mistakenly cause the value to not get pre-selected when a user returns later to the form, which could cause a blank value to mistakenly overwrite the saved value unbeknownst to the user if the form is saved again. (Ticket #54988)

• Bug fix: If a project's metadata is exported via the Project XML file, in which a multiple choice field contains an HTML break tag (<br>) in its choice option label, then if a new project is created from the XML file, it might mistakenly add extra choices to that field if any text exists after the HTML break tag for a given choice. (Ticket #55122)

• Bug fix: The "record" column in the table on the Survey Invitation Log page would mistakenly not wrap the record name and thus would truncate longer record names displayed in that column.

Version 8.10.0 - (released 12/6/2018)

BUG FIXES & OTHER CHANGES:

• New API method: “Import Repeating Instruments and Events” – Allows users to import a list of the repeated instruments and repeating events for a project as a means of setting which instruments and events should be repeatable.

• New feature: Many project components added to the Project XML file – When downloading the Project XML of metadata or metadata+data on the Project Setup->Other Functionality page, it now provides checkboxes to allow users to incorporate the project components listed below in the XML file. This means that all these things will be easily transferable now when exporting/importing the Project XML to create a new project on the same REDCap server or on a different REDCap server. Note: The server on which a project is being created using a Project XML file must also be on REDCap 8.10.0 or higher in order for these components to be added, otherwise it will simply ignore these components when creating the new project.

  • Data Access Groups (including DAG assignments for records if data is included in the XML file)

  • Data Quality Rules

  • User Roles

  • Surveys and survey settings (including a survey logo, if used)

  • Automated Survey Invitations

  • Survey Queue

  • Reports

  • Report Folders

  • Record Status Dashboards

  • DDP Field Mappings (for DDP Custom and DDP on FHIR) – administrator must still enable DDP in the project manually

• Change: Survey responses that were completed using the e-Consent Framework will no longer be editable (this includes no editing on data entry forms, surveys, Data Import Tool, API, and Mobile App). In previous versions, completed e-consent surveys were editable.

• Bug fix: After adding fields to a report via the "Quick Add" dialog popup on the "Data Exports, Reports, and Stats" page, those new fields would mistakenly not be draggable afterward if the user wishes to move a field to another position in the report.

• Bug fix: For certain server configurations related to PHP’s decoding of HTML entities, the Survey Settings page might not be able to properly store or display the survey instructions text or the survey completion text if they contain certain non-Latin characters.

• Bug fix: Users would mistakenly be allowed to use the @DEFAULT action tag for Signature fields and File Upload fields. This can cause synchronicity issues of a single file being associated with multiple fields, and thus should not be allowed. It will now ignore the @DEFAULT action tag if used for such fields.

• Bug fix: When viewing the Draft Mode production changes page in a project, if the project had been initialized in the REDCap Mobile App, then it would mistakenly give the warning "Please note that they *may* be affected by these changes and may not be able to successfully imported their data from the app afterward..." even though no current users have Mobile App user privileges anymore. It should only be displaying the warning if at least one person in the project still has Mobile App privileges and has initialized the project in the app at some point in the past.

• Bug fix: When exporting data via the "Export Records" API method with type="eav" and providing Filter Logic as a parameter in the API request in which no records should be returned based on that filter logic, it would mistakenly return all records instead.

• Change: When granting a user access to a project via the User Rights page, in which the "notify user via email" checkbox is checked, it now includes a link directly to the project in the resulting email to the user, whereas previous versions only included a link to the main REDCap home page.

Version 8.9.3 - (released 11/28/2018)

BUG FIXES & OTHER CHANGES:

• New feature: AWS Quick Start – Method for quickly deploying a full, production-ready REDCap server environment on AWS (Amazon Web Services) CloudFormation. This includes a completely automated way for deploying the server infrastructure as well as a fully automated installation of REDCap, including the ability to utilize the REDCap “Easy Upgrade” feature. For details, see the top of the page https://projectredcap.org/software/requirements/

• New features relating to Data Privacy (e.g., GDPR) – The new settings listed below are available on the “Edit a Project’s Settings” page for a given project. Thus these must be enabled by a REDCap administrator on a per-project basis

  • (optional) Delete a record's logging activity when deleting the record - If enabled, this will delete all the data values and actions logged for the given record being deleted as seen on the Project Logging page. Note: For multi-arm longitudinal projects, this feature will delete the record's logging for the given record only in the current arm. This feature can be used to aid in compliance with GDPR or similar regulations that require 'right to erasure'.

  • (optional) Auto-delete all Data Export Files in the File Repository that were created more than X days ago – To enable this setting, an administrator may set a value from 1 to 999 to set the number of days after which all Data Export files will get automatically deleted from the project’s File Repository. This feature can be used to aid in compliance with GDPR or similar regulations that require 'right to erasure'. NOTE: This will only delete files under the Data Export Files tab. No other types of files in the File Repository will be deleted.

  • (optional) Custom footer text for survey pages - Custom text may be provided (including HTML-formatted text) that will be displayed either via a modal dialog or inline at the bottom of all survey pages in the project. This could potentially be used for display a data privacy statement or other similar things that should be displayed on the same page where data is collected. Note: This is only display on survey pages.

• Change/improvement: When composing a survey invitation on the Participants List page or via Survey Options on a data entry form, the "From"/sender drop-down list now displays all the email addresses (primary, secondary, and tertiary) of all users in the project, which is how the setup dialog for Automated Survey Invitations has always behaved. In previous versions, these two places would only allow the user to choose from the current user's email addresses as the "From"/sender address. This provides more flexibility, and establishes greater consistency between all the interfaces for scheduling survey invitations.

• Major bug fix: If a slider field on a data entry form has a value set, and then the user clicks the balloon icon next to any field to open the Field Comment Log popup, it would mistakenly set the slider value to 50, sometimes unbeknownst to the user. This does not occur on survey pages but only data entry forms. (Ticket #53371)

• Improvement: If a REDCap cron job fails to complete (often due to a fatal PHP error), it will now send an email to the REDCap Administrator (using the email address listed on the General Configuration page in the Control Center) to inform them of this error. The email will note which cron job failed and when, as well as the details of the PHP error itself. This should help some folks troubleshoot issues if this ever occurs. (Ticket #19260)

• Bug fix: If a user is viewing a project's Record Status Dashboard in which some records has been assigned to Data Access Groups, then under certain rare conditions (e.g., users bookmarking a link to the RSD after a DAG has been deleted in the project) users might not see all the records on the RSD anymore, which could be confusing. (Ticket #53335)

Version 8.9.2 - (released 11/16/2018)

BUG FIXES & OTHER CHANGES:

• Improvement: A new search utility was added to the top of the “Help & FAQ” page to make finding keywords easier on the page. It allows for multiple word matches and also “exact phrase” matching. When performing the search, all matching questions/answers will be displayed on the page with the keywords being highlighted while non-matching questions/answers will be hidden on the page.

• Improvement: The DDP field mapping page (for both DDP Custom and DDP on FHIR) now has a CSV import/export capability that allows users to easily import an existing DDP mapping rather than having to set the field mapping manually via point-and-click. This will save users a lot of time for those who wish to test the same mapping in multiple projects and/or on multiple REDCap installations.

• Improvement: A new "Filter by event" option was added to the Logging page: "Record deleted (only)". This allows users to display only the logged events in which a record was deleted in the project.

• Bug fix: Certain web browsers (e.g., Chrome) would mistakenly be allowed to pre-fill Notes fields on a survey page or data entry form, which might also cause other fields on the page (such as Text fields or Radio button fields) to have values inserted into them as well.

• Bug fix: Under certain conditions when a field on a survey/form is using the @DEFAULT action tag, and the survey/form has already been saved at least once (i.e., does not have gray form status icon), it might mistakenly display the red bar on the right side of the field as if the value has changed even though it has not.

• Change: Upgrading the Font Awesome library to version 5.5

• Change: More debugging information was added to DDP on FHIR’s adjudication popup to provide more information to REDCap administrators in the event that a FHIR access token fails to pull data from the EHR.

• Bug fix: When downloading certain PROMIS Adaptive or Auto-Scoring instruments from the REDCap Shared Library, viewing a completed survey response on its data entry form might mistakenly display a popup error due to malformed branching logic, specifically for the T-Score field.

• Bug fix: If a user has "De-Identified" or "Remove all tagged Identifier fields" privileges and then exports a PDF of a form with saved data, then any multiple choice fields that are tagged as an Identifier field would still have all their choices displayed, although it would not display which choice was selected, which is confusing because it appears as if the field has a blank value rather than having its value redacted due to user privileges. In this situation, it now no longer displays the field choices but instead says "[*DATA REMOVED*] so that the user understands that the saved value was removed from the PDF.

• Change: Added a small note on the DDP mapping page (for both DDP Custom and DDP on FHIR) that the MRN field cannot exist on a repeating instrument/event. This message is only displayed when repeating instruments/events exist in the project.

• Change: Data Quality rules A and B have always ignored checkbox fields. But since a checkbox field can be set as "required", in which it produces an error message if no checkbox option is checked, then DQ rule A and B appear to be inconsistent with regard to whether a checkbox field can truly be empty/blank. To make these consistent when interpreting the missingness of checkbox fields, DQ rules A and B will no longer ignore checkboxes but will return discrepancies for a checkbox if it has no options checked. (Ticket #53120)

• Bug fix: The FHIR scope "patient/Patient.read" was missing when "DDP on FHIR" makes calls to the EHR. This caused "DDP on FHIR" not to function for some EHRs, such as Cerner. (Ticket #53285)

• Bug fix: When using "DDP Custom" or "DDP on FHIR" in which a value already exists in REDCap for a mapped DDP field but a blank value exists (i.e., is missing) for the field in the EHR/source system, it would mistakenly prompt the user to overwrite the existing value with the blank/missing value. Missing values from the EHR/source system should instead just be ignored. (Ticket #53258)

• Bug fix: When exporting the PDF of saved data (all records) on the Other Export Options tab on the "Data Exports, Reports, and Stats", if any data is being piped into a field note, field label, etc., it would mistakenly pipe the values from the first record into the text of all the subsequent records in the PDF.

• Bug fix: Certain popup alert boxes would mistakenly not get displayed in the proper place on the page. This includes the "Value removed!" alert for matrix ranking, the "Cannot select choice!" alert when using @MAXCHECKED on a checkbox field, and all field auto-suggest boxes that are displayed when typing into a text box for ASI conditional logic, Data Quality rule logic, advanced filters for reports, etc.

Version 8.9.1 - (released 11/9/2018)

BUG FIXES & OTHER CHANGES:

• Improvement: When copying a project, a new checkbox has been added to the Copy Project page to copy "all report folders". In the previous version, it would always copy all reports and report folders if the "all reports" option was checked, but now it allows reports to be copied without copying report folders, if need be.

• Major bug fix: Only for certain versions of Internet Explorer, if a user with lock/unlock privileges enters a data entry form that is already locked, then clicks the Unlock button at the bottom of the form, enters some data, and then clicks the Lock checkbox to lock the form again, it would submit the form immediately after checking the Lock checkbox, thus locking the form again, but it would mistakenly not save any of the data that had been entered on the form prior to being locked again.

• Change: Users that do not have "Project Design and Setup" privileges will no longer be able to navigate to or view the Project Setup page in a given project. Since such users cannot effectively perform any actions on the Project Setup page (i.e., everything on the page is disabled), it does not make much sense for them to be able to access it at all. (Ticket #52327)

• Bug fix: When downloading multiple Adaptive or Auto-Scoring instruments from the REDCap Shared Library into the same project, the T-Score field and Std Error field would conflict and thus cause those fields on the subsequent instruments to be renamed, in which it would append random alphanumeric characters to the variable names. This would make it difficult to have the same variable names consistently if all the same instruments were downloaded in different projects.

• Bug fix: If a user enters a value for a datetime field on a form or survey and then immediately removes the value, they would mistakenly be presented with a validation error message, which should not occur. This could cause the user to be stuck in an infinite loop on the page, in which the prompt keeps appearing, thus causing the user to have to reload the page and possibly lose any data entered. (Ticket #52024)

• Bug fix: If using the Data Resolution Workflow in a project, and a user views an open query, it would mistakenly display data values for all fields in the query, even if the user has "No Access" user privileges to that field's data entry form. In this case, it now redacts the data value and instead displays a message stating that the field's value cannot be displayed because the user does not have view access. (Ticket #49956)

• Bug fix: If the REDCap installation has the "Survey Base URL" set on the "General Configuration" page in the Control Center, then if a survey participant is viewing a Survey Queue for a record and then clicks the "Begin Survey" button for a given survey, it would mistakenly send the participant to the the wrong URL, in which it would be using the default "REDCap Base URL" instead of the "Survey Base URL". (Ticket #52502)

• Bug fix: If viewing the Record Status Dashboard in a project where only one arm exists, but the arm is not arm "1" but another number, then clicking the record name link in the dashboard table will mistakenly take the user to the first arm, where the record does not exist. (Ticket #52575)

• Bug fix: If a multi-arm longitudinal project has surveys using Automated Survey Invitations on multiple arms, in which at least one of the ASI's condition logic references a field/event on another arm, then if that ASI condition becomes true for a given record, it would mistakenly schedule the survey invitation even if the record does not exist on that arm. The record must exist on a given arm before a survey invitation can be scheduled for that arm for that record. (Ticket #52174)

• Bug fix: On the Control Center's System Statistics page, the "Data values pulled from source system via DDP" count for both DDP Custom and DDP on FHIR would mistakenly inflate the true count. This was caused by mistakenly counting temporal values multiple times in longitudinal projects or in projects with repeating instruments/events if the same value was imported into multiple events/instances for a given record. This often depends on the window of time (i.e., day offset) being used, in which a larger day offset value would pull in more duplicate values.

• Change: The alert that is displayed on a survey page or data entry form that notifies the user that an unvalidated text field begins or ends with extra spaces has been disabled so that it no longer notifies users when this occurs. This is due to reports of general annoyance by several users at the feature. This feature may possibly be re-added in the future and modified to be more user friendly, but for now it has been disabled for all projects indefinitely.

• Bug fix: When using "DDP on FHIR" in a project that does not have any demographics fields mapped on the DDP Field Mapping page, then if a patient is launched inside the REDCap window from within the EHR user interface, and the user chooses to add the patient to a project, then it would return a strange JSON-encoded message and would mistakenly take the user to the wrong page if they clicked "View patient in project" immediately after creating the record.

• Bug fix: When using "DDP on FHIR" with the setting "Convert source system timestamps from GMT to local server time?" set to "Yes" on the "DDP on FHIR" setup page in the Control Center, it might sometimes mistakenly not pull in some temporal data (e.g., labs, vitals) when the data value's date of service is close to the edge of the window of time in which REDCap is querying from the EHR. For example, if a lab field's associated date field has a value of 2018-11-06, and the DDP Adjudication window has a +-3 day offset value set, which should search for all values from 2018-11-03 to 2018-11-09 (including those days), then some values saved on 2018-11-03 or on 2018-11-09 might not get returned from the EHR. This bug is the result of the data being stored in GMT/UTC time in the EHR while REDCap is querying the EHR using the local time.

• Bug fix: When using Google Authenticator as a Two-Factor Authentication option, and an Account Manager (as opposed to an Administrator) clicks the "Send Google Authenticator instructions via email" button for a user on the Browse Users page in the Control Center, it would mistakenly fail and give an error message. This only occurs if the user clicking the button is an Account Manager. (Ticket #52597)

• Change/improvement: When importing data via the Data Import Tool, if a CSV data file is re-uploaded on the second page after the initial attempt (e.g., due to errors displayed after the first attempt), it now hides all the error messages on the page after clicking the Upload File button to re-upload the file. Thus it resets the page so that the user does not get confused thinking that the previous errors apply to the current upload if the re-upload process takes a while. (Ticket #52518)

• Change/improvement: When importing data via the Data Import Tool and an error is detected in the data file, the header text of the error message has been changed slightly to prevent confusion so that users more clearly understand that the file was not fully uploaded. (Ticket #52519)

• Bug fix: If a user clicks the "Show plots only" or "Show plots & stats" button on the "Stats & Charts" page in a project, it will mistakenly display the "Download image" button for fields on the page that do not have a graph displayed, in which clicking the button for such fields would cause it to download an unopenable/unviewable PNG file. (Ticket #51565)

• Bug fix: If a field on a repeating event or repeating instrument has branching logic, in which fields in the logic exist on that same repeating event/instrument, then the field might mistakenly not get displayed in the PDF export with saved data.

• Bug fix: If REDCap is set up to connect to the MySQL database via SSL, it would mistakenly not display the "REDCap server is offline!" message to users if the database connection failed. Additionally, for installations not using an SSL database connection, the "REDCap server is offline!" message would be inconsistent in its text being displayed depending on whether the user was on the REDCap Home Page/My Projects page as opposed to accessing a page in which "/redcap_vX.X.X/" appears in the URL (where X.X.X is your current version). (Ticket #51758)

• Bug fix: If a user's account was suspended due to inactivity and afterward an administrator unsuspended the user using the green "Unsuspend User" button on the Browse Users page under the "View User List By Criteria" tab (as opposed to unsuspending a single user when viewing the user account under the "User Search" tab on that page), then if the cron job that suspends users due to activity gets run before the user logs in to REDCap the next time, the cron job would mistakenly suspend them again. (Ticket #52768)

• Bug fix: Users that do not have "Add/Edit/Organize Reports" privileges in a project would mistakenly see the "Organize" link on the left-hand menu that would allow one to create Report Folders. It should not display the link for users with such user rights. (Ticket #52801)

• Bug fix: If a participant is returning to a multi-page survey that has the "Save & Return Later" option enabled, and the survey exists on a repeating event or is a repeating instrument, then if the current survey page being opened by the participant is not the first repeating instance of the survey but is a later repeating instance, then it might mistakenly start the participant on the wrong page of the survey to which they are returning. It normally should take them to the page containing the last question having data. (Ticket #50898)

• Change: On the "Add/Edit Records" page for projects in development status, the notice that real data should not be entered into a project while in development has been moved more to the top of the page to make it more prominent as a reminder to users.

Version 8.9.0 - (released 11/2/2018)

NEW FEATURES, BUG FIXES, & OTHER CHANGES:

• New feature: Report Folders - Reports can now be organized into folders in any given project. If a user has "Add/Edit Reports" privileges, they will see an "Organize" link on the left-hand project menu above the project’s reports. They will be able to create folders and then assign their reports to a folder, after which the project's reports will be displayed in collapsible groups on the left-hand menu.

• New feature: “Edit Access” for reports - In addition to setting "View Access" when creating or editing a report, users can now set the report's "Edit Access" (under Step 1) to control who in the project can edit, copy, or delete the report. This setting will be very useful if one wishes to prevent certain users from modifying or deleting particular reports.

• New feature: Report search - A new search feature exists on the left-hand menu to allow users to search within the title of that project’s reports to help them navigate to a report very quickly.

• Improvement: The Browse Users page in the Control Center now displays a "Can create projects?" column in the user table to indicate if the user has privileges to create or copy a project on their own. This is only available if users in the system are allowed to create/copy projects (as opposed to requesting them be created by an admin).

• Minor security fix: A Cross-Site Scripting (XSS) vulnerability was discovered on certain pages, in which a malicious user could potentially exploit it by manipulating the query string of an HTTP request.

• Minor security fix: An SQL Injection vulnerability was found on surveys pages and data entry pages in which a malicious user could potentially exploit it by manipulating the query string of an HTTP request.

• Major bug fix: If a user has "De-identified" or "Remove all tagged Identifier fields" data export user privileges in a project, and then the user downloads a PDF of a data entry form with saved data, in which the form is a repeating instrument or repeating event, it would mistakenly not remove the appropriate data from the PDF as required according to their user privileges. (Ticket #52190)

• Change: Changed the text "Manage Survey Participants" to "Survey Distribution Tools", which more clearly describes the pages in that section.

• Bug fix: Users using certain browsers (e.g., Firefox) on the "Create New Report" or "Edit Existing Report" page would mistakenly be unable to place their mouse cursor into the input fields in Step 2 on that page, thus preventing them from adding new fields to the report using the auto-complete functionality. (Ticket #52055)

• Bug fix: When performing a data import (either via API or via Data Import Tool) in which the first instrument of a record is locked, it would mistakenly prevent the data import from completing, thus resulting in an error, even if the user is not attempting to update values on the first instrument.

• Bug fix: Uploading, editing, or deleting a file in the File Repository of a project would fail if the project's language was set to anything other than the default "English" language. Bug emerged in REDCap 8.7.0. (Ticket #51457)

• Bug fix: The data dictionary import process would fail if any calculated fields in the data dictionary contained Smart Variables in their calculation. (Ticket #51346)

• Bug fix: If using a custom record label in a longitudinal project, in which the custom record label references a field that exists on an event that is not the first event of the current arm, then it might not display the custom record label at all. (Ticket #50733)

• Bug fix: Some cron jobs were mistakenly shifting by a minute or two each day with regard to the time they should be run by the system. They will now be run at the exact minute they are expected to based on their previous run time + their defined frequency to run.

• Bug fix: When using DDP on FHIR to add a patient to a project from inside the EHR interface, in certain cases the add-patient process would fail and simply return a dialog saying "ERROR".

• Bug fix: If a report in a project is created, copied, reordered, or deleted, then on occasion it may mistakenly cause many (or all) of the existing reports to be reordered in a seemingly random fashion. (Ticket #42809)

• Bug fix: When using the Publication Matching module, if REDCap is upgraded to a newer version after an email has been sent to a PI regarding a possible publication match, then the link in the email would not redirect to the correct webpage properly. (Ticket #52023)

• Bug fix: If custom Homepage Announcement text is set for the system and the current user is sponsor of a user, then the custom text would mistakenly not stretch as wide as the My Projects table. (Ticket #51782)

• Bug fix: If a field on a repeating event/form has a specific repeating instance number that is referenced in a calc field or branching logic (e.g., [weight][2] > 150), then even if the specific repeating instance of the event/form exists, it will throw an error on the data entry form or survey page if the field itself does not have a value saved for the repeating instance that is explicitly referenced.

• Bug fix: When using certain non-English languages for the translated text in a project, the title/hover-over text for the repeating survey icon in the Online Designer would mistakenly get truncated. (Ticket #52126)

• Bug fix: When piping data from a repeating event/instrument onto another instrument or event, especially a non-repeating instrument/event, then the PDF download of that instrument with saved data might mistakenly not pipe the data into the labels in the PDF.

• Bug fix: In a multi-arm project using the Scheduling module, opening a record from the Calendar page and then clicking "view schedule" from the calendar popup would load the "View or Edit Schedule" page but might mistakenly not pre-select the record in the record drop-down list on that page.

• Bug fix: When viewing the Browse Projects page in the Control Center, any projects that have been deleted in the past 30 days but have not yet been removed from the system would have a missing status icon on the far right of the projects table. It should instead be displaying a red cross icon for the status.

• Bug fix: The plugin/hook/module method REDCap::getReport now more strictly checks the value of the third parameter ($exportAsLabels) to ensure it is a boolean. (Ticket #52382)

• Bug fix: When using a bookmarked link of a page in the Plugins, Hooks, and External Modules documentation after REDCap is upgraded to a newer version, then the bookmark would not redirect to the correct webpage properly. (Ticket #51824)

• Change: Added extra admin-specific error message in DDP on FHIR when a FHIR access token fails. This is to help troubleshoot access token issues.

• Bug fix: If a conversation in Messenger is attached to a project, it would mistakenly display the HTML <br> tag when hovering over the conversation title. (Ticket #52308)

• Bug fix: If certain Smart Variables (e.g., [survey-queue-link]) are used in the email text of an Automated Survey Invitation, which also uses datediff with "today" or "now" as a datediff parameter, then it would prevent the ASI+datediff cron job from fully running. Note: This would only affect a small percentage of the total invitations being sent out. (Ticket #51081)

Version 8.8.2 - (released 10/17/2018)

BUG FIXES & OTHER CHANGES:

• Change: If a user loads a data entry form without a record in context, in which it displays the Incomplete/Complete Records drop-downs for choosing a record (this page can only be navigated to by clicking the "Show data collection instruments" link on the left-hand project menu and then selecting a form), if the project exceeds 25,000 records, it will truncate the drop-downs so that they only display the last 25,000 records ("last"=those at the end when viewing an ordered list of all records). This is to improve performance by preventing the page from having to output so much HTML to the client.

• Change: Added suggested change to the REDCap install page regarding the sample MySQL script for creating a new MySQL user. (Ticket #51144)

• Bug fix: If text has been set for the Home Page setting "Announcement text to display at top of Home page and My Projects page" and the setting "Additionally display text on login page?" is set to "No" (which is a new feature in v8.8.1), then it would mistakenly display the custom Home Page text below the login form when a user is logging in, even though it is not supposed to. Bug emerged in REDCap 8.8.1. (Ticket #50889)

• Bug fix: The table listing all the user rights/roles on the User Rights page in a project would mistakenly not display the last column or two of the table. (Ticket #50876)

• Bug fix: When using the Twilio Telephony Services for surveys and setting up an Automated Survey Invitation in which the Invitation Type is "SMS Invitation (contains survey link)", it would mistakenly add the survey link twice to the SMS message. And in the version of REDCap just prior to this one, it was mistakenly adding the survey link if it was not included in the SMS message for the ASI, which should not occur because the instructions state that the survey link will not be automatically added to the SMS when using the "SMS Invitation (contains survey link)" invitation type. So if using "SMS Invitation (contains survey link)" invitation type, it will not add the survey link unless the [survey-url] Smart Variable is used in the SMS message for the ASI. (Ticket #50596)

• Bug fix: If a field exists on a repeating instrument, and a value is being imported for that field (via Data Import Tool or API) in which no value is provided for the redcap_repeat_instrument field for that row of data, it would mistakenly allow the data to be imported without errors, and that data might become orphaned and be inaccessible on certain pages (e.g., Record Home Page, Record Status Dashboard) after the import has completed.

• Bug fix: In certain cases, the left-hand project menu might display the link "View/Edit Records" when instead it should always display the "Add/Edit Records" unless the user does not have "Create Record" privileges.

• Bug fix: When clicking the pencil icon on the Online Designer, it would mistakenly not open the "Add Field"/"Edit Field" dialog if the user was using Internet Explorer. Bug emerged in REDCap 8.8.1 (Standard). (Ticket #51359)

• Bug fix: For certain SFTP server configurations, the system-level feature "e-Consent Framework: PDF External Storage Settings" might mistakenly not save files successfully to the SFTP server.

Version 8.8.1 - (released 10/5/2018)

IMPROVEMENTS, BUG FIXES & OTHER CHANGES:

• Improvement: REDCap admins may now, if they wish, prevent normal users from contacting admins in REDCap Messenger. This option can be enabled under the "REDCap Messenger" section on the "Modules/Services Configuration" page in the Control Center. If set to "prevent users from messaging admins", then users will not be able to add any REDCap admins to any new or existing conversation in Messenger. However, admins will still be able to add normal users and other admins to a new or existing conversation.

• Improvement: The "Sponsor Dashboard" and the Control Center's "Browse Users" page now have a new action button: "Re-send account creation email". This new action is only available for REDCap installations with either "Table-based" or "LDAP & Table-based" authentication. Clicking the button will send the user the same email (which includes the link to set their password) that was sent to them when their Table-based account was created. This will often be used in case the user did not receive the original email (for whatever reason).

• Improvement: Under the "PDF Customization Options" section in the Additional Customizations popup on the Project Setup page, a new option has been added: "Display or hide the Secondary Unique Field value (if enabled) at the top right corner of the PDF". This option will be useful, for example, when sending the PDF to a survey participant, in which the Secondary Unique Field value should not be known or viewable to the participant.

• Improvement: When selecting a color for an item under "Custom survey theme options" on the Survey Settings page, the color-picker now allows users to provide the Hex color code (e.g., #0b5394) to choose the color of the item. (Ticket #8321)

• Change/improvement: The option "Announcement text to display at top of Home page and My Projects page" on the "Home Page Configuration" page in the Control Center now has an extra option that says "Additionally display text on login page?", which will give admins the ability to opt out of displaying that text on the login page, which it currently does by default. (Ticket #21796)

• Major bug fix: If importing new records into a project via Data Import Tool or API Import Records, it would mistakenly not update the record count in the project to reflect the new records that were added.

• Major bug fix: If a user in a Data Access Group is creating a new record and uploading a file for a File Upload field on a form or survey prior to clicking the Save button, which would create the record, it will correctly assign that record to the user's DAG, but that record might mistakenly not show up for the users in that DAG when viewing a report, Record Status Dashboard, Add/Edit Records page, or other pages that display a list of records. This issue would usually correct itself after 3 days.

• Bug fix: If a user attempts to create a new record on the Add/Edit Records page, in which the record contains a tab character (via copy-and-pasting the record name from elsewhere), it would mistakenly not inform the user that tab characters are not permitted in record names and would simply remove them when loading the Record Home Page for that new record. (Ticket #50347)

• Bug fix: If a user adds Custom Event Labels for a longitudinal project, and then converts the project to classic/non-longitudinal format, the Custom Event Label for the first event would mistakenly still appear on the Record Home Page. Custom Event Labels should only appear when a project is longitudinal. (Ticket #49885)

• Change: The language has been abstracted to allow for translation for the popup that appears on data entry forms and survey pages when a user leaves spaces at the beginning or end of a text box's value. (Ticket #37401)

• Bug fix: The notification in the Control Center that informs REDCap admins that a new External Module update is available would mistakenly display versions of modules that were not compatible with the current REDCap version. However, if the admin clicked the blue button to visit the REDCap Repo and then returned back to REDCap afterward, it would temporarily resolve this issue. (Ticket #49957)

• Bug fix: If a user creates a thread in REDCap Messenger that is connected to a project, and then navigates into a different project, in which the Messenger panel is initially closed while in that project, then when the background AJAX call for Messenger runs after being on a page for 60 seconds, it would mistakenly cause a JavaScript error and might cause some functionality of Messenger not to work correctly. (Ticket #24930)

• Bug fix: The plugin/hook/module method named REDCap::evaluateLogic might not interpret the event context correctly depending on the value passed as the $event parameter. (Ticket #49420)

• Bug fix: Fixed issue related to performance boost from REDCap 8.7.2 that caused some very large projects to be extremely slow on certain pages temporarily if multiple users were using the project simultaneously.

• Bug fix: In a longitudinal project that is in production, if a user attempts to un-designate an instrument for an event on the "Designate Instruments for My Events" page, specifically using the CSV file upload option, it would mistakenly allow the user to do so, even though only REDCap admins should be able to un-designate instruments for events while in production. (Ticket #48290)

• Bug fix: When using a date or datetime field with DMY or MDY format as the record ID field, it would mistakenly not save the record name correctly when trying to create the record, but instead it would mangle the date format. (Ticket #49373)

• Bug fix: If branching logic or a calculation on a repeating instrument or repeating event utilizes the Smart Variable "current-instance" (e.g., [yesno_var][current-instance]*1), then when viewing the first repeating instance of that instrument/event, it would mistakenly not perform the branching logic or calculation correctly if the value for that field in the logic/calc changes while on that page. (Ticket #50094)

• Change: When viewing the “Add New Field”/”Edit Field” popup in the Online Designer, it will now ask the user to choose the ontology service that they wish to use (it did not do this in previous versions), even though there is just one to choose. After choosing “BioPortal Ontology Service”, it will then display all the ontologies available for BioPortal, as it has done in the past. This extra step was added to allow for more custom ontology services to be added in the future. But for now, BioPortal is the only service currently available by default in REDCap.

• Bug fix: When using the Twilio Telephony Services for surveys and setting up an Automated Survey Invitation in which the Invitation Type is "SMS Invitation (contains survey link)", it would mistakenly add the survey link twice to the SMS message. (Ticket #50596)

• Bug fix: When downloading a PROMIS Battery from the REDCap Shared Library, it would mistakenly enable the Survey Auto-Continue option for all instruments in the battery when instead it should enable it for all except for the last one.

• Bug fix: When running Data Quality rule F, in which some fields being evaluated exist on a repeating instrument, it might mistakenly display them in the list of discrepancies when in fact it is a false positive. (Ticket #49640)

• Bug fix: Calculated fields would sometimes hit a precision limit in JavaScript and mistakenly return a blank value for the calc field rather than the correct numerical result, which might need to be displayed in scientific (exponential) notation. (Ticket #50578)

• Bug fix: When using LDAP or LDAP & Table-based authentication, it was mistakenly not allowing users to be assigned to a user role in a project if the username contained a space. (Ticket #50791

Version 8.8.0 - (released 9/30/2018)

IMPROVEMENTS, BUG FIXES, & OTHER CHANGES:

• New feature: PROMIS Batteries – 15 batteries of instruments are now available in the REDCap Shared Library. A battery is a set of instruments that can be downloaded from the Shared Library as a bundle, in which they are meant to all be taken together one after another within a single battery. When downloading from the Shared Library, the survey auto-continue feature will be enabled for these instruments to allow a participant to automatically continue from one to another to simulate the battery functionality.

• Improvement: A project's Record ID field can now be used as a Live Filter in any given report, thus allowing users to easily view the report for a single record.

• Bug fix: When hitting the Enter button while inside a date or datetime field that triggers calculations or branching logic on the same page of a form or survey, it might mistakenly display erroneous error prompts stating that something is syntactically incorrect with the calculation or branching logic, which is not the case.

• Bug fix: When piping a value from a date or datetime field into the @DEFAULT action tag of another date/datetime field that has either MDY or DMY date format, the value would mistakenly get mangled and thus be incorrect when the page initially loads. (Ticket #17157)

• Bug fix: When uploading a file for a File Upload field, under certain conditions it might mistakenly cause multiple rows to be added to the redcap_data database table for that record. (Ticket #50178)

• Bug fix: Fixed issue related to performance boost from REDCap 8.7.2 that caused some very large projects to be extremely slow on certain pages temporarily if multiple users were using the project simultaneously.

• Bug fix: If records exist in an arm in a multi-arm project, and then that arm is deleted, those records in that now-deleted arm might mistakenly appear on certain pages, such as the Record Status Dashboard or Add/Edit Records page. (Ticket #50353)

• Bug fix: When using DDP on FHIR and opening a record on the Record Home Page while viewing it inside the EHR, a JavaScript error might mistakenly occur, thus sometimes preventing the DDP adjudication dialog from opening.

• Bug fix: When creating a new Table-based user in the Control Center, in which the user's attributes contain special/non-Latin characters, then depending on the server's MySQL collation_connection, it might not save the user's attributes correctly in the database but may instead mistakenly garble them. This bug was supposedly fixed in REDCap 8.7.3 but was mistakenly not. (Ticket #48983)

• Bug fix: When mapping an EHR field on the DDP mapping page in a longitudinal project using DDP on FHIR, and clicking the "Copy mapping to other event" for a given field, it might mistakenly also copy the category header that immediately follows that field, which makes the page look confusing to the user.

Version 8.7.4 - (released 9/20/2018)

BUG FIXES & OTHER CHANGES:

• Major bug fix: If a user has data export privileges of "De-identified" or "Remove all tagged Identifier fields", and then the user exports a report in which every field in the report gets removed due to their export privileges, then it would mistakenly export data for *all* the fields in the entire project. (Ticket #48976)

• Major bug fix: If a user attempted to put a production project into Draft Mode on the Online Designer page, it would fail and merely reload the page. (Ticket #49866)

• Bug fix: The projects table on the Browse Project page in the Control Center was cut off on the right side. (Ticket #49773)

• Change: Added the HTML tags <map> and <area> to the list of allowed tags that can be used in user-defined text (e.g., field labels, survey instructions). (Ticket #49526)

• Bug fix: If a field was using @DEFAULT, @NOW, or @TODAY action tags, and that field was also being piped into text somewhere on that same page, then the field values would mistakenly not get piped when the page initially loads. (Ticket #49839)

Version 8.7.3 - (released 9/19/2018)

IMPROVEMENTS, BUG FIXES, & OTHER CHANGES:

• New options for Data Exports

  • Improvement: When exporting a report, a new “Data formatting options” section appears in the export dialog to allow users to choose the CSV delimiter character to be used in CSV Raw Data and CSV Labels exports. Options include comma (default), tab, semi-colon, pipe, and caret. This is useful in certain cases when the resulting data file needs to have another delimiter, such as a tab, for example. In addition, the two API methods “Export Records” and “Export Reports” have a new analogous parameter “csvDelimiter” that will set the CSV delimiter character if using “csv” as the format in the API request. See the API documentation for full details. (Ticket #30939)

  • Improvement: When exporting a report, a new “Data formatting options” section appears in the export dialog to allow users to optionally force all numbers into a specified decimal format. It will default to “Use fields’ native decimal format”, but provides the choices “Use period/full stop” and “Use comma” as the decimal character for all numbers. This will allow projects that have fields with period/full stop decimals (calc fields, number validated fields) and those with comma decimals (comma-as-decimal validated fields) to all be exported in the same uniform number format, thus providing greater consistency in the data being exported. In addition, the two API methods “Export Records” and “Export Reports” have a new analogous parameter “decimalCharacter” that will set specified decimal format for all numbers in the API request. See the API documentation for full details. (Ticket #30939, #34597)

• Improvement: New optional parameters added to the API Export Records method to filter data returned based on when a record was created or modified

  • dateRangeBegin – To return only records that have been created or modified *after* a given date/time, provide a timestamp in the format YYYY-MM-DD HH:MM:SS (e.g., '2017-01-01 00:00:00' for January 1, 2017 at midnight server time). If not specified, it will assume no begin time.

  • dateRangeEnd – To return only records that have been created or modified *before* a given date/time, provide a timestamp in the format YYYY-MM-DD HH:MM:SS (e.g., '2017-01-01 00:00:00' for January 1, 2017 at midnight server time). If not specified, it will use the current server time.

• Improvement: The Record Status Dashboard will now remember the user's last selection for the "page number" drop-down and the "records per page" drop-down, so that when they return to the dashboard in that project in the future, it will already have their last selections pre-selected for those two drop-downs. Note: It already remembers the user's last selection for "dashboard displayed" and "data access group". (Ticket #48913)

• Improvement/change: When a user copies a project via the "Copy the project" button on the Other Functionality page, it now logs the PID (project_id) and project title of the new project in the copied project, and it now also logs the PID and project title of the originating project in the newly created project. So now it should be much easier for users to see if someone copied a project, and if so, determine which project is the one that had been created from the original. (Ticket #47208, #42783)

• Improvement: Two new parameters "exportAsLabels" and "exportCsvHeadersAsLabels" were added to the plugin/module method named REDCap::getReport. These allow developers to designate whether to output data as raw values vs labels, as well as choose to export CSV headers as labels rather than as variable names (for CSV outputFormat only). (Ticket #49173)

• Improvement: If one or more External Modules are enabled in a project, it now allows the user to choose if they want to copy over the module configuration settings when copying the project. In previous versions, it would always copy the settings without asking, even though the modules were disabled by default. So now users have a choice.

• Bug fix: After completing a data import in a project with thousands or tens of thousands of records, many project pages would sometimes become unresponsive for quite a while.

• Bug fix: When viewing the To-Do List in the Control Center, some requests might mistakenly still show up in the request counts even though the requester's account has been deleted from the REDCap system. (Ticket #48846)

• Bug fix: Certain database queries that check to make sure that a project's reports are in the correct order were getting run more than necessary, which would sometimes cause certain pages in a project to run slowly.

• Bug fix: For large screens, project pages might mistakenly have an empty column of whitespace on the far right. (Ticket #49155)

• Bug fix: The External Module framework methods setDAG() and addAutoNumberedRecord() were not updating the record list cache table, thus causing some record lists (e.g., Record Status Dashboard) to become out of sync with the data in the redcap_data database table. Bug emerged in REDCap 8.7.2 Standard. (Ticket #49215)

• Bug fix: After editing the branching logic of a field in the Online Designer, it would mistakenly chop off the first character in the branching logic when displaying it in red text on the page for the field. (Ticket #49098)

• Bug fix: When using DDP on FHIR to add a patient to a project, in some cases it would navigate to an incorrect non-existing record named "Undefined" in the REDCap project after clicking "View patient in project" button after creating the record via DDP on FHIR.

• Bug fix: When using DDP on FHIR, some LOINC codes related to Multiple Sclerosis were mistakenly missing from the DDP field mapping page.

• Bug fix: When creating a new Table-based user in the Control Center, in which the user's attributes contain special/non-Latin characters, then depending on the server's MySQL collation_connection, it might not save the user's attributes correctly in the database but may instead mistakenly garble them. (Ticket #48983)

• Bug fix: The To-Do List page in the Control Center would mistakenly display with the action buttons overlapping the previous column in the table. (Ticket #49096)

• Change: When a REDCap administrator enables or disables either the DDP on FHIR module or the DDP Custom module, it now explicitly states this on the Logging page, whereas previous versions merely logged the action generically as "Modify project settings".

• Bug fix: When using DDP on FHIR, the information page/popup that describes how to use DDP to users was mistakenly missing the specific codings required for the three demography fields "sex", "race", and "ethnicity". The required multiple choice codings for those fields are now listed in the DDP on FHIR informational page that is accessible on the DDP on FHIR Control Center page and via the popup on a project's Project Setup page.

• Bug fix: When launching multiple patients using DDP on FHIR inside the EHR interface (i.e., multiple tabs during same session), if the user returned to an older tab/patient during the same session, it might mistakenly confuse it with the latest patient that was loaded, thus losing that tab's proper context for the patient and causing confusion for the user.

• Bug fix: If using MySQL 8.0 as the database, in certain cases the Control Control might erroneously display the "Database structure is incorrect" warning even though nothing is wrong with the database tables. (Ticket #49580)

• Bug fix: If using certain non-English languages as the system language, the login page might mistakenly truncate the "Username:" or "Password:" labels. (Ticket #48547)

• Bug fix: When exporting a project's Project XML file, for certain server configurations, it would cause the XML file to have all linefeeds removed from Section Headers and Field Labels. Note: This fix will not fix any Project XML files that have already been generated but will fix this issue for any XML files generated in the future. (Ticket #48719)

• Bug fix: If there exists piping, calculations, or conditional logic using the Smart Variables first-event-name or last-event-name that happens to be prepended to a checkbox field, in which a checkbox choice is explicitly specified inside parentheses, it would mistakenly return a list of all the checked-off checkbox labels instead of the checked-off status for the specified choice. (Ticket #49378)

• Bug fix: When a user attempts to place a production project into draft mode, it might mistakenly just reload the same page with no changes, thus preventing the project from being put in draft mode. (Ticket #6346)

• Fixes and updates for External Modules Framework

• Bug fix: If an External Module was using the API endpoint for assets (non-PHP pages), it would mistakenly enforce authentication on those assets, which would cause issues for certain authentication types, such as Shibboleth.

Version 8.7.2 - (released 9/7/2018)

IMPROVEMENTS, BUG FIXES, & OTHER CHANGES:

• Improvement: Performance boost – Certain pages in projects with thousands or more records should now load much faster in most cases. This includes the Record Status Dashboard, various pages utilizing Data Access Groups, and certain reports. Reports A and B should especially see significantly faster loading (excluding when viewing “all” pages in report A or B).

• Improvements related to viewing or creating reports

  • New report option that will combine checkbox options into a single column of only the checked-off options. Previously, any checkbox fields in a report would have their choices represented as separate columns in the report, but with this new setting, they can now all be represented as a single column with comma-delimited values and comma-delimited labels. Note: If data is exported to a stats package on a report using this option, checkbox fields will be represented as text fields in the stats package’s syntax file that gets generated by REDCap.

  • Report description – Users may now optionally set a description for a report, in which the description gets displayed as text below the report title on the report page. This allows users to provide instructions or explanatory text for the report. Note: HTML may be used in the description to add links or to style the text.

  • Change: When exporting a report, it now includes the report’s title as part of the resulting export files’ file name. This should make it easier to distinguish different exported data sets if a user is exporting several reports for a given project.

  • Improvement/bug fix: In previous versions it was very difficult (and sometimes impossible) to create reports with lots of fields in projects that contained >1000 total fields. In some cases, it would cause the Create Report page to be very sluggish or even to crash in some cases. This should no longer happen, and users should be able to easily create reports with thousands of fields, if they wish, with no problem.

• Improvement: If using "Local" file storage for uploaded files, inline image attachments for Descriptive fields and also survey logos will load on the page with their proper width and height already set, which should cause shifting/disturbance on the page due to the images loading slightly later than the page itself.

• Bug fix: When setting the value of the Rate Limiter on the General Configuration page in the Control Center, it would display a soft validation error if a value was entered that was less than 60. It should instead allow all integers to be entered with a minimum possible value of "0".

• Bug fix: If a POST request to REDCap exceeds the maximum number of POST parameters according to the max_input_vars setting in the PHP.INI configuration file, it might truncate the parameters sent and mistakenly not display an error message, thus only saving part of the data submitted without informing the user of such. It now properly returns an error message to let the user knows if this ever occurs. This includes API requests. (Ticket #47117)

• Bug fix: Updated some outdated text on the "Administrators & Acct Managers" page in the Control Center. (Ticket #47531)

• Change: When exporting a data dictionary, it will now automatically prepend the Field Annotation column with a single space character if the value begins with an "@" sign. This is to prevent issues when loading the data dictionary into Microsoft Excel, which uses "@" to denote the beginning of an equation. When the data dictionary is re-uploaded back into REDCap, the extra space will be subsequently removed to maintain the integrity of the initial value in the data dictionary as it was exported.

• Bug fix: If a record in a project has some survey invitations scheduled, and then the record is renamed, its associated invitations would mistakenly get disassociated from the record, thus causing the invitations not to get delivered. (Ticket #47887)

• Bug fix: When using the "DDP on FHIR" module and launching a REDCap window inside an EHR interface, if the user navigates inside a REDCap project in that window, it would mistakenly display the left-hand project menu when it should instead keep the menu invisible in that window. Bug emerged in REDCap 8.7.0.

• Bug fix: If a user placed their cursor into any text input field and clicked their Backspace button on their keyboard, it would cause a JavaScript error. In most cases, this would go unnoticed; however, some browsers might display a popup alerting the user of this error, which could confuse the user.

• Bug fix: Drop-down fields using the auto-complete option would react very slowly when typing text into them if the number of drop-down options was very large (>1000). For larger drop-down fields, it now requires more characters (based on the drop-down size) to be initially typed before it begins performing the auto-complete functionality. For example, if the drop-down contains more than 200 options, it requires at least 1 character to be entered before auto-complete is activated, and if it contains more than 500 options, then requires 2 characters (and so on, up to 4 characters max). Bug emerged in REDCap 8.7.0 (related to jQuery 3).

• Bug fix: The Repeating Instruments tables displayed at the bottom of the Record Home page would mistakenly be displayed vertically rather than horizontally. Bug emerged in REDCap 8.7.0.

• Bug fix: Minor aesthetic styling fixes due to Bootstrap 4 issues. This additionally includes reports not printing correctly in Firefox. (Ticket #47920)

• Bug fix: When viewing the "Copy existing choices" popup when adding/editing a field in the Online Designer, many of the choices might mistakenly overlap each other, thus making some impossible to read.

• Bug fix: The REDCap cron job was mistakenly being counted toward "Page Hits" as displayed on the Control Center's Activity Graphs page. (Ticket #46074)

• Bug fix: When using the e-Consent Framework in a project, in which a record has an e-Consent PDF file associated with it and a user deletes the record, it would mistakenly not delete the record's e-Consent entry. This would cause problems if another record was created later using the same record name, in which it would prevent the saving of that new record's e-Consent file. (Ticket #38660)

• Change: Minor changes made to login process for AAF authentication.

• Change: When exporting data to SPSS, date and datetime fields are now represented as A500 and text fields as A1000 in the SPSS syntax file, whereas previously they were all represented as A30000, which could cause very slow processing when loading the data into SPSS. (Ticket #37115)

• Bug fix: When using "Japanese (Shift JIS)" for a project's "character encoding for exported files" setting, and the project's PDF Customization setting has the PDF header text (e.g., Confidential) in Kanji/Japanese, then the PDF header text would mistakenly not display correctly in the PDF. (Ticket #48035)

• Bug fix: LDAP allows for spaces to be used in usernames, and even though REDCap users could successfully log into REDCap while having a space in their username, REDCap would not allow such users to be added to projects, in which it would display an error message stating "User names can only contain letters, numbers, underscores hyphens and periods". If using "LDAP or "LDAP & Table" authentication, it will now allow users to be added to a project via the User Rights page even if their username contains a space. (Ticket #48169)

• Bug fix: When using literal date or datetime values inside a datediff() function in the "Add/Edit Branching Logic" popup in the Online Designer and testing the logic against a record, it might mistakenly state the field should be hidden when instead it should be shown (or vice versa). Related, if using literal dates inside a datediff() function in the branching logic of a field, and a user goes to export a PDF with saved data of that field's instrument for an existing record, the field might mistakenly be hidden in the PDF when instead it should be shown (or vice versa). (Ticket #47717)

• Bug fix: When using "Japanese (Shift JIS)" for a project's "character encoding for exported files" setting, the Kanji text might not display correctly if the PDF is opened on certain devices. The remedy this, the internal font in the PDF has been changed from Gothic to Kozmin. (Ticket #48035)

• Bug fix: When using a Stop Action on a checkbox on a survey, in which the "Enhanced checkbox and radio button" option is enabled for the survey, then if a participant triggers the Stop Action but chooses to "Continue survey" (rather than ending the survey), it would mistakenly not uncheck the checkbox choice they had selected. (Ticket #48273)

• Bug fix: Using an X-instance Smart Variable that is appended to a variable or Smart Variable containing a parameter with a colon (e.g., [mycheckbox:checked][last-instance]) might mistakenly not be parsed correctly, thus possibly returning an incorrect value. (Ticket #48251)

• Bug fix: When the record ID field in a project has field validation, and the Scheduling page is being used in a longitudinal project to create a new record (assuming record auto-numbering is not enabled), the Scheduling page would mistakenly not employ the field validation if a record name was entered in an incorrect format. This only occurs for certain field validation types. (Ticket #46643)

• Bug fix: When using the Smart Variables "previous-event-name" or "next-event-name" in a calculated field while viewing the first or last event, respectively, it would mistakenly display the error prompt stating that there was an error in the calculation. Instead, it now silently replaces those with a blank value (wrapped in quotes) in the equation to prevent an error from occurring in order to force a blank value to be returned. (Ticket #48631, 48669)

• Bug fix: When using the X-event-name Smart Variables as prepended to a field variable, in which the variable name contains a number, it might not parse the Smart Variable correctly, thus causing it to replace it with a blank value or the value from the wrong event. (Ticket #48576)

• Bug fix: If PHP's Multi-Byte String extension is not enabled on the web server, then REDCap might throw a fatal PHP error when attempting to send an email. (Ticket #48757)

• Bug fix: Some data entry forms, especially for records that have repeating instruments with many repeating instances saved (i.e., hundreds or more), would load very slowly, sometimes causing the page to time out and never fully load. They should now load much faster. (Ticket #40634)

• Bug fix: When calling the method REDCap::getPDF inside a hook in a project, in which the current user does not have full data export privileges, the method would mistakenly fail to output the PDF. The method should work regardless of the user's project-level rights. (Ticket #48756)

Version 8.7.1 - (released 8/15/2018)

BUG FIXES & OTHER CHANGES:

• Major bug fix: Calculations that exist on a repeating instrument or repeating event might mistakenly not get calculated when importing data via API or Data Import Tool or when executing Data Quality rule H.

• Bug fix: When cross-event branching logic is used on a field in a longitudinal project, in which some events being referenced in the logic do not contain any data for a given record, in some cases the PDF export of an instrument would mistakenly not correctly determine if the field should be hidden or not in the PDF, and thus it might hide the field when it should display it (or vice versa). This bug only affects the PDF. (Ticket #42206)

• Bug fix: The action of creating or modifying a Custom Record Status Dashboard was mistakenly not getting logged on the project Logging page.

• Bug fix: The default browser behavior of navigating back to the previous page after a user clicks their keyboard's Backspace button was mistakenly occurring in "search" input type fields, which are predominate in External Modules and their configuration pages.

• Bug fix: An error message on the Data Import Tool had incorrect text. (Ticket #47040)

• Bug fix: In longitudinal projects in production, the "select all" and "deselect all" links on the "Designate Instruments for My Events" page would mistakenly allow the user to select/deselect already-designated instruments. Instead it should only allow the user to select/deselect instruments that are not yet designated. (Ticket #47020)

• Bug fix: Small SQL issue caused if upgrading to 8.7.0 from an earlier version. (Ticket #47020)

• Bug fix: In a longitudinal project that has multiple arms and is also using the Double Data Entry module, the Record Status Dashboard would mistakenly not display any form status icons on the page for a user that is Double Data Entry person 1 or 2.

• Bug fix: Minor alignment or placement issues for elements on certain pages (due to introduction of Bootstrap 4), such as the position of the main project window on iPads and also the placement of "Upcoming Calendar Events" table at the bottom of the Project Home page. (Ticket #47074, #47230)

• Various fixes and updates for the External Modules framework

Version 8.7.0 - (released 8/9/2018)

NEW FEATURES, BUG FIXES, & OTHER CHANGES:

• New feature: Integration with Microsoft Azure Blob Storage for file storage - see the File Upload Settings page in the Control Center to set up file storage on Azure Blob Storage.

• Improvement: A "Copy existing choices" link was added to the "Add Matrix of Fields" popup on the Online Designer page (just like the same link in the "Add New Field" popup on that same page) to copy the choices from an existing multiple choices field to that matrix of fields. (Ticket #46680)

• Change/improvement: The JS/CSS front-end libraries jQuery and Bootstrap have been upgraded to jQuery 3 and Bootstrap 4.

• Change: Added a new check on the Configuration Check page that detects if the current MySQL user (or the MySQL user used for Easy Upgrade) has CREATE table privileges but does not have either ALTER or DROP table privileges. If the user has CREATE but not ALTER and DROP privileges, then it would cause REDCap to mistakenly create many database tables with names beginning with "redcap_ztemp", which are created as temporary tables when testing the MySQL user's privileges.

• Change: When exporting data in CSV format (raw data or labels) on the "My Reports & Exports" page, it now maintains all double quotes in free-form text, whereas previous versions would replace all double quotes with single quotes in a CSV export. Note: When exporting to stats packages, it will still replace double quotes with single quotes for compatibility purposes.

• Bug fix: When using the E-signature feature at the bottom of a data entry form, if the username is in an incorrect case or has trailing spaces, it would mistakenly fail during the initial E-signature login. It should instead be trimming the username of any whitespace at the beginning or end, and should be evaluating the username as case insensitive since this is how the regular login behaves.

• Bug fix: If an external module has its configuration permissions set to "Require module-specific user privilege" on the External Modules page in the Control Center, and a user has been given the rights to configure the module in a project, then if a REDCap administrator opened the User Rights page in the project to edit that user's module rights and unchecked every module and saved it, the user would mistakenly still have access to the modules to which they previously had access. This only occurs when all modules are unchecked on the User Rights page. (Ticket #44112)

• Bug fix: When using a logo on a survey and also using the "Save & Return Later" feature, if a respondent chose to return to a survey, then upon loading the survey page to enter their return code, a JavaScript error would occur on the page. (Ticket #46143)

• Change/improvement: Elements on survey pages have been modified to work better for accessibility purposes, such as with screen readers.

• Change: Some language was hard-coded in previous versions. The following things have now had their text abstracted so that they is now translatable: the buttons for uploading/deleting files in the File Repository, the "Generate Schedule" button on the Schedule page, and the "Auto Logout Warning" popup. (Ticket #26708)

• Various fixes and updates for the External Modules framework

• Bug fix: If any projects used Twilio telephony services for surveys and had an Automated Survey Invitation set to use the "Participant's Preference" as the delivery method, then new invitations scheduled by the ASI might mistakenly not include a survey link if an individual participant's preference is "Email Invitation". (Ticket #42868)

• Change: The footer of survey pages now says "Powered by REDCap", whereas previous versions have "REDCap X.X.X - © 20XX Vanderbilt University". For non-survey pages, the footer will remain the same.

• Bug fix: When executing a custom Data Quality rule that contains a single variable in the logic, extra discrepancies might mistakenly be returned in some cases, especially if the project is longitudinal and/or contains repeating instruments/events. (Ticket #45695)

• Bug fix: When piping the Smart Variable [previous-event-name] or [next-event-name] when it is prepended to a variable name, it might mistakenly replace it incorrectly by replacing just the Smart Variable (but not the field variable) with six underscore characters or with nothing (depending on the context). (Ticket #46001)

• Bug fix: The PHP LogicTester class mistakenly contained some debugging code that prints SQL out on the page. (Ticket #46864)

Version 8.6.5 - (released 8/3/2018)

BUG FIXES & OTHER CHANGES:

• Major bug fix: When upgrading from a REDCap version lower than 8.4.0 to version 8.4.0 or higher, if any projects used Twilio telephony services for surveys and had an Automated Survey Invitation set to use the "Participant's Preference" for the delivery method, then new invitations scheduled by the ASI might not include a survey link (when needed) upon being scheduled. (Ticket #42868)

• Bug fix: When using Twilio telephony services for surveys and having it make voice calls to participants, each voice call would mistakenly have an unnecessarily long pause at the beginning of the call.

• Bug fix: When importing data values for a repeating event via Data Import Tool or via API but not including the form status field in the imported data set for any of the instruments on which the imported fields are located, those repeating instances on the repeating event might get orphaned in some user interfaces, such as in the Record Status Dashboard, and thus do not become visible until the user attempts to create a new instance through the user interface and then saves the form. (Ticket #46285)

• Bug fix: AAF Authentication was mistakenly being excluded during CSRF token check.

• Bug fix: When piping the Smart Variable [event-name] when it is prepended to a variable name, it might mistakenly replace it incorrectly by replacing it with the current event name without square brackets around it. (Ticket #46001)

• Bug fix: In certain cases Smart Variables were not getting evaluated correctly when used inside the conditional logic of Automated Survey Invitations, thus causing invitations not to get scheduled appropriately. (Ticket #44104)

• Bug fix: On the Project Modifications page, when clicking the Compare button to view the differences between old and new choices of a multiple choice field, it would mistakenly always display "0" for the record count for every choice, even if some records do have that choice saved. This issue appears to only occur in specific versions of PHP. (Ticket #25851)

• Bug fix: In a report or via the API, if the user is requesting specific records and also specific events to be returned, if there is no data for those events for those records, then it would mistakenly return empty "ghost" rows as if data does exist on those events, which is confusing. (Ticket #46342)

Version 8.6.4 - (released 7/30/2018)

BUG FIXES & OTHER CHANGES:

• Bug fix: The upgrade or install pages would fail to load if running PHP 5.3 or 5.4, thus preventing the administrator from upgrading or installing REDCap. This bug emerged in REDCap 8.6.2, and it exists in both 8.6.2 and 8.6.3.

Version 8.6.3 - (released 7/30/2018)

BUG FIXES & OTHER CHANGES:

• Critical security fix: An SQL Injection vulnerability was found on several pages that could be potentially exploited by manipulating the URL query string of an HTTP request by a malicious user, including non-REDCap users through publicly available URL end-points that do not enforce authentication. It appears very unlikely that this vulnerability could be used to extract information from a REDCap database. But if enough knowledge is known about REDCap internally, it might be possible for an outsider to upload files into random projects in REDCap; however, there is no evidence that those same files could be executed or downloaded, and thus the files would essentially be orphaned (would not be accessible through the user interface in any way) and would simply take up unnecessary space on the file server. This bug appears to exist in every version of REDCap since version 4.0.0.

• Major bug fix: On survey pages, data entry forms, and other pages where conditional logic and calcs are evaluated, those pages may take an exorbitant amount of time to load (and in some cases may never successfully load at all). This appears to only affect certain Windows server environments.

Version 8.6.2 - (released 7/18/2018)

BUG FIXES & OTHER CHANGES:

• Change/improvement: Better regional support for AWS S3 file storage

  • If using Amazon Web Services (AWS) S3 for file storage in REDCap, you may now use many of the newer regions/endpoints around the world. The previous S3 library in REDCap would only work for certain regions of the world, whereas now it works for all available AWS regions.

  • The S3 configuration options on the File Upload Settings page in the Control Center now require a “region” to be provided (or else “us-east-1” is used by default). This refers to the region name (e.g., ap-northeast-2) and NOT the endpoint URL. Previous versions of REDCap required providing the endpoint URL. If you had already set an endpoint URL for this in REDCap, then during the upgrade, REDCap will automatically translate the endpoint URL into a region name for you so that everything will continue to work normally.

  • Note: Because of this change, PHP 5.5.0 or higher is now required for using AWS S3 file storage in REDCap.

• Change/improvement: When displaying the filename of an uploaded file on a File Upload field on a form or survey, if the filename is very long (>34 characters in length), it now truncates the filename with an ellipsis closer to the middle of the filename rather than at the end. This allows the file extension to be visible, whereas in previous versions it was impossible to tell what type of file it is without downloading it if the filename was long.

• Change: When viewing a partially completed or fully completed survey response on a data entry form, the text color and background color of the red box near the top of the page have been changed to reflect the state of the response more accurately (i.e., it is no longer displayed as a red box, which often evokes a sense of there being an error). If the response is partially completed, it is displayed as an orange box, whereas if it is fully completed, it is displayed as a green box. The box color is thus consistent with the color instrument status icons used.

• Major bug fix: On some occasions, DDP on FHIR was mistakenly not parsing all the data being received from the EHR, thus some clinical data values from the EHR were not being stored in REDCap.

• Bug fix: When using the biomedical ontology search for a text field on a form or survey, it was mistakenly including Semantic Types Ontology (STY). It now excludes Semantic Types Ontology from biomedical ontology search unless field validation is STY. (Ticket #44910)

• Bug fix: In REDCap Messenger, it might display that there are unread messages for the user to read even though there are none.

• Bug fix: When a survey has "Save & Return Later" enabled, and a respondent clicks the "Start Over" button upon returning to the survey, the survey page mistakenly does not display the survey instructions at the beginning of the survey. (Ticket #44838)

• Bug fix: The record drop-down list displayed in the Online Designer both in the "Add/Edit Branching Logic" popup and also in the "Add/Edit Field" popup for calc fields would mistakenly not display the Custom Record Label and Secondary Unique Field labels.

• Bug fix: The record drop-down list displayed in the Online Designer both in the "Add/Edit Branching Logic" popup and also in the "Add/Edit Field" popup for calc fields would be too long for projects with large amounts of records, which could cause the page to load very slowly or not load at all. To remedy this, the record drop-down list now only displays the first 200 records.

• Bug fix: If using AWS S3 for file storage and a user attempts to copy a project that contains files for File Upload fields, files for Signature fields, or attachments for Descriptive fields, then none of those files would get copied to the new project from the original project. (Bug emerged in REDCap 8.6.1.)

• Change: Small change to "Easy Upgrade" instructions for easier setup

• Change: The database tables "redcap_surveys_response_users" and "redcap_surveys_response_values" were removed because they were never really used for anything, so they were taking up lots of database space unnecessarily.

• Change: When viewing a partially completed or fully completed survey response on a data entry form, the process of displaying the number of contributors to the response in the red box near the top of the page was resulting in very slow page loads in many circumstances. To provide a better user experience for this, it now displays a "View all contributors" link instead, which can be clicked to reveal the users who have contributed to that response.

• Bug fix: The rendering of the Participant List was unnecessarily slow due to some incorrect queries that were pulling information not needed. This fix should make the Participant List load much faster, especially for larger projects with thousands of records.

• Bug fix: In the "Compose Survey Invitations" popup on the Participant List page, the "Previously Sent Email" drop-down list displayed under "Load message box with text from a previous email?" would mistakenly load email text containing static, unique survey links from previously sent invitations (which could cause major issues if used verbatim for new invitations) when instead it should have been loading the invitation text containing the Smart Variable [survey-url] in place of the static survey link.

• Change: Very small wording change to the certification text on the certify page when using the e-Consent Framework on a survey.

• Change: On the "Edit a Project's Settings" page in the Control Center, it now does not display the drop-down list of projects if viewing the settings of a specific project, but instead provides a link to "Select another project", which will then display the drop-down list. This helps the page load faster if there are many (>10,000) projects that exist in the REDCap system.

• Change/improvement: The REDCap Shared Library can now be disabled (if desired) at the project level by an administrator on the "Edit a Project's Settings" page in the Control Center. If disabled for a given project, all Shared Library buttons and all references to the Shared Library will no longer appear in the project.

Version 8.6.1 - (released 7/11/2018)

IMPROVEMENTS, BUG FIXES, & OTHER CHANGES:

• Improvement: Smart Variables are now able to be utilized in Data Quality rule logic. Note: In many cases, Smart Variables in the logic may cause Data Quality rules to take much longer to complete, which is due to the fact that the logic has to be re-evaluated for *every* item being processed by the DQ rule, whereas normally the logic only needs to be evaluated just once at the beginning of when the DQ rule is executed.

• Improvement: Data Quality rule H (i.e., "Incorrect values for calculated fields") and auto-calcs (i.e., the process of calc fields being triggered by data imports or cross-form/cross-event calculations) can now handle Smart Variables that are used inside calculated field equations. In previous versions, such calc fields could only successfully run while on a data entry form or survey page.

• Bug fix: When creating/editing an Automated Survey Invitation and in Step 3 setting the option "Send after lapse of time" that would result in a send time occurring in the year 2038 or afterward, it would mistakenly set the send time to be 1/1/1970 or 12/31/1969 instead. (Ticket #44459)

• Change: The file install.php is no longer included in the list of replacement non-versioned files, which are provided in case the non-versioned files in REDCap ever change in the future. Since install.php is only used during the install process, there is no need for it to stay updated afterward.

• Change/improvement: When using the Easy Upgrade module, links to the LTS changelog and Standard Release changelog pages on the REDCap Community site are now included inside the box that lists new versions that are available.

• Change/improvement: The MySQL setting "SQL_SAFE_UPDATES" is now automatically set to be disabled for the database connection used by REDCap and also has been set as disabled in the REDCap upgrade SQL script that is output by the Upgrade Module. This is done in order to prevent some MySQL clients from mistakenly enabling safe updates, which might cause some queries not to get executed successfully during an upgrade, and to prevent issues with REDCap running on database servers that might have safe updates enabled by default in the MySQL configuration file.

• Improvement: A Data Access Group can no longer be deleted if one or more records are still assigned to it. If a user attempts to delete a DAG that contains records, it will prevent such and display an error message.

• Bug fix: When using the Smart Variables [form-link] and [record-name] inside the email subject or email message of an Automated Survey Invitation, it would mistakenly not pipe the record name into the form link URL for [form-link] and would mistakenly replace [record-name] with "______" instead of the real record name. (Ticket #44549, #44550)

• Bug fix: The "DDP on FHIR" page that gets displayed inside the EHR user interface was mistakenly missing a link to the "DDP on FHIR" information page that provides all the information about that module.

• Bug fix: If a slider field exists on an instrument that is currently locked, the user would mistakenly still be able to modify the slider position and value. Note: This would not affect the slider's value at all since the instrument could not be saved until it was unlocked. So at most, this could cause confusion. (Ticket #44608)

• Updates and fixes for the External Module Framework

• Bug fix: In a calculated field or in branching logic that has cross-event logic while referencing a field that exists on a repeating instrument from another event, it would mistakenly assume instance #1's value to always be blank/null for that field and thus cause the logic or calculation to come to an incorrect result. (Ticket #44474)

• Bug fix: If a suspended user gets unsuspended by an administrator either via the Browser Users page in the Control Center or via a Sponsor Dashboard request, the user would mistakenly get suspended again within the next day if they did not log into REDCap soon after being unsuspended.

• Bug fix: If a sponsor had made a request to an administrator via an action in the Sponsor Dashboard, if the administrator was using a link in the email to process requests (as opposed to using the To-Do List), the administrator might mistakenly try to process the same request twice, which could cause issues. Now if an administrator attempts to process an already-processed request, it will display an error message letting them know that it has already been processed and therefore cannot be processed again.

• Bug fix: Users might mistakenly receive a notification email stating that they have an unread message in a conversation in REDCap Messenger, even though the conversation has been deleted.

Version 8.6.0 - (released 7/2/2018)

BUG FIXES & OTHER CHANGES:

• New feature: Easy Upgrade

  • Administrators may now upgrade to a more recent version of REDCap in an easier and more automated fashion with just a couple clicks. The Easy Upgrade process (if fully enabled) allows REDCap administrators to upgrade REDCap using only the REDCap user interface in the Control Center (i.e., direct access to the web server or database server is not required).

  • Setup instructions will be displayed in the Control Center at the top of the page in blue regarding the steps that need to be performed to enable the Easy Upgrade feature, which requires the three following things in order to function:

    • When using this feature, REDCap will auto-download the upgrade zip file of a REDCap version and will extract it on the REDCap web server, which requires that the REDCap application (e.g., Apache, IIS) must have “write” permissions to the main “redcap” webroot directory on the server. The setup instructions in the Control Center will notify you regarding the permission status of REDCap to be able to write to the “redcap” webroot.

    • REDCap needs to be able to make outbound HTTP requests to https://redcap.vanderbilt.edu, which hosts the web service that serves the REDCap upgrade files that are downloaded by the application during the Easy Upgrade process.

    • A MySQL user with elevated privileges (e.g., CREATE, ALTER, DROP tables) is required for this feature since it will need to sometimes create, modify, and even delete database tables during the upgrade process. The setup instructions for this feature in the Control Center provides two different methods for accomplishing this. 1) The current MySQL user that REDCap utilizes can be given elevated privileges. This is often not recommended because some security experts view this as a potentially exploitable weakness, such as if a malicious user somehow manages to discover an SQL injection vulnerability in the application to take advantage of those elevated privileges, or 2) A new MySQL user can be created with elevated privileges for the explicit purpose of using the Easy Upgrade process (and also the Auto-Fix method seen below for fixing the database structure). This new MySQL would never be used for normal REDCap database connection calls. For both of these two options, REDCap will provide the SQL required to increase the user privileges or to create the new MySQL user, respectively.

  • If a particular upgrade is not able to complete the Easy Upgrade process because it recommends that REDCap first be taken offline before executing the upgrade SQL script, the Easy Upgrade feature will still be able to auto-download the REDCap upgrade file, but it will redirect the administrator to the Upgrade Module to complete the upgrade manually. This will occur only a small minority of the time for an upgrade.

  • Once the Easy Upgrade feature has been successfully enabled, a cron job will check several times a day for any new REDCap versions that might have been released. If there are any new versions available, it will display a list of the versions at the top of the Control Center page to allow an administrator to choose the version to which to upgrade. The latest (most recent) version will be highlighted as the recommended upgrade path. If the REDCap installation is on the LTS branch, it will recommend the latest LTS version, whereas it will recommend the latest Standard Release version if the REDCap installation is on Standard Release. But regardless, the administrator will have control over which version to which they wish to upgrade.

  • Note: This feature will not be able to be used until another version of REDCap is released after this one (since this feature can only be used when there is an upgrade available).

  • Note: The Easy Upgrade feature cannot be used if the REDCap web server is using load balancing (multiple application servers). This is because the source code would only get downloaded to a single server (rather than to all of them) during the upgrade process.

• Improvement: For the error message that says "Your REDCap database structure is incorrect!", which is found on the Configuration Check page and also on the main Control Center "Notifications" page, if the "Easy Upgrade" feature has been activated in REDCap or if REDCap’s MySQL user has elevated privileges (e.g., CREATE, ALTER, DROP tables), it will display an "Auto-Fix" button in the red box that will allow administrators to automatically fix the database structure issues by simply clicking the button. This action is often much easier for users than executing the SQL in the database directly to fix this issue.

• Improvement: Regarding the green box that appears in the Control Center after a REDCap version directory has been loaded on the server, if it detects any other REDCap versions on the server that might be possible upgrade paths, it will list each one, and it will note if upgrading to that particular version would require taking REDCap offline temporarily for the upgrade or if the upgrade can be completed without taking REDCap offline.

• Improvement: Improved data export for biomedical ontology fields - If fields using the biomedical ontology auto-suggest feature are being exported to a stats package, it will now render those fields as multiple choice fields (rather than as free-form text fields) in the resulting stats package syntax file, in which all the cached choices for those ontologies will be output as separate choices (values and labels) for those fields in the syntax file. Note: Since some ontologies contain thousands of choices, all possible choices will not be output in the syntax file, but instead only the cached choices that have been saved in that REDCap project for those ontologies will be output as choices in the syntax file.

• Change/improvement: A new "Administrator Resources" section was added near the top of the Control Center's left-hand menu. It contains links to the REDCap Community site, the public Project REDCap site, and the REDCap Training Materials site.

• Major bug fix: If an Automated Survey Invitation has conditional logic containing a datediff() function that is explicitly using "now" as a parameter, the cron job that runs several times a day to trigger any datediff+now ASIs would mistakenly fail to schedule invitations for this ASI. Note: The issue does not exist for datediff+today ASIs but only for datediff+now ASIs. (Ticket #43783)

• Bug fix: When clicking the +- options at the top of a survey page to increase or decrease the font size of the survey text, in some cases with particular nested HTML tags, it would mistakenly compound the size changes unnecessarily, thus causing the font size to be too large or too small for some blocks of text.

• Bug fix: When downloading a "compact" PDF containing data, if a multiple choice field contains many choices (e.g., >20) it might mistakenly display only that field on a page by itself.

• Bug fix: When downloading the CSV file of users on the Browse Users page in the Control Center, it would mistakenly have the resulting filename ending with ".csv.csv" instead of just ".csv". (Ticket #43774)

• Bug fix: When referencing a repeating instance number in the conditional logic of an Automated Survey Invitation and then selecting a record using the "Test logic with a record" option, it would mistakenly cause a PHP fatal error. (Ticket #44104)

• Bug fix: When a user has De-identified data export privileges in a project and attempts to export a PDF containing data, in which MDY- or DMY-formatted date/datetime fields are being piped into labels in that PDF, then instead of the piped values being replaced with "[*DATA REMOVED*]" as expected, they would mistakenly be replaced with "00.00.0000 REMOVED*]". (Ticket #44123)

• Bug fix: If an external module has its configuration permissions set to "Require module-specific user privilege" on the External Modules page in the Control Center, then if a user in a project gives another user the rights to configure that module, it would save that setting correctly. However, if the user reloaded the User Rights page to edit that same user's rights again, it would mistakenly appear that the user no longer has config permissions for that module (i.e., the module's checkbox would be unchecked), even though they were just given such rights. (Ticket #44112)

• Bug fix: When using the [survey-queue-link] Smart Variable with custom text to display, in certain situations it may mistakenly cut off the first word of the custom text or not display the custom text at all. (Ticket #44224)

• Bug fix: When setting an account expiration time for a user on the Browse Users page (via "View User List By Criteria"), if the administrator's date format preference is set to Y-M-D on their My Profile page, then the pre-filled expiration time in the Set Account Expiration popup might mistakenly be in Y-M-D H:M:S format when instead it should only be in Y-M-D H:M format, thus throwing a date-formatting error when submitting the action. (Ticket #44228)

• Bug fix: If using MySQL 8.0 or later for REDCap's database, it would erroneously display the "database structure is incorrect" error in the Control Center when nothing is really incorrect about the database tables. (Ticket #42594)

• Bug fix: Minor changes to some database tables, which were mistakenly created with BTREE indexes, which is a type of index that is not compatible with some versions of MySQL or MariaDB.

Version 8.5.2 - (released 6/22/2018)

BUG FIXES & OTHER CHANGES:

• Improvement: The REDCap Mobile App v3.0 and later supports the Repeating Instruments and Events feature in REDCap projects. This version of the mobile app will be released on 6/22/2018 in the Google Play Store, and will also be released in the Apple App Store shortly thereafter (pending approval).

• Improvement: A new setting has been added to both "DDP Custom" and "DDP on FHIR" that, if enabled, will convert source system timestamps (i.e., dates of service associated with temporal fields such as labs) from GMT time into local/server time. If the source system (e.g., EHR) has temporal data with dates/times of service that are being output in Greenwich Mean Time (GMT), setting this option to 'Yes' will automatically correct all associated timestamps so that they appear in local time in the DDP adjudication popup. This option was added because some EHRs/external systems might output associated timestamps in GMT/UTC time rather than in local time. Note: This uses the server's timezone setting in PHP.INI to determine what the "local time" is. This option can be enabled at the bottom of the "DDP Custom" page or "DDP on FHIR with EHR Launch" page in the Control Center.

• Change: Added "Postal Code (France)" as a new field validation type.

• Bug fix: When clicking the "Download upgrade script" button in the REDCap Upgrade Module (as opposed to copy-and-pasting the contents of the textarea box on that page), the upgrade script would mistakenly be missing the SQL query "REPLACE INTO redcap_history_version...". This would not have any adverse effects on the systems though. (Ticket #43372)

• Bug fix: When viewing reports, the same SQL query would mistakenly get run many times unnecessarily, thus reducing performance on the report page. (Ticket #42764)

• Change: Extra protection has been added to the username/password form when using the E-signature feature on a data entry form in order to prevent browsers from auto-filling the username/password.

• Bug fix: When clicking the "Fix calcs now" button when viewing the results of Data Quality rule H, if the first instrument of an event is locked for a given record, then any calc fields existing on that same event (even on other instruments) would mistakenly not have their values fixed by DQ rule H. (Ticket #23433)

• Bug fix: Fixed incorrect instructions in an error on the Configuration Check page in the Control Center. (Ticket #43672)

• Bug fix: When exporting a Project XML file that contains multiple choice fields that have choice labels containing a "less than" sign followed immediately by a number or letter, it would mistakenly truncate that choice label in the XML file. (Ticket #43675)

Version 8.5.1 - (released 6/14/2018)

BUG FIXES & OTHER CHANGES:

• Medium security fix: A user access vulnerability was found in External Modules that have plugin pages that require authentication, in which a malicious user could potentially gain access to a module's plugin pages without having first logged in to REDCap (assuming the module installed in REDCap has plugin pages associated with it - many modules do not). This means that information displayed on that module page might be publicly accessible (able to be viewed without logging in) if a malicious user knows how to navigate to a particular External Module's plugin page and manipulate the query string URL in a very specific way. Note: This would not grant anyone access to other pages in the REDCap project but only to that particular module's plugin page to which they are manipulating the URL (i.e., standard REDCap pages are not affected by this; only module pages are vulnerable).

• Minor security fix: When using the Double Data Entry module and merging two records into a new third record, if a File Upload field has a file that has been uploaded for either record, then the merge process would mistakenly display a text box to allow the user to enter a value (such as a different Doc ID) for the File Upload field, which does not make sense to allow during the merge process. However, this could allow the user to inadvertently enter the Doc ID of a file to which they do not have access (in the current project or in another project to which they have access), thus allowing them to have unauthorized access to a file if they have some special knowledge regarding how REDCap stores documents. From now on, users are no longer given the option to enter a value for a File Upload field on the merge page, and thus they can only choose one of the two existing options. (Ticket #42221)

• Bug fix: Many project pages would not function at all if using MySQL version 8.0 or higher. (Ticket #42264)

• The outdated training video on Instrument Development was updated.

• Bug fix: When a calc field's value is being piped somewhere on the same form or survey page where the calc field is located, and if a Smart Variable is utilized in the calculation, then the calculated value might not get piped and propagated correctly when the page immediately loads. (Ticket #42687)

• Bug fix: When using WebDAV for file storage and uploading files larger than 2 GB in size, they would mistakenly fail to upload successfully. (Ticket #42416)

• Bug fix: When performing the EHR Launch for "DDP on FHIR", it might mistakenly display the erroneous error message "The 'state' parameter is incorrect!" for specific FHIR configurations. (Ticket #42583)

• Bug fix: When enabling the aggregate survey results display on a survey, if respondents are allowed to return to the survey without needing a return code, it would mistakenly still ask the respondent for a return code if returning directly to the aggregate survey results page. (Ticket #42568)

• Bug fix: The variable names of fields were mistakenly being displayed next to the field labels of fields on the survey's aggregate survey results page. It should not display the variable names on surveys but only on the "Stats & Charts" page within the project.

• Bug fix: When using the Dynamic Data Pull module (either DDP on FHIR or DDP Custom), the date comparison function for evaluating timestamps for temporal mapped fields might exclude some values if their timestamps fall right on the edge of the date range. This means that some values might mistakenly not appear in the list of DDP values to adjudicate from the EHR/source system. For this to occur would likely be rare. (Ticket #42444)

• Bug fix: Cross-event branching logic or calculations would mistakenly not evaluate correctly for unchecked checkboxes referenced on other events. (Ticket #42585)

• Change: For DDP on FHIR, 25 more LOINC lab codes were added to the DDP field mapping process.

• Bug fix: When using certain Smart Variables inside the query of an SQL field, if that SQL field's value is being piped somewhere on the same form or survey page where the field is located, then if the value of the SQL field has already been saved, the SQL field's value would mistakenly not get piped when the page loads but only when the field's value was modified again while on that page. (Ticket #41868)

• Bug fix: When a field's value is being piped into the field label of a required field, in which that required field is submitted on a survey or form without a value, the resulting popup error "Some fields are required!" would mistakenly display the pre-piped version of the field labels in the popup rather than performing the piping before displaying the labels. (Ticket #42577)

• Bug fix: When using the Data Search feature on the "Add/Edit Records" page in a longitudinal project, if a value is entered that has a match inside a record name (record ID field), then some of the options returned in the search would often not navigate the user to a data entry page when clicked but would instead mistakenly just reload the "Add/Edit Records" page. (Ticket #42965)

• Bug fix: When using the To-Do List to process a "move to production" request, in which the request has been moved to "low priority" status, it would display the erroneous error message "Error: Request not valid", thus preventing the administrator from processing the request. (Ticket #43036)

• Bug fix: Record names displayed in the Participant List would not wrap to the next line but would mistakenly get truncated, thus preventing users from viewing the full record name in some cases. (Ticket #43059)

• Bug fix: REDCap Messenger would mistakenly run in the background when using the EHR Launch functionality in the "DDP on FHIR" module. This could mistakenly lead to some JavaScript errors, which might get displayed in the EHR interface.

• Bug fix: When using AWS S3 or WebDAV for file storage, some uploaded files (even those imported via the API or Mobile App) might have a copy mistakenly left in the /redcap/temp/ directory on the web server under a random name, in which the temp files never get deleted. (Ticket #43127)

• Bug fix: For certain server configurations or directory structures, the Cron Jobs page in the Control Center might go into an infinite loop and never fully load the page. (Ticket #43144)

• Bug fix: If branching logic or calculations are used for a field on a survey page, in which the logic/calc references the current survey's Form Status field, it would mistakenly assume the Form Status value to always be "" (blank) rather than the true status value of 0, 1, or 2. This does not affect data entry forms but only survey pages.

• Change: When composing a survey invitation and clicking the "Preview" tab, instead of displaying the survey link as "Sample Survey Link" or "SURVEY TITLE", it now displays the actual survey title as the link text. Additionally, when clicking the "Send text email", this same thing now occurs in the email that is received. (Ticket #38955)

• Bug fix: The database variable "collation_connection" was not getting set correctly when initializing the database connection. In most cases, this would not affect anything at all since it would only affect institutions who had recently performed a fresh installation (not an upgrade) of REDCap 8.5.0 and then afterward migrated to a new server or upgraded MySQL in which the collation_connection setting in MY.CNF (or MY.INI) was different from the original server.

• Bug fix: If using custom link text for the Smart Variable [survey-link] when used inside a survey invitation's text, it would mistakenly fail to use the defined custom link text for the Smart Variable and instead would revert to using the survey title as the link text.

• Change: Added "Postal Code (Germany)" as a new field validation type.

Version 8.5.0 - (released 5/29/2018)

NEW FEATURES, BUG FIXES, & OTHER CHANGES:

• New feature: DDP on FHIR with EHR Launch

  • REDCap’s “DDP on FHIR with EHR Launch” feature provides the ability to launch a REDCap window while inside an EHR and to quickly and seamlessly import clinical data from the EHR into a REDCap project. As a built-in module in REDCap that can be enabled by an administrator, this feature can interface with any EHR system that has “SMART on FHIR” web services enabled.

  • What is DDP on FHIR? DDP on FHIR (Dynamic Data Pull from EHR) is a special feature for importing data into REDCap from an EHR (electronic health record system), such as Epic, Cerner, etc. It provides an adjudication process whereby REDCap users can approve all incoming data from the EHR before it is officially saved in their REDCap project. DDP on FHIR can only be enabled by a REDCap Administrator, so you should contact them if you wish to utilize DDP on FHIR for this project.

  • How the DDP on FHIR works: DDP on FHIR has the ability to fetch data from the EHR system both manually in real time and automatically at a regular interval. From the EHR interface, DDP on FHIR can create new records in a DDP-enabled REDCap project. Additionally, if a user knows the patient identifier (e.g. medical record number), then they could optionally enter the MRN for a record in a DDP-enabled REDCap project, after which it will then go and immediately retrieve the patient data from the EHR in real time.

  • For more documentation on “DDP on FHIR”, please see https://redcap.vanderbilt.edu/redcap_v8.5.0/Resources/misc/redcap_ddp_fhir_setup.zip To view a 5-min overview video of DDP, please see https://tinyurl.com/redcapddp (note: this video is not specific to DDP on FHIR since the video was originally created for DDP Custom years ago, but it contains most of the functionality in DDP on FHIR (i.e., it does not showcase the EHR Launch feature of DDP on FHIR).

• Improvement: PDF Customization Options – Users may change or remove the “Confidential” text displayed in the header of all PDFs in a project. Also, instead of displaying the REDCap logo and REDCap website URL at the bottom right of all PDF pages, they can instead choose to display the text “Powered by REDCap” in small font. These two settings are project-level, so they will be applied to every page of a PDF for all instruments in a project (for both forms and surveys). These settings can be found in the Additional Customizations popup on the Project Setup page. (Ticket #25326)

• Change/improvement: Protection has been added to help prevent the REDCap database connection's client character set (e.g., latin1, utf8, utf8mb4) from being affected 1) due to changes to the MY.CNF (or MY.INI for Windows) configuration file in MySQL, 2) due to a server upgrade, or 3) due to migrating to a new servers. The current database connection's client character set will be stored in the redcap_config database table, and if the client character set ever changes on its own due to one of the reasons above, REDCap will automatically keep using the existing character set from the redcap_config table in order to maintain the correct encoding to prevent data corruption.

• Change/improvement: New installations of REDCap will utilize utf8mb4 as the default character set for both the database columns (previously set to utf8[mb3]) and client connections (previously set to that of the database server), which is defined in the MY.CNF (or MY.INI for Windows) configuration file in MySQL, or set to latin1 if non-existent. This default has been changed because utf8mb4 encoding can allow for a greater variety of non-Latin characters to be stored in the database. Existing installations will not be able to utilize utf8mb4 encoding but instead will keep using their existing encoding (if other than utf8mb4).

• Bug fix: When installing REDCap, it would mistakenly not auto-set the value of the REDCap Base URL on the install page.

• Bug fix: If using MariaDB 10.2 (or higher) for the REDCap database, the REDCap Control Center would display the erroneous error message "Your REDCap database structure is incorrect!". (Ticket #28083, #32131, #41911)

• Bug fix: When using the "Add/Edit Branching Logic" popup in the Online Designer, if certain Smart Variables are used in the branching logic, and then the user selects a record from the "Test logic with a record" drop-down, it might display an erroneous message saying the the logic is not syntactically correct.

• Bug fix: When performing a data import of radio buttons in a matrix that has ranking enabled, it would sometimes display an erroneous error message if two or more matrixes of questions are being imported at one time, thus preventing the import from completing. (Ticket #39804)

• Bug fix: When using Dynamic Data Pull (either DDP Custom or DDP on FHIR) and the MRN field is being used as the Secondary Unique Field in the project, then if an MRN is entered on a form and the "Duplicate value!" error message popup is displayed, it would mistakenly not be possible to close the popup, thus causing the user to have to reload the page. (Ticket #41879)