Release Notes: Illume v5.1.1.19546

Home / Developer / IT / DatStat Illume Release Notes / Release Notes: Illume v5.1.1.19546

This applies to:

Illume 5
Discovery
Data Change

Search AcademySearch Academy
Contact UsContact Us

Introduction

Release Date: January 8, 2016

This maintenance release was primarily focused around bug fixes for the Illume 5 product. Six bugs were fixed all of which dealt with Section 508 Accessibility standards within the classic rendering of Illume surveys.

This release also includes a few new features primarily to improve email processing and access to DatStat data through the API and Audit Utility.

New Features

  • The Rebex .NET component has been upgraded to the latest version so that email processing within Illume is more efficient.
  • When viewing the audit logs in Data Change, datagrid columns that identify users in the system now identify users by their usernames instead of their GUIDs.
  • Email Jobs are now processed asynchronously increasing email send performance.
  • The REST API survey results route now includes the previously hidden internal variables of ParticipantID, DiscoveryID, and UserID and a field has been added to the SurveyResults object to identify which variables map to which response values.
  • Users can now use the Audit Utility to pull the full audit history for all participants using the friendly name of a participant list or a survey.

Resolved Bugs

Illume

  • Question Tables and Multi-Control Questions properly label inputs within the cells of the tables with the response options that are used as the table headers so that these question types can now be configured to be 508 compliant.
  • The offline installer for the desktop client now allows the user to upgrade their desktop client to the latest version without having to uninstall the previous version.
  • By default, the Survey Title in surveys now uses H1 header tags in its HTML to appropriately designate the text as the page heading in accordance with 508 compliant guidelines.
  • All default text styling in surveys now has a 3:1 contrast ratio with the default survey background color as recommended by 508 compliant guidelines.
  • The progress bar is no longer included in the survey header by default.
  • Survey HTML now uses the lang attribute on the opening HTML tag to appropriately identify the language of the survey in accordance with 508 compliance guidelines.

Known Issues

  • Illume Installs with 500 or more surveys can’t see all of their surveys in the Data Change Module
  • The Survey Comments Summary feature in the desktop client does not display survey comments in the Review All Comments list.
  • Data Import fails when you have participant properties with defaults that are not defined in your import file
  • The report for failed participant assign actions is not detailed enough to inform the user of what they need to correct in order to retry the import successfully.
  • Participant fields created using data import cannot be added to data grid views until the user logs out and back in to the system.
  • “Last modified by name” column header uses the database column name instead of the end user label in Discovery.
  • Hidden properties should be hidden from all data grids, not just the data grids when viewing participants.
  • Individual column filters for a datagrid in Data Change are not always blank by default.
  • Unique state of properties in the Import participants modal Duplicate Participant Warnings section do not match configured states.
  • Data Change feature is not disabled when Data Change is not enabled in the license.
  • Improper dropdown menu shown while copying nested tasks.
  • The Reports table in Data Manager does not display the owner of reports listed in the table until the report has been published and the user logs out and back in to the system.
  • Assign actions should be removed when the participant list for the action group is changed.
  • Default values specified for participant list columns should not be able to have different data types that that of their questions.
  • Hidden tag is not supported for use with check all that apply questions.
  • Participant address remains in the participant information section of the participant details page even when the “Set participant properties” checkbox is unchecked.
  • When view the Scheduled Task Execute Events tab under the Study Task Events section, the message should say “No scheduled task execute events defined” instead of “No scheduled task runtime events defined.”
  • Text objects/headers in question tables cannot be copied and pasted.
  • Minimize, maximize, and close buttons are not available on data dictionary window when viewing the data dictionary from the survey manager.
  • Participant Assign Action on save shows the Study Arm GUID Value instead of the Study Arm Name.
  • Multiple workflow events can be added to study task, and milestone event sections if the user clicks the Add Workflow Event icon and closes the modal without clicking save several times in row without refreshing the page.
  • The value of Question Response Percentage does not take skipped questions into consideration when calculating.
  • Participant data properties cannot be used for survey authentication.
  • SDK GetResponseDataType does not return accurate information when variables does not exist in the survey.
  • Special characters (%$#) used in file names cannot be referenced from survey resources.
  • Selecting the “Resource” option in the style editor for Backgroundimage without adding a resource causes an exception.
  • When viewing an individual session data in the web console, if the survey contains loops only data from the first iteration of the loop is shown.
  • The Showif tag allows users to apply showif login for content inline, currently is a user embeds a piping tag with the statement only the inner tab is evaluated.
  • Add validation error for invalid variables in a loop summary tables.
  • Checking in a template file allows you to try and publish it to your system as a survey.
  • When using filters in Illume the “Equals to” operator throws an error if the user tries to use it to compare a Date to a Date/Time.
  • Users receive an unclear error message when trying to change the data type of a participant property that is already in use by participants on the participant list.
  • Calculations that are of type whole number cannot be piped into other question fields that are text data types.
  • Users receive an internal server error when trying to manually view a submission that has had its participant list deleted.
  • Getting an error when trying to delete a study with excessive status codes.