DatStat Connect™ 2017.3

Home / Developer / IT / DatStat Connect™ Release Notes / DatStat Connect™ 2017.3

This applies to:

The DatStat Connect™ Platform

Search AcademySearch Academy
Contact UsContact Us


Release Date: October 13, 2017

This release of the DatStat Connect™ Platform introduces new features focused around data capture. All of the new features provide the platform users with new ways to capture and manage data either in Activities or on Participant Records. These new features include the ability to edit and delete submission data, the ability to view and download the data dictionary for an activity, and the ability to make participant fields campaign specific and protect the data in those fields behind campaign access permissions.

New Features

Participant PINs

A PIN is an optional alternative authentication mechanism that can be utilized by participants logging into applications. For example, after the first successful login into the Participant Portal support by the App Studio, participants returning to the portal can quickly enter a PIN instead of their username and password to securely enter their portal. Population Administrators can optionally configure PIN requirements around the complexity of participant PINs and participants can use their PIN numbers to securely access workflow items and patient portals. PINs provide a quicker and easier mechanism for participants to access items in the DatStat Connect Product Suite without compromising security.

Participant Campaign Fields

Campaign specific participant fields represent participant data specific to the context of the campaign they are configured for. They give Population Administrators the ability to organize participant data into relevant campaigns and even protect sensitive data required for one campaign from users in other campaigns. These fields can still be used in workflow configurations, including piping into emails and SMS messages, for the campaigns they were configured for and they can also still be pre-loaded into activities. End users are required to have permissions to a campaign in order to view and edit participant values for the fields configured for that campaign. With proper permissions users can also use campaign specific fields when querying submission data and when importing to create or update participants in the population.

Editing Submission Data

The ability to edit submission data is supported by the already existing submission data import feature. End users with the submission data edit permission will be able to use the familiar import feature to upload a file that represents a series of changes that need to be made to one or more submissions. Comments can be dictated in the import modal to explain the reason for the import which will be captured and stored alongside the entries in the audit log that track the data changes. This feature is accompanied by additional, related features intended to support FDA 21 CFR Part 11 compliance including a configurable electronic signature feature.

Deleting Submission Data

End users with the Delete permissions will be able to access delete buttons on individual submissions and delete them. All delete actions will be captured in the audit log. Deleting submissions allows normal users to remove any sessions that they might not want in the data set for a selected activity. When deleting a submission, the user is able to modify the status and reason of the task associated to that submission.

Data Dictionary

Population Administrators can view the Data Dictionary of any activity checked into the population in order to review it and distribute the activity variable definitions to interested parties. The Data Dictionary section contains tables for each collection in the activity and each table lists the variables configured within the representative collection. The user can quick-search through these tables to return results based on the variable names in order to quickly find variables of interest. Users can also view the definitions of all published activity versions for the activity including the definition of the current draft version. This allows the user to view explicit differences between the versions. Exporting the data dictionary to PDF allows the Population Administrator to distribute the dictionary to other users on the platform or to third parties requesting such information.


  • Participants are sent confirmation messages when they opt-in/out of SMS messages from their portal profiles.
  • API Users can update participant communication preferences for receiving emails or SMS messages over the API.
  • Participants can text certain keywords in response to SMS messages and receive a specific response or to opt-in/out of receiving SMS messages. Keywords include: STOP, UNSTOP, HELP, & INFO.
  • Population Administrators can configure information that will be used in one of the three specific messages that can be sent to participants when they are using SMS in their campaigns – these messages include an Opt-In Confirmation Message, an Opt-Out Confirmation Message, and a Help Response Message. The content that can be configured and are used in these messages includes the Program Name and Customer Care Contact Info.
  • Participant Campaigns keep track of communication preferences for participants in the campaign for whether or not the participant should be sent emails and SMS messages from email and SMS tasks in that campaign.
  • Population Administrators can configure email from addresses and SMS contact numbers at the campaign level, instead of the population level, to tie specific contacts to individual campaigns.
  • Population Administrators can configure default values for participant fields so that participants coming into the population can be given an initial state for a field before being evaluated for a more specific/appropriate value.
  • API Users can get aggregate counts and percentages of participant workflow items with each status over the API.
  • Users with participant workflow edit permissions can edit the expiration date of a step.
  • Population Administrators can configure enrollment conditions for campaigns to determine whether or not a participant is eligible for any of the workflows the campaign contains.
  • API Users can update a step’s status and expiration date and workflow’s status through the API.
  • API Users can enroll participants into new workflows through the API.
  • The text in the tables on the Submission Data details pages of a single submission are no longer truncated. The text now wraps as long as needed within its table cell in order to display all content so that users can read responses from this screen.
  • API Users can change user passwords through the API.
  • API Users can get all internal fields for a given population over the API.
  • API Users can get all internal fields and data for a given participant over the API.
  • API Users can update all internal field values for a given participant over the API.
  • Users are now shown more detailed error messaging when participant imports fail.
  • Both End users and Participants can view the data captured in an activity when that activity has a submitted status or the activity task has a closed status.


  • Fixed a bug that made participant fields configured as unique to be case insensitive, allowing for Apple and apple to be treated as unique values.
  • Fixed a bug that prevented population administrators from configuring workflow conditions with activity variables.
  • Fixed a bug that failed to show error messaging to end users when attempting to close a workflow with a complete status.
  • Fixed a bug that prevented population administrators from editing conditions on participant categories.
  • Fixed a bug that prevented participant categories from updating when the category configuration was changed.
  • Fixed a bug that caused steps to close before evaluating whether or not the participant should receive any additional tasks configured for that step.
  • Fixed a bug that prevented end users from being able to specify their own values for the internal Start Date and Submit Date variables when importing new submissions for an activity task.
  • Fixed a bug that prevented the product version from updating.
  • Fixed a bug that prevented population administrators from configuring workflow conditions with task statuses.
  • Fixed a bug that prevented the background service from enrolling participants into workflows that were configured to automatically enroll participants.
  • Fixed a bug that allowed population administrators to edit participant field and site names after participants had been introduced into the system.
  • Fixed a bug that caused a second opt-out confirmation message to be sent to participants that opted-out of SMS communications by texting STOP to the campaign SMS contact number.
  • Fixed a bug that prevented workflows from recurring at the time that they are configured to do so.
  • Fixed a bug that allowed invalid query conditions to run while throwing an internal server error.
  • Fixed a bug that prevented footer content from adjusting for pages with larger amount of content.
  • Fixed a bug that prevented the participant field section in queries from displaying the IDs and Datatypes.
  • Fixed a bug that prevented test emails in workflows from being sent.
  • Fixed a bug that caused certain footer sizes to overlap with the survey content on Internet Explorer.
  • Fixed a bug that allowed duplicate fields to be created when double clicking the Create Field button on Participant Fields page.
  • Fixed a bug that prevented population administrators from editing the Participant Table column configuration.
  • Fixed a bug that allowed users to save invalid or blank entries in Email From Address and prevented error messages from being displayed.
  • Fixed a bug that prevented error messages from being displayed when duplicate site names were saved while editing a site.
  • Fixed a bug that prevented error messages from being displayed when Label fields in Site pages are left blank when creating and editing a site.
  • Fixed a bug that prevented site names from showing up when editing or creating the permissions of a user.
  • Fixed a bug that prevented filters from resetting the date pickers in the tasks page when the Reset button is clicked.
  • Fixed a bug that allowed required fields to be moved to a campaign specific field group.
  • Fixed a bug that caused the system to enroll participants into two instances of a workflow when added manually.
  • Fixed a bug that caused the instance value of campaigns, workflows, steps, and tasks to be 0 when a participant is newly added to a workflow.
  • Fixed a bug that prevented users from dragging participant fields from one field group to another a field group on the participant fields page.
  • Fixed a bug that prevented filters configured on the User Permissions page from showing results of users with access to multiple sites or campaigns.
  • Fixed a bug that caused internal server errors in exceptions thrown in windows service.
  • Fixed a bug that prevented Decimal data type variables in the Activity Manager from working with show-if logics are configured.
  • Fixed a bug that caused the service to loop and continue to try and process thank you emails after failing the first time due to a missing email address.
  • Fixed a bug that allowed emails/SMS messages to be sent to recipients, even after being disabled.
  • Fixed a bug that caused database upgrade logic to not properly identify the latest run database upgrade script.
  • Fixed a bug that prevented users from configuring activities to use question numbering and represent questions with icons/images instead of numbers.
  • Fixed a bug that caused the Activity Manager default desktop icons to still match that of Illume Next.
  • Fixed a bug that prevented users from choosing years as an option for recurring workflows.
  • Fixed a bug that caused tables to shift and expand all the text in the description when checkbox is checked.
  • Fixed a bug that prevented users from moving forward without filling in a value for preload in the Activity Manager.
  • Fixed a bug that caused jumps in the activity to trigger when no data is provided for the variable used in the jump-if logic.
  • Fixed a bug that allowed users to save the password security page without specifying the minimum length field.
  • Fixed a bug that prevented error messages from showing when creating a new user without filling in any of the fields.
  • Fixed a bug that prevented users from viewing a survey session if the task that session was collected with has switched activities.
  • Fixed a bug that caused all the options to disappear from the view once the all the options in the section have been selected in the filter.
  • Fixed a bug that caused disabled participants to receive email/SMS task types, as well as invite, reminder, and thank you emails.
  • Fixed a bug that caused an internal server error resulting in the inability to create users using the Create User Modal from the Assign Users page.
  • Fixed a bug that caused long campaign descriptions to mess with the rendering of participant task view page.
  • Fixed a bug that caused the platform the break when the timezone is set to the system default on the coordinator profile.
  • Fixed a bug that prevented the configured amount of time to pass before adding the step and task for the workflow of the participant.
  • Fixed a bug that caused the text of workflow items with long names to wrap inside of the input field and not render the entire text.
  • Fixed a bug that caused multiple error messages to appear for instances of the use of pre-authenticated tags below the message body.
  • Fixed a bug that prevented users from moving an activity between systems, resources, and calculations while cloning an activity.
  • Fixed a bug that prevented error messages from showing when custom expression has an error for multiple conditions in the campaign entrance criteria.
  • Fixed a bug that allowed users to upload non-tab delimited .txt files and not return correct validation errors.

Known Issues

  • The add workflow option is still available when you first disable the participant; however, the workflow add fails because they are disabled.
  • Population Administrators can edit participant field and site names when there are participants in the system, which would in effect, cause an internal server error.
  • When participants opt-out by texting the campaign number, the product should not attempt to send an opt-out confirmation message, which is not going to get sent to the participant in any case since Plivo blocks any messages being sent after the opt-out.
  • Unassigning users from a population is taking too long and users are having to wait 30-60 seconds for the data-grid to refresh and update.
  • The user is prevented from saving when changing the display type of a field – that no participant currently has values for – from a Poplist to Textbox.
  • The minimum length configuration option for passwords does not save for big numbers and does not notify the user of the error.
  • The return URL does not work when users try to access a specific sub page when they are not logged in.
  • Changing the name of the participant field group in the participant fields page does not update the title in the data grid.
  • Leaving the timezone field blank in the locale settings is not displaying validation messages for the required field validations.
  • Changing the site ID is not saving or updating when configuring the site information in the sites tab of the security configuration.
  • When bulk editing user permissions, the names of the users are not being displayed.
  • Modifying the date picker in filters for the task grid does not update the drop down to custom.
  • Users can continue to save queries that contain participant field columns they don’t have permissions for.
  • Required participant fields are able to move to campaign specific field groups in the population and is still required after the move.
  • Tables in the Connect platform, such as one in the User Permissions under the security tab, are rendering as having multiple page results, even when there’s less than 50 results.
  • The version drop down list in the data dictionary section of an activity under the configure tab is ordered in ascending order (starting with the first/oldest version), but the ordering should be revered to have the latest/most current version to the top.
  • The domains of emails are being removed on Connect email tasks, which may remove credibility from the source.
  • When viewing search results in the data dictionary section of the selected activity, every collection shows an empty state message.
  • Pre-defined date ranges in filters for the tasks page do not automatically populate date pickers with values.
  • In the participant field group tab, once the vertical limit of the page has been reached, users cannot add any more groups due to the tab not being able to vertical scroll on the page.
  • Participants cannot be dragged into empty groups on the participant fields configuration page, at least one field needs to be present in the group in order for drag and drop to function.
  • Name-based quick search for user permissions and user groups tab under the security page does not return values based on full names.
  • In the workflow settings under the campaigns page, null values and values of 0 for the max recurrences field in “Recur When Workflow is Completed” and “Recur Based on Date” radio options save without an issue and later the radio selection to “This Workflow Does Not Recur”.
  • Deleting resources when creating a survey in the activities manager throws a 404 error, but seems to function correctly in deleting the resource.
  • For both steps and tasks, the count denominators will change when new steps/tasks are added and when existing steps/tasks are disabled.
  • Users cannot sort columns on the tasks table in population’s manage tab and only due date and last updated columns are sortable.
  • Failed emails due to incorrect piping do not show up in the email logs.