Version Changes

This page lists all relevant changes that have been made during a version release. It indicates the date installed or when it was released which will approximate the installation date. Bug fixes are not itemized as they are not relevant to this page but are indicated so that you are aware no new functionality or change has been made. Only changes that have been made over the past 12 months are shown.

Version 9.7.5 - (installed 2/24/2020)

BUG FIXES

Version 9.7.4 - (installed 2/24/2020)

BUG FIXES

Version 9.7.3 - (installed 2/13/2020)

BUG FIXES & OTHER CHANGES

CHANGE/ IMPROVEMENTS: Inclusion of the SweetAlert2 JavaScript framework for displaying custom dialogs. It is worth noting that Internet Explorer 9 and 10 are not supported by SweetAlert2. So if users are using IE 9 or 10, the SweetAlert dialogs will not be displayed for them.

CHANGE: To wean users off of using Internet Explorer 9 and 10, any users using IE 9 or 10 will see a thin, yellow banner at the top of all project pages, which will inform them that their browser is not fully compatible with REDCap and thus will encourage them to upgrade to IE11 or use another browser. Technically, IE 9 and 10 will be supported till July 2020 in Standard Release, but this warning is mostly preemptive in preparation for that.

Version 9.7.2 - (installed 2/10/2020)

BUG FIXES & OTHER CHANGES

CHANGE: When viewing reports, it now displays "report execution time" in seconds near the top of the report. This denotes the total server execution time that it took to create the report. Note: This does not account for the rendering time of the report (i.e., via JavaScript), which can sometimes take several seconds or more (if the report is large) for a user's web browser to actually render the report's HTML on the page.

Version 9.7.1 - (installed 2/10/2020)

BUG FIXES & OTHER CHANGES

CHANGE: In the Online Designer's Edit Field dialog, the text area boxes (field label, field choices, and action tags) are now slightly bigger and are all resizable.

Version 9.7.0 - (installed 2/10/2020)

BUG FIXES & OTHER CHANGES

NEW FEATURE: REDCap-branded URL Shortener (https://redcap.link)

  • The “Get short survey link” and “Create custom survey link” buttons on a project’s Public Survey Link page now utilize the REDCap-branded URL Shortener (https://redcap.link) instead of BIT.LY and IS.GD, which are third-party websites utilized by previous versions.
  • For administrators, a new “URL Shortener” link on the Control Center’s left-hand menu will take you to the “All-Purpose REDCap URL Shortener” page, which allows an admin to take *any* URL and shorten it as a custom redcap.link URL. We ask that you please try to limit the usage of this feature to only REDCap-related and work-related things.
  • NOTICE: Since this feature is ultimately supported by Vanderbilt, which pays for the hosting and infrastructure on AWS, it is a requirement that the REDCap server must have reported its REDCap stats to the consortium first in order to be able to use the REDCap URL Shortener. If the server’s REDCap stats have never been submitted, then the feature will return an error when attempting to create a redcap.link URL and will note this requirement in the error message.
  • To disable this feature and revert back to using BIT.LY and IS.GD for URL shortening for public survey links, you can run the following SQL query on your REDCap database: UPDATE redcap_config SET value = '0' WHERE field_name = 'enable_url_shortener_redcap';

CHANGE/ IMPROVEMENTS: By popular demand, the "Send test email" link/feature has been re-added to all the following places where emails are composed: Email Users page in the Control Center, Automated Survey Invitations setup dialog, Compose Survey Invitations dialog for Participant List, Compose Survey Invitation dialog at the top right of data entry form, and the Confirmation Email setting on the Survey Settings page.

CHANGE: In a production project where repeating instruments/events are enabled, if a user opens the Repeating Instrument/Event setup dialog on the Project Setup page, in which one or more checkboxes are checked already in the setup, a warning dialog with red text will be displayed to inform the user that unchecking any of the checkboxes might cause data to be orphaned and thus will cause any data already collected from repeating instances to disappear indefinitely from the user interface, reports, and exports. This warning will help users to be aware of this possibility that might affect their data and thus might have otherwise caused confusion.

Version 9.6.5 - (installed 2/10/2020)

BUG FIXES & OTHER CHANGES

IMPROVEMENT: Adaptive and Auto-scoring instruments (i.e., PROMIS assessments) that have been downloaded from the REDCap Shared Library may now have their survey responses deleted via the Delete button at the bottom of the data entry form when viewing the survey response. In previous versions, if an Adaptive and Auto-scoring instrument had been partially completed or the wrong one had been taking accidentally, there was no way to remove the existing response since the whole response was locked afterward. Now the "Delete data for THIS FORM only" button appears at the bottom to allow users to remove the response if they wish to add another to replace it.

Version 9.6.4 - (installed 2/10/2020)

BUG FIXES & OTHER CHANGES

IMPROVEMENT: If the "email notifications for administrators" option is enabled on the To-Do List page, then when a user cancels a "move project to production" request or a "delete production project" request, it now sends an email notification to the REDCap administrator to inform the admin that the request was cancelled so that the admin does not attempt to process it (even though the admin will be prevented with an error message if they try to process it). In previous versions, the request would have been cancelled silently by the user without ever notifying the admin.

Version 9.6.3 - (installed 1/23/2020)

BUG FIXES & OTHER CHANGES

IMPROVEMENT: The text box fields for logic have been increased in size and made resizable for the following places: the Survey Queue setup popup in the Online Designer, the Add/Edit Branching Logic popup in the Online Designer, and the Advanced Filter Logic when creating/editing reports.

Version 9.6.2 - (installed 1/23/2020)

BUG FIXES & IMPROVEMENT

IMPROVEMENT: New options for Alerts & Notifications

  • A “Trigger Limit” setting was added to Step 1 in the Add/Edit Alert popup that allows users to define where and to what extent within a record that the alert will be triggered. Its options include “only once per record”, “only once per event”, “only once per instrument regardless of the event”, and others that are displayed if the project contains repeating instruments/events. The trigger limit will help users to limit alerts to only be triggered on certain parts of a record and/or so many times within a record to achieve the behavior they desire for their notifications. Note: For non-longitudinal projects that do not have repeating instruments, this option (Step 1C) will not be displayed at all since it would contain only one choice: “only once per record”. (Ticket #70860).
  • The “every time” option of the “Send it how many times?” setting in Step 2 has been expanded to have sub-options to provide more possible scenarios in which an alert will be triggered. In previous versions, the only option was to set an alert to be triggered “every time the form/survey in Step 1B is saved”, but now it contains two new variations: “every time the form/survey in Step 1B is saved with new or modified data” and “every time the form/survey in Step 1B is saved with new or modified data (ignoring calc fields)”.
  • Recurrence maximum - When setting an alert to send multiple times in a recurring fashion in Step 2, a new option has been added to limit the maximum number of recurrences (i.e., the total times the alert will be sent on its repeated schedule). In previous versions, the alert would continue sending indefinitely at its defined interval (typically until conditional logic became no longer true), but now the alert can be set to repeat up to 9999 times at the interval that has been defined.

IMPROVEMENT: If the Custom Record Label and/or Secondary Unique Field are being used in a project, their values will now be displayed on the Calendar page when viewing the Day or Agenda tab for any calendar event connected to a record in the project.

CHANGE/ IMPROVEMENT: On the Alerts & Notifications page, users may now edit a deactivated alert. This is especially useful if a user is setting up part of an alert and wishes to make incremental edits to the alert prior to re-enabling it.

IMPROVEMENT: A new setting "Utilize the Display Name in all outgoing emails?" was added to the "Configuration for Outgoing Emails" section on the Control Center's "General Configuration" page. This setting allows administrators to disable the email Display Name feature in all outgoing emails from REDCap. This feature might need to be disabled if your institution is having a disproportionate amount of emails not being received due to email servers blocking them, sometimes due to the usage of the display name. This setting is enabled by default when upgrading or installing REDCap.

IMPROVEMENT: On the Clinical Data Interoperability Services (CDIS) page in the Control Center, a new helper popup was added to assist admins in quickly determining their EHR's "Patient Identifier String". A new button "Find patient identifier string" will appear on the page, and after clicking it, it will ask the administrator to enter the Social Security Number of any patient in the EHR system, which will return a list of all patient identifier strings that are available in the EHR. After finding the identifier string that corresponds to MRNs in the EHR system, that string can then be pasted and saved on that page so that the Clinical Data Mart and Clinical Data Pull services can begin functioning fully.

Version 9.6.1 - (installed 1/18/2020)

BUG FIXES

Version 9.6.0 - (installed 1/18/2020)

NEW FEATURE, BUG FIXES & OTHER CHANGES

NEW FEATURE: SMS and Voice Calls for Alerts & Notifications

  • If Twilio services have not been disabled at the system level for the REDCap installation, then users may now send a notification as an SMS text message and/or as a one-way voice call for any given alert in a project by setting them up on the Alerts & Notifications page.
  • The Twilio telephony services must first be enabled on the project on the Project Setup page (the same way it has in the past when utilizing Twilio for surveys and survey invitations), and once enabled, using the Twilio configuration dialog users may choose to utilize Twilio in the project for surveys (default), alerts, or both surveys and alerts.
  • Once enabled for alerts, inside the Add/Edit Alert dialog on the Alerts & Notifications page users will see the options to send a notification as an email, SMS message, or voice call. If SMS or voice call is chosen, it will hide all email-specific settings and will reveal the “Phone Number” fields for entering the phone numbers of one or more recipients of the notification, which may include the following: the phone numbers of all project users (from their My Profile account settings), any fields having integer validation or phone validation, and the survey participant’s phone number (if also using Twilio services for surveys).
  • Note: Just as when SMS messages are sent and when voice calls are made via Twilio for surveys, REDCap has a cron job that runs every 2 minutes that will automatically delete all logs on the Twilio website for any SMS messages sent or voice calls made via Alerts & Notifications. This is for privacy reasons to remove any potentially sensitive information (e.g., recipient phone numbers) that might be stored in Twilio’s logs.
  • New system-level settings for Alerts & Notifications have been added to the “Modules/Services Configuration” page in the Control Center that allow REDCap administrators to disable the phone-related settings listed below (similar to the ones that currently exist regarding email address usage in alerts). Note: These settings are enabled by default when upgrading to 9.6.0 or higher or when installing REDCap.
    • Option: “Allow normal users to use project variables for phone fields and integer fields in the project for an alert's recipient phone numbers?
    • Option: “Allow normal users to manually enter email addresses as freeform text for an alert's recipient phone numbers?”

CHANGE/ IMPROVEMENTS: Added four new redcap_log_event database tables for new projects to improve server performance when REDCap is querying logging data for a project. Note: This will not improve performance when querying the logging records of existing projects but only applies to projects created after upgrading to v9.6.0 or higher.

CHANGE/ IMPROVEMENTS: To protect the performance of the REDCap server, safeguards have been added to prevent users from running more than five Data Quality rules simultaneously for a given project. If this is detected, REDCap will automatically kill all but the newest five Data Quality rule requests that are still running and will display an error message on the page explaining this.

Version 9.5.3 - (installed 1/4/2020)

BUG FIXES & IMPROVEMENT

IMPROVEMENT: New content was added to the "Help & FAQ" page

Version 9.5.2 - (installed 1/4/2020)

NEW FEATURE, BUG FIXES & OTHER CHANGES

NEW FEATURE: Built-in activation process for external modules (system-level setting - enabled by default) All modules that have been set as “Discoverable” in the system will now have a “Request Activation” button displayed next to them when viewing the list of available modules on the External Modules page in a project. If a user with Project Setup/Design privileges in the project clicks the button, it will add a new item to the To-Do List in the Control Center (and also send an email to the REDCap administrator if admin email notifications are enabled) that will ask the admin to activate the module. Once the admin has activated the module for the user, the user will receive an email informing them that the module has been activated for the project. Note: This option can be disabled to hide this button for all discoverable modules (e.g., if you wish to use your own module activation process) at the top of the “Modules/Services Configuration” page in the Control Center.

NEW FEATURE: Users can self-activate an external module for a project. This will allow any user with Project Setup/Design privileges in a project to activate the module in their project on their own (i.e., without an administrator having to enable it for them).

IMPROVEMENTS AND CHANGES >WHEN EXPORTING DATA FROM REDCap INTO SAS: Full integration of the Missing Data Code functionality in the SAS data export syntax file to prevent issues when loading data containing Missing Data Codes into SAS. Note: The SAS Pathway Mapper file has been removed and is no longer utilized. Users exporting data to SAS will now need to manually modify the path of the CSV data file in their .SAS syntax file to reflect its locally saved path on the device.

Version 9.5.1 - (installed 12/15/2019)

BUG FIXES

Version 9.5.0 - (installed 12/8/2019)

BUG FIXES & OTHER CHANGES

NEW ACTION TAG: @HIDDEN-PDF - Hides the field only in the downloaded PDF of one or more instruments (including blank PDFs, PDFs with data, and compact PDFs with data). Note: Other @HIDDEN action tags will not hide fields inside PDF exports, so @HIDDEN-PDF must be used specifically to hide fields in PDFs.

IMPROVEMENT: More rich text editors - The rich text editor is now available when composing survey invitations. This includes composing Automated Survey Invitations or invitations to be sent via the Participant List or via the Survey Options on data entry forms.Improvement: The rich text editor is now available on the Email Users page in the Control Center and also for the Survey Confirmation Email option on the Survey Settings page.

Version 9.4.2 - (installed 11/26/2019)

IMPROVEMENTS & BUG FIXES

IMPROVEMENT: Line breaks may be preserved in data values in CSV data exports - When creating/editing a report, the section "Additional report options" contains a new setting: "Remove line breaks/carriage returns in all text data values (only applicable for CSV Raw and CSV Label data exports)". This setting will be enabled by default for all existing reports and for any new reports being created. The option will effectively not be enabled when exporting Reports A and B in order to be consistent with their current behavior in previous versions. This option is only used for CSV data exports and not for reports or exports to statistical analysis packages.

IMPROVEMENT: Added “Copy” and “Paste” options to the [right-click] context menu for all rich text editors.

Version 9.4.1 - (installed 11/16/2019)

IMPROVEMENTS, BUG FIXES, & OTHER CHANGES

IMPROVEMENT: A custom email “display name” can be set for the email sender when sending an email for Alerts & Notifications, the Survey Email Confirmation option on the Survey Settings page, and when sending survey invitations via Automated Survey Invitations, via the Participant List, or via the Compose Invitation option on a data entry form.

IMPROVEMENT: The email “display name” for most outgoing emails is now automatically populated and thus is able to be displayed in the recipient’s email client. Previous versions did not use the display name but left it blank for outgoing emails. For user requests that are triggered by users, such as production change requests, API token requests, etc., the user’s first and last name from their My Profile page will be used automatically as the display name in those emails. For emails originating from REDCap administrators that are automated by the system, the email display name will the “Name of REDCap Administrator” setting (from the General Configuration page) or else the “Contact name to display on Home page” (from the Home Page Configuration page), which is dependent upon the type of email being sent.

IMPROVEMENT: New system-level setting “Suppress usage of the Universal FROM Email address for specified email domains” on the General Configuration page - If the setting “Universal FROM Email address” is enabled for the system, then the Universal FROM Email address will be used for all outgoing emails. But if one or more domain names (e.g., vanderbilt.edu) are specified for “Suppress usage of the Universal FROM Email address for specified email domains”, then the Universal FROM Email address will NOT be used for any outgoing emails in which the FROM/sender's email address matches one of those domains. Instead the FROM/sender's email address will remain as-is.

IMPROVEMENT: The module/plugin method REDCap::email now has new parameters that can be passed to it: BCC, FromName, and Attachments. The parameter BCC represents the email address of someone being BCC'd on the email (if using more than one email address, they must be separated by commas and/or semicolons). The parameter FromName represents the sender's email display name that will be displayed in the recipient's email client next to the sender's email address (e.g., "Rob Taylor"). And the parameter Attachments should be an array of one or more file attachments, in which the array keys will represent the file name as seen in the email client and the corresponding array values will represent the full file path of the attachment file on the REDCap server. A new example is provided on the "Developer methods for Plugins, Hooks, & External Modules" page to illustrate how to use these new parameters.

CHANGE: The popup for displaying Project Notes on the My Projects page might not behave correctly under certain conditions. It is now displayed in a better format to avoid these issues.

Version 9.4.0 - (installed 11/12/2019)

NEW FEATURES, BUG FIXES, & OTHER CHANGES

NEW FEATURE: Missing Data Codes (i.e., “Data Missingness” functionality) (project-level setting)

  • Fields that have a blank/missing value may be marked with a custom 'Missing Data Code' to note why the value is blank. These missing codes may be used to aid in data analysis by specifying why a field lacks a value. Users may enable custom missing data codes at the project-level in the Additional Customizations popup on the Project Setup page. The missing codes should be coded just like the choices of a multiple choice field with code + comma + label, in which the codes can only have letters, numbers, dots, dashes, and underscores (e.g., '-999, Not asked' or 'UNK, Unknown'). If no codes are entered, this feature will remain disabled. After missing data codes have been set up in a project, you will see an 'M' icon next to each field when viewing a data entry form. Click the icon to open your list of missing data codes, and select one. Once selected, it will save the missing code as the literal data value for the field. Missing data codes can be used for any field type (e.g., date, slider, file upload fields).
  • If utilizing missing data codes, the functionality will be enabled on all fields by default, and the code will be saved as the literal data value for the field.
  • New action tag @NOMISSING can disable the missing data option for a given field
  • Behavior with branching logic – If a field should be hidden by branching logic, REDCap will ask the user (except on surveys) if they wish to delete the value of the field being hidden. But if the field has a missing data code saved for it, it will still hide the field but will not remove the missing data code as the field’s value. This allows a field to still be “blank” and have a missing code while being hidden by branching logic.
  • New isblankormissingcode() function for branching logic, logic, and calculations - Returns a boolean (true or false) if the field value is blank/null/"" or if the value is a Missing Data Code, in which Missing Data Codes have been explicitly defined in the project on the Project Setup page under Additional Customizations. E.g. isblankormissingcode([age]), in which if "age" has a value of "UNK" (which might be a Missing Data Code in a project), then it will return TRUE. And if the field has any non-blank/non-null value that is also not a Missing Data Code, it will return FALSE.
  • Missing data codes can be imported via API, Data Import Tool, or REDCap::saveData (for plugins/hooks/modules)
  • All the missing data codes are displayed for reference at the top of the Codebook page
  • When creating/editing a report, a new option exists under the “Addition report options” section: “Display any Missing Data Codes in place of blank values (where applicable)”. This option will allow users (based on their preference) to show or not show the Missing Data Codes (if they have been saved for any field in any record) in the report or export.Note: In PDF exports of data collection instruments, any Missing Data Codes will be represented as blank values in the PDF.
  • Changes for Data Quality Rules
    • DQ rule A and B (for finding blank values) will continue to return only truly blank values and thus will not return fields with missing data codes saved as the value.
    • New rule - DQ “Rule I (Fields containing missing data codes)” has been added as a new rule for specifically finding fields with missing data codes saved as the value.
    • DQ rule F (Hidden fields that contain values) will ignore fields that have a missing data code saved as the value because it is allowable for such fields to be hidden by branching logic while still maintaining a missing data code as a value.

IMPROVEMENT: If the Clinical Data Mart has been enabled for the system, the Control Center's System Statistics page now lists the following stats related to Data Mart under the "Modules Utilized" section: 1) Records with data values imported via Data Mart, and 2) Projects with data values imported via Data Mart.

IMPROVEMENT/ CHANGE: If a user is viewing a data entry form that has been enabled as a survey and then clicks "Compose survey invitation" in the survey options at the top right of the page, if they compose and send an invitation that is marked to be sent "Immediately", it will display a popup to inform the user that it is recommended that they leave the page very soon before the respondent has a chance to enter any data on the survey page. This is done because if the respondent begins entering data on the survey immediately after receiving the invitation, and then the user (while still viewing the data entry form) saves the form, the user could unwittingly erase the respondent's data values that were just entered.

CHANGE: When enabling the Twilio telephony services in a project, REDCap no longer performs a check to ensure that Twilio's "Request Inspector" feature is disabled. Due to technical issues with not being able to automatically disable the Request Inspector via Twilio's API for some REDCap server configurations, REDCap no longer forces the Request Inspector to be disabled but instead provides text to inform users during the Twilio setup process that it is *highly* recommended that they disable the Request Inspector manually in their Twilio account (especially if collecting identifying information) and provides information on where/how to do such.

CHANGE: REDCap now utilizes PHPMailer for all emails sent out.

IMPROVEMENT/ CHANGE: If the Universal “From” Email Address option is being utilized for the system, the sender’s email address now gets set as the Display Name in the email received. In previous versions, no Display Name is ever set for outgoing emails. So instead of the recipient only seeing that the sender is no-reply@vumc.org (assuming this to be the catch-all universal address, for example), it instead will appear to be from “joe.user@gmail.com . This is an improvement because it provides the recipient with more context with regard to who the sender is.@vumc.org>

Version 9.3.8 - (installed 11/4/2019)

BUG FIXES

Version 9.3.7 - (installed 10/28/2019)

IMPROVEMENT: Major performance improvement when loading the Participant List page for projects with surveys. For projects with thousands of records or more, this page should be significantly faster.

IMPROVEMENT: Performance improvement for record searching on the "Add/Edit Records" page when entering part of a record name in the "Enter a new or existing [Record ID]" text box. For projects with thousands of records or more, this functionality should be much faster.

IMPROVEMENT: Performance improvement for projects using record auto-numbering, in which the process of generating the record name of the next potential record is much faster, especially for projects with many records.

CHANGE: Performance improvement for projects using record auto-numbering, in which the process of generating the record name of the next potential record is much faster, especially for projects with many records.

Version 9.3.6 - (installed 10/21/2019)

IMPROVEMENT: Performance improvement for large data exports that might have previously taxed the REDCap servers or might have failed to complete altogether for some large projects. An internal auto-batching mechanism is now utilized to limit the performance hit to the servers (both database and web server) when exporting large quantities of data (via API or user interface) in order to improve the user experience and to prevent REDCap processes from using up too many server resources. Note: This does not necessarily mean that data exports will be faster; in fact, some exports might be slightly slower as a means of preserving server resources used by REDCap processes.

IMPROVEMENT: Performance improvement for when REDCap is generating the record list cache for a project, especially for projects with Data Access Groups. For each project, REDCap maintains a record list in a database table that is used throughout a project. This record list improves overall performance, especially for large projects. Every few days the record list cache is automatically rebuilt internally. The process of rebuilding the record list is now more efficient, faster, and less error-prone than in previous versions.

IMPROVEMENT/CHANGE: The Codebook now denotes if an instrument is enabled as a survey, in which it is noted immediately to the right of the instrument name.

Version 9.3.5 - (installed 10/4/2019)

BUG FIXES

Version 9.3.4 - (installed 9/26/2019)

BUG FIXES

Version 9.3.3 - (installed 9/11/2019)

BUG FIXES

Version 9.3.2 - (installed 9/9/2019)

BUG FIXES

Version 9.3.1 - (installed 9/3/2019)

BUG FIXES

Version 9.3.0 - (installed 8/15/2019)

NEW FEATURE: File Version History for File Upload fields (project-level setting)
This feature allows a new file to be uploaded onto a File Upload field that already has a file uploaded for it. If a file has already been uploaded, the field will have a new link “Upload new version”, and after being clicked, it will allow the user to upload another file without having to delete the existing one. The old/existing file will not be deleted but will still be accessible as an older version of that file in the Data History popup (by clicking the “H” icon next to the field). Within the Data History popup, a user may view, download, or delete any existing version of the file that exists, in which all versions of the file will be displayed in a table format and listed in chronological order with regard to being uploaded.

“Import File” API behavior: When the File Version History feature is enabled for a project, and the “Import File” API method is used to import a file into a File Upload field that already has a file saved for it, the new file will overwrite the existing file but keep the existing file in the File Version History, thus not deleting it. This is different for projects that have the File Version History disabled, in which importing a new file will delete the existing file.

IMPROVEMENT: The Data History Popup for File Upload fields now provides more detailed information, such as the filename of the uploaded file.

SECURITY/BUG FIXES

Version 9.2.5 - (installed 8/2/2019)

BUG FIXES

Version 9.2.4 - (installed 7/28/2019)

BUG FIXES

Version 9.2.3 - (installed 7/25/2019)

BUG FIXES

Version 9.2.2 - (installed 7/23/2019)

BUG FIXES

Version 9.2.1 - (installed 7/15/2019)

BUG FIXES

Version 9.2.0 - (installed 7/12/2019)

NEW FEATURES, BUG FIXES, & OTHER CHANGES

10 NEW SMART VARIABLES

[project-id] The Project ID (i.e., PID) of the current REDCap project.
[user-fullname] The current user's first and last name (as listed on their My Profile page).
[user-email] The current user's primary email address (as listed on their My Profile page).
[redcap-base-url] The base web address for the REDCap installation.
[redcap-version] The current REDCap version number of the REDCap installation.
[redcap-version-url] The base web address of the current REDCap version directory for the REDCap installation.
[survey-base-url] The base web address for surveys for the REDCap installation.
[instrument-name] The unique instrument name of the current survey or data entry form. It will return a blank value if not in an instrument context.
[instrument-label] The instrument label of the current survey or data entry form. It will return a blank value if not in an instrument context.
[survey-title] The survey title of the instrument specified by the 'instrument' parameter (if provided). If the 'instrument' parameter is not provided, the current survey instrument will be used, else it will return a blank value if not in an instrument/survey context.

4 NEW ACTION TAGS

@NOW_SERVER Loads the REDCap server's date+time into a blank Text field - similar to the @TODAY tag but additionally includes the time portion. If the field has validation, the value will adjust to match the date format. NOTE: The time used will be the REDCap server's local time, which might be different from the user's local time if in another timezone. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field.
@TODAY_SERVER Loads the REDCap server's date into a blank Text field - similar to the @NOW tag but without the time portion. If the field has validation, the value will adjust to match the date format. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field.
@NOW_UTC Loads the current UTC/GMT date+time into a blank Text field - similar to the @TODAY tag but additionally includes the time portion. If the field has validation, the value will adjust to match the date format. NOTE: The time used will be the current UTC/GMT time, which might be different from the user's local time if in another timezone. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field.
@TODAY_UTC Loads the current UTC/GMT date into a blank Text field - similar to the @NOW tag but without the time portion. If the field has validation, the value will adjust to match the date format. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field.

Version 9.1.2 - (installed 7/3/2019)

BUG FIXES, & OTHER CHANGES

NEW FEATURE: RICH TEXT EDITOR FOR FIELD LABELS AND SECTION HEADERS
For any field on an instrument in the Online Designer, users may optionally utilize the rich text editor for styling field labels or section headers with many text-formatting options. The rich text editor allows users to change the color of text (including background color), create tables, add text of varying sizes, bullet lists, and more. For any field labels that were originally created without the rich text editor, users may optionally enable the rich text editor for any field by clicking the 'Use the Rich Text Editor' checkbox. It may also be disabled afterward at any time just the same. Rich text is enabled by default for any new fields being created via the Online Designer.

NOTE: The PDF export of surveys/instruments will NOT reflect all the styling of the rich text editor, so keep in mind that line breaks and paragraphs should be represented well in PDFs, but other text-formatting options, such as large text, bullet points, and colors are not able to be translated into the PDF export of the instrument. This is a current limitation in REDCap.

Version 9.1.1 - (released 6/21/2019)

BUG FIXES

Version 9.1.0 - (released 5/30/2019)

BUG FIXES & CHANGES

NEW FEATURE: CLINICAL DATA MART
The Data Mart module can pull clinical data from the EHR in bulk (i.e., dozens or hundreds of patients at once), as compared with the Clinical Data Pull (CDP) that pulls patient data from the EHR just one patient at a time. Both Data Mart and CDP utilize REDCap’s “Clinical Data Interoperability Services” infrastructure, which can interface with any EHR system that has FHIR web services enabled. If CDP has already been set up and enabled in REDCap, then enabling Data Mart is very simple and requires no further setup other than enabling it on the CDIS page in the Control Center. This is not available for REDCap users at this time, but we want to ensure you are aware of its existence.

Version 9.0.3 - (released 5/24/2019)

BUG FIXES & CHANGES

Version 9.0.2 - (released 5/17/2019)

IMPROVEMENT: On the Alerts & Notifications page, the email "From" address is now displayed in the right-hand Email box for each alert.

Version 9.0.1 - (released 5/10/2019)

BUG FIXES & CHANGES

CHANGE: Replaced many of the older icons in the user interface with Font Awesome icons, especially on the left-hand project menu and left-hand Control Center menu.

CHANGE: Consolidated the two project pages “Record Locking Customization” and “E-signature and Locking Mgmt” into a single two-tabbed page named ”Customize & Manage Locking/E-signatures”. NOTE: If user only has access to one of these pages, they will simply not see the other page/tab.

Version 9.0.0 - (released 5/3/2019)

NEW FEATURES, BUG FIXES, & OTHER CHANGES

NEW FEATURE: ALERTS & NOTIFICATIONS
The Alerts & Notifications feature allows you to construct alerts and send customized email notifications. These notifications may be sent to one or more recipients and can be triggered or scheduled when a form/survey is saved and/or based on conditional logic whenever data is saved or imported. When adding/editing an alert, you will need to 1) set how the alert gets triggered, 2) define when the notification should be sent (including how many times), and 3) specify the recipient, sender, message text, and other settings for the notification. For the message, you may utilize customized options such as rich text, the piping of field variables (including Smart Variables), and uploading multiple file attachments. While similar in many respects to Automated Survey Invitations, Alerts & Notifications allow for greater complexity and have more capabilities. For example, alerts apply to both data entry forms and surveys, and they also allow for more options regarding who can be the recipient of a notification (project users, survey participants, etc.).

System-level permission settings – On the “Modules/Services Configuration” page in the Control Center (at bottom of page), administrators may adjust the settings that determine if normal users are able to use email field variables in an alert’s To/CC/BCC field and/or use email addresses entered manually as freeform text into an alert’s To/CC/BCC field. These settings will be determined based on the comfort level and/or policy of the local REDCap institution. By default, REDCap will allow normal users to use email fields and freeform text emails (i.e., both are enabled by default), but this can be easily changed immediately after installation or upgrading. Additionally, if Yes is chosen for allowing freeform emails to be entered, the admin may limit those emails to a specific whitelist of email domain names (e.g., vumc.org, mmc.edu) to provide some additional restriction there.

Converting existing Email Alerts into Alerts & Notifications – If your REDCap installation currently has the Email Alerts external module installed and is being used in projects, there will be an option (a green button) at the top left of the Email Alerts configuration page to convert all the Email Alerts in a given project into Alerts & Notifications. This is an opt-in setting, and must be done for each project one at a time. It will present a dialog popup with information so that the user understands that there are some differences between EA and A&N, but overall, everything will be able to be converted, although the alerts might look slightly different afterward as A&N’s. Once the Email Alerts are converted, the Email Alerts module will be automatically disabled for the project, and the user will be redirected to the A&N page.

The conversion instructions notes that if (for whatever reason) the A&N’s are not behaving like the user anticipated, they can easily revert back to using Email Alerts again by 1) deactivating all the A&N’s that were created from the conversion, and 2) have an administrator re-enable the Email Alerts module.

IMPROVEMENT: The rich text editors on the Survey Settings page have now been updated to a newer version of the TinyMCE package. NOTE: IE9 and IE10 will still use the older version of the rich text editor because they are not compatible with the newer one.

IMPROVEMENT: New records can now be created directly from the Record Status Dashboard. If record auto-numbering is enabled, it will display an “Add new record” button, otherwise it will display a text field for users to enter a new record name to create.

IMPROVEMENT: Links to the Online Designer, Data Dictionary Upload page, and Codebook were added to the left-hand project menu for easier navigation. Also, a new section “Project Home and Design” was added on the left-hand menu to contain all these links, as well as the Project Home and Project Setup page links.

CHANGE: The Quick Tasks box on the Project Home page was removed since all the pages listed inside it are now located on the left-hand project menu, thus making the Quick Tasks box redundant.

Version 8.11.11 - (released 4/26/2019)

BUG FIXES & OTHER CHANGES

Version 8.11.10 - (released 4/19/2019)

BUG FIXES & OTHER CHANGES

CHANGE: The Data History Widget on data entry pages now displays the "seconds" component of the "Date/Time of Change" timestamp for when the data value was added/modified. This allows users to view the logging items with greater granularity for when data changes are made in narrow windows of time.

Version 8.11.9 - (released 4/12/2019)

BUG FIXES

Version 8.11.8 - (released 4/4/2019)

BUG FIXES

Version 8.11.7 - (released 3/24/2019)

BUG FIXES

Version 8.11.6 - (released 3/15/2019)

BUG FIXES

Version 8.11.5 - (released 2/21/2019)

BUG FIXES

Version 8.11.4 - (released 2/15/2019)

BUG FIXES