DatStat Connect™ 2018.2

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

This applies to:

The DatStat Connect™ Platform

Search AcademySearch Academy
Contact UsContact Us

Introduction

Release Date: May 18, 2018

This release of the DatStat Connect™ Platform focuses on introducing new features that allow users configuring populations to better reach the individuals in those populations as well as provides tools to allow users to test their configurations. The new features for these two goals include: the ability to configure workflow events, multi-lingual activities, randomization of questions and response options, activity tasks that allow for daily submissions, test populations with test participants and test data, and the ability to delete campaign items. Other new features include: allowing users to reset forgotten passwords via email and configuring data sets to compile data across activities and download for use outside the system.

New Features

Workflow Events

A workflow event is an action that the server will perform at a specified time such as campaign enrollment, workflow start or close, step start or close, or task start or close. There are two types of workflow events available with this release: 1) updating a participant field with a value from a list and 2) adding a campaign level task to a participant. The Participant Field Update From List event requires that a list be configured for the campaign. A list is simply a list of values that all have the same data type and the values are imported into the system by the user. When configuring the participant field update from list event, the user simply chooses a list from which to pull the next available value and a participant field into which to place that value. The Add Task event requires that a campaign level task be configured, which is simply a task that exists outside of the normal step and workflow structure. When configuring this event, the user simply selects the task that they wish to be added. All events can be configured with a set of conditions that determine whether or not it is appropriate for that event to occur at the specified time.

Multi-Lingual Activities

Platform Administrators can configure a list of supported languages for the system on the Locale page under Settings. This list determines what options are available to participants on the Language field as well as what languages are available when configuring activity content. Users configuring activities can decide to configure an activity in multiple languages by enabling a language from the list of supported languages from the platform and configuring the text for that language as well as in English as they create questions and text content in the activity. When an activity with multiple languages is checked in to the platform, users can view the data dictionary for that activity in each specified language. Once that activity is published and used in workflow, the language of the activity will be determined by the selected language of the participant that is logging in. If configured, users and participants can change the language of an activity from within the activity itself.

Randomization of Questions and Response Options

Users configuring activities can configure collections to randomize the items within the collection so that the questions show in a completely random order or randomly show in reverse order. Individual items within a collection can be anchored into a specified position so that a question is always the first question on the page even though the rest of the questions show in a random order. Questions with response options can also be configured to show their response options in a random order or randomly in reverse order and similarly to individual questions, individual response options can also be anchored into a specified position. The random order of questions and response options is maintained across multiple sessions, meaning that when a participant logs into an activity they will be shown questions in a random order and when they return to that activity, the questions will be shown in the same random order and before, the items are not randomized each time the participant logs in.

Daily Activity Tasks

Activity tasks can now be configured as campaign level tasks and/or to allow multiple submissions to a single task. A campaign level task is simply a task that does not live within the step and workflow structure; it can be added to a participant to do along side any workflows that they may be doing and not be restricted by the timeline of those workflows. These campaign level tasks, as well as activity tasks within workflows, can be configured to allow daily submissions by changing the submission frequency from Single Submission to Daily Submission. This will allow the user to configure what days during the week the task is able to take submissions, the time frame each day that the task is able to take submissions, and the due date of the task after which the task will stop taking submissions. Daily activity tasks are shown on the Tasks page and on the Participant Record page along with all other tasks and task types. The primary difference between a daily task and other tasks is that the editable details are a little different and include available days and submission windows and the user can view a submission history for a selected daily task that shows them the number of submitted/partial/missed submissions the participant has and which dates each of those falls on.

Test Populations

Users can be given permissions to the Test Population within the platform which will allow them to create test participants with which to test their campaign configurations and activity configurations as well as troubleshoot any issues being experienced by live participants. The test population, participants, and data are all stored separately from their live counterparts and cannot be converted from live to test or vice versa in order to ensure that live data stay un-impacted by testing activities. Test data can be purged from the system simply by deleting all of the test participants from the test population, as this will trigger a cascading effect where the test data and participant campaigns are also deleted from the system.

Deleting Population Items

Population Administrators can delete population items such as participant field groups, campaigns, workflows, steps, tasks, and activities. Removing unused population configuration items allows users to better organize and maintain their platform configurations. Each item has it’s own limitations on when it can and cannot be deleted, but generally, if the item is in use in any way then it cannot be deleted. This helps prevent 

Forgot Password

DatStat Connect™ Platform users can now see a “Forgot Your Password?” link on the login page for the application, which provides users with a way to reset their own passwords instead of needing to reach out to the system administrator to set them a temporary password. Clicking this link will prompt the user to enter their email address in order to send a secure link to that email address that will allow the user to set a new password for their account. Emails are only sent if the address entered into the field matches that of a user in the system and the link that is sent to the user is only valid for one use in a period of up to 20 minutes. After 20 minutes the link will expire and the user will need to request a new one in order to reset their password.

Data Sets

Users with the ability to view and download submission data from the platform can create data sets from the Data page. A Data Set represents a subset of submission data across the activities in the system that can be downloaded as a zipped file in two different formats. When creating a data set, the user must select the format that they need prior to configuring more specific details; format options include: Raw Data and Study Data Tabulation Model (SDTM) formats. When configuring either format users can select which activity’s data they would like to include in the data set and they can optionally configure a filter for each selected activity that allows them to retrieve only the submissions that they need. There are no further configuration details for raw data, data sets. When configuring SDTM data sets users can configure additional information which includes: Study Information; a set of three required fields to specify the study name, description and protocol; and key variables for each activity which represent the variables used to tie multiple submissions to a single participant. Once a data set is properly configured, the user can download that data set to a zipped file, which will be compiled as a background task and then made available to download the user’s computer from the background tasks page.

The Study Data Tabulation Model format is an FDA prescribed XML format. SDTM formatted data sets contain a define.xml file that defines the variables for all activities selected for the data set and a dataset.xml file for each of those selected activities that contains the submissions that meet the defined filter conditions. In both files there are a set of attributes that are considered required when the data is to be submitted to the FDA and a set of attributes that are optional. SDTM formatted files generated from the platform will include all of the required attributes in the files which will be populated with data pulled from various sources in the platform; the exception to this is the significant figures attribute required for decimal type variables. In this case the files will contain a default value of 2 and when this is not accurate users can modify the file directly to the appropriate value. If users wish to include any of the optional attributes available for SDTM formatted data, they will need to add those attributes to each file by hand after the data has been downloaded from the system.

Improvements

  • The Activity Manager has had non-functional buttons and configurations removed and had language updated to be more user friendly.
  • Population Administrators can now preview configured email content when viewing email task and activity task configurations for draft or published workflows.
  • Workflow settings can be configured with a ‘before’ option, which allows users to schedule items prior to a specified time.
  • The audit log has been optimized to only log changes to calculated participant fields when the recalculation process results in a value that differs from the previous value.
  • Calculated participant field and category conditions can now reference task statuses and activity variables.
  • The Activity Manager no longer allows users to save questions with all response options disabled.
  • The chat feature now allows a single server to support multiple portals and maintains conversation access to their source portals.
  • The enable/disable toggle has been replaced with active/suspend toggle for workflows, steps, and tasks to better reflect the fact that, that change needs to be published to take effect.

Bugs

  • Fixed a bug that prevented users from updated chat settings over the chat API from DatStat Connect™ applications that support the chat server.
  • Fixed a bug that prevented users from importing data into campaign level tasks.
  • Fixed a bug that caused the padding and page margins to be removed from the bottom of all pages under the Data page in the platform.
  • Fixed a bug that prevented new installs of the DatStat Connect™ Platform from allowing multiple submissions to be made to a single task.
  • Fixed a bug that prevented users from being able to add new submissions with a submitted status over the API, instead they would be added as partial submissions.
  • Fixed a bug that prevented users from reordering field options for calculated fields.
  • Fixed a bug that prevented users from removing minimum and maximum length/value configurations on participant fields after they had been saved with those configurations in place.
  • Fixed a bug that caused calculated field methods used to retrieve the values of other participant fields to return values stored in time fields as if they were translated into UTC instead of returning the value as it is stored.
  • Fixed a bug that caused daily submission tasks to default their submission windows to midnight when participants did not have values for the specified time field instead of defaulting to the configured fall back time.
  • Fixed a bug that prevented users from moving a field from a population level group into a campaign level group when that field was used in workflow logic for the same campaign.
  • Fixed a bug that prevented activity question numbering preferences from saving causing users to be unable to change their question numbering style.
  • Fixed a bug that caused data filtered by date/time values to omit data that should have met the filter conditions because the value entered in the filter was being converted into the server’s local time before being applied to the data set.
  • Fixed a bug that allowed users with 2018.1 activity manager clients to connect to systems that had been upgraded to 2018.2 causing activities to be put into a bad state.
  • Fixed a bug that caused calculated field conditions to throw errors and not evaluate properly when the conditions contained internal activity variables that used the is set or not set operators.
  • Fixed a bug that caused file uploads to the platform larger than 30MB to fail.
  • Fixed a bug that caused bad links to be sent to users and participants that used the save page in the activity to send themselves links to resume that activity at a later time.
  • Fixed a bug that caused some participant field mappings to be optional which caused several internal functions to fail such as the ability to login to portals.
  • Fixed a bug that caused submission queries via the API to return all submissions instead of only those meeting the specified conditions.
  • Fixed a bug that caused scale values to appear as “undefined” in drop downs for participant fields and variables when configuring workflow conditions.
  • Fixed a bug that prevented updating participant data with import files if a participant field had been disabled, regardless of whether or not that field was included in the import file.
  • Fixed a bug that prevented users from accessing the status dropdown menu in the delete submission modal when attempting to delete a submission from a task.
  • Fixed a bug that caused activity task communications to cache piped values and send out incorrect content to participants.
  • Fixed a bug that caused submission data to be truncated in table cells on the Session Detail view page.
  • Fixed a bug that caused the submission history table when viewing the details of a daily submission task to use dates with nonstandard, ambiguous formatting.
  • Fixed a bug that caused submitted, partial, and missed submission counts for daily submission tasks to always be set to zero.
  • Fixed a bug that prevented users from configuring variable mappings for activity tasks during campaign configuration.
  • Fixed a bug that caused “Optional Task” to appear under task names on their details page despite required and optional tasks no longer existing in the system.
  • Fixed a bug that caused the primary navigation bar to be too large.
  • Fixed a bug that caused the last login value under Account Settings when viewing the account of a user from the User Management page to be inaccurate.
  • Fixed a bug that prevented users from logging in after changing their own password from their account page.
  • Fixed a bug that caused incorrect messaging to display on import confirmation modals stating that users would receive active notifications when the tasks completed.
  • Fixed a bug that caused error messaging to display on the default value field of participant field configuration when creating a field and changing to a display type that no longer supports field options.
  • Fixed a bug that caused group security indicators to disappear from the participant field configuration page when editing a group name.
  • Fixed a bug that caused daily task due dates to be shorted time due to not counting partial days resulting in the task only allowing for 29 submissions when it is configured to be open for 30 days.
  • Fixed a bug that caused the search function not to filter results in the Choose Item modal when configuring conditions.
  • Fixed a bug that caused calculated participant fields to be available for configuration under an activity task’s variable mappings even though those fields are not eligible for manual or mapped updates.
  • Fixed a bug that caused session timeout settings to not apply to the entire DatStat Connect™ product suite.
  • Fixed a bug that allowed participant fields to be created without selecting a data type and display type.
  • Fixed a bug that prevented users from reordering task events.
  • Fixed a bug that caused custom date filters to automatically select the previous day from the day entered by the user when applied to the page.
  • Fixed a bug that caused filter tags to disappear when applied to the page.
  • Fixed a bug that caused the Disable Site modal ‘Ok’ and ‘Cancel’ buttons to perform the same action.
  • Fixed a bug that allowed users without submission data export permissions to download data sets.
  • Fixed a bug that caused a participant’s workflow to remain open when that participant was disabled instead of setting all open workflows to incomplete.
  • Fixed a bug that prevented horizontal scrolling at smaller display widths when configuring task communications.
  • Fixed a bug that caused status and status reason labels to be blank for workflows, steps, and tasks when trying to change the status of an individual participant’s item in Firefox.
  • Fixed a bug that caused the Active/Suspended toggle to be present on step edit page rather than the view page.
  • Fixed a bug that caused users without submission data export permissions to be able to select activity submissions checkboxes for the purpose of downloading despite the download button being hidden from the user.
  • Fixed a bug that caused the Submission page’s table columns to shift slightly when a checkbox was selected.
  • Fixed a bug that caused End Users and User Administrators with participant add permissions to only see internal fields when creating a new participant.
  • Fixed a bug that caused the new participant page ‘Cancel’ button to be non-functional.
  • Fixed a bug that prevented the User Permissions page’s sites and campaigns table columns from truncating to two lines in Firefox.
  • Fixed a bug that caused tasks to be missing from the Choose Item modal when configuring campaign conditions.
  • Fixed a bug that caused obsolete workflow date based conditions to still be present in the conditions interface.
  • Fixed a bug that prevented activity task configuration edit pages from displaying configured variable mappings.
  • Fixed a bug that caused a silent error to be thrown when editing an activity that had not yet been published.
  • Fixed a bug that caused exported define.xml files to format incorrectly.
  • Fixed a bug that caused exported dataset.xml files to format incorrectly.
  • Fixed a bug that caused an error when attempting to download audit data from the Administration area without specifying a date range.
  • Fixed a bug that caused delete status reason confirmation modals to show the value “null” instead of specifying where the status reason is being used.
  • Fixed a bug that prevented the names of daily tasks from updating in the workflow sidebar when changes were made.
  • Fixed a bug that prevented internal participant fields from being listed in the Edit Participants Table modal as options to use as table columns.
  • Fixed a bug that caused User Permissions filter criteria to disappear as selected items when clicking the ‘Create’ button to save the filter.
  • Fixed a bug that prevented users from saving edits to the campaign details pages.
  • Fixed a bug that allowed users to save campaigns without names in the Edge browser.
  • Fixed a bug that allowed workflows to be published after a participant was given a task that the user deleted in the draft workflow, causing null reference errors to be thrown in regards to viewing that participant and their workflow information.
  • Fixed a bug that prevented participants from entering the next step of a workflow once the prior one was completed.
  • Fixed a bug that prevented ‘step delays’ and ‘next workflow starts’ from being configured as 0 minutes/hours/days/etc.
  • Fixed a bug that caused due date descriptions be incorrect for campaign level daily submission activity tasks.
  • Fixed a bug that prevented the tasks page from being filtered by applied filters in Internet Explorer 11.
  • Fixed a bug that prevented activities from being sorted by name in the Select Activities modal when configuring data sets.
  • Fixed a bug that caused the search fields for every Origin Type on the activity edit page to always show No Results text once all variables had been assigned to an origin type without the user clicking into a single of the search fields.
  • Fixed a bug that caused exported data set dataset.xml files for the questionnaire domain to format incorrectly.
  • Fixed a bug that caused participant fields to appear duplicated on the screen when dragged into a non-interactive space on the Fields page causing errors to be thrown that prevent users from selecting those fields to edit.
  • Fixed a bug that caused selected filter tags to disappear once all available criteria for an option had been selected on the User Permissions tab.
  • Fixed a bug that caused a silent error when a user without access to participants not assigned to sites attempted to remove a participant from a site and leave their site field empty.
  • Fixed a bug that prevented participants from being assigned to sites whose ID’s were configured with lowercase letters.
  • Fixed a bug that allowed site IDs to be entered with lowercase letters.
  • Fixed a bug that prevented event failures for Add Task events from logging to the database.
  • Fixed a bug that caused an error when using ‘equals’ and ‘not equals’ operators for filtering submission data for a selected activity.
  • Fixed a bug that caused an error when End Users with the Analyst role logged into the platform.
  • Fixed a bug that prevented daily tasks from working correctly due to inconsistencies between tasks that only allow for single submissions.
  • Fixed a bug that allowed the view activity URL pipe tags to be used in emails for daily submission tasks even though read only activities are not yet supported for daily submission tasks.
  • Fixed a bug that prevented filters created on the Activities tab under Data from being available to clone when configuring a data set with the same activity.
  • Fixed a bug that caused the timeout warning modal to appear repeatedly when the timeout was set to a very large number of minutes despite the user’s idle time not being near the timeout limit.
  • Fixed a bug that prevented API requests for bad workflow and task IDs from correctly reporting the error.
  • Fixed a bug that allowed the language dropdown menu to be selectable in the read-only versions of activities causing users that attempted to change the language to experience internal server errors.
  • Fixed a bug that caused version 1 of an activity’s data dictionary to download as version 0 in the PDF.
  • Fixed a bug that caused default activity header HTML to be different from the default HTML used in the header builder tool.
  • Fixed a bug that caused the activity header to not save separately for each supported language.
  • Fixed a bug that prevented Sendgrid and Plivo API information from being cleared after it had initially been configured.
  • Fixed a bug that caused the Participants tag to disappear when applied as an unsaved filter to the Tasks page.
  • Fixed a bug that prevented test data from being filterable when interacting with the test population.
  • Fixed a bug that caused an error when saving a task’s status as complete or incomplete preventing users from manually closing tasks.
  • Fixed a bug that caused the data sets Delete modal to have the wrong title.
  • Fixed a bug that caused selected participant fields to not be saved on data set filters.
  • Fixed a bug that caused internal variables to be excluded from exported data set files when a filter had not been applied to exclude them.
  • Fixed a bug that prevented users from creating a submission data filter on the Activities tab under Data with internal participant fields.
  • Fixed a bug that prevented activity variables from being renamed in the Activity Manager.
  • Fixed a bug that prevented the Email Log search from returning results.
  • Fixed a bug that allowed users to publish draft activities that were currently in a checked out state requiring the user who had that activity checked out to cancel their checkout and lose all changes that had made.
  • Fixed a bug that allowed password reset emails to be sent to email addresses that did not exist in user accounts in the platform.
  • Fixed a bug that allowed the password reset link in password reset emails to be used multiple times after the user had used it to successfully reset their password.
  • Fixed a bug that allowed in-use participant fields set to a response option display type to be edited when a value had already been stored in that participant field.
  • Fixed a bug that caused email address domains in the “To:” field to be removed from received emails.

Known Issues

  • The About modal cannot be opened when the user in on the Background Tasks page in the platform.
  • Users are unable to reorder workflows, the UI allows them to try but fails to save the new order when the reorder modal is closed.
  • Randomizing collections that contain a combination of questions and page breaks results in unexpected numbers of questions appearing on each page, rather than randomizing items within their configured pages.
  • The user’s last login value is only updated when logging into Connect, rather than being updated any time a user logs in to any DatStat Connect Product Suite application.
  • Participants are getting insufficient error messaging when attempting to log into an activity assigned to a user or user group that they are unable to access.
  • The Activity Manager’s Activity Edit window will not open after being minimized until the user right clicks on the task bar icon and uses the Restore option.
  • Email task content previews do not reflect that a sans serif font style had been used in the WYSIWYG editor in Firefox.
  • After logging out, users can still access the application by using a browser’s ‘back’ button.
  • The Activity Manager is not correctly importing response option values from a users clipboard.
  • The scheduler does not adjust items that were scheduled before daylight savings time to account for the hour shift when those items fire after daylight savings.
  • Navigating to the last page of the Participants table, under Manage, causes an internal server error when there are more than 400K items in the table.
  • Disabled participant fields are shown in the Edit Participants Table modal as possible options for table columns.
  • Users are prevented from changing the display type of a field with options to a text box display type, despite the conversion being compatible.
  • On the Activity Log page of Administration, the hover state on the Action column does not display the full action text for the create user action.
  • Step settings are missing task options when configuring conditions to open new workflows or close the current workflow.
  • Users cannot select an incomplete status reason when configuring a task to be set to incomplete when overdue.
  • When viewing a participant’s workflow, the most recent step is not selected by default unless that step has an In Progress status.
  • Editing a participant’s time zone to be the “system default” time zone will automatically select the currently configured default time zone.
  • Site descriptions should wrap to two lines and then become truncated when viewing the sites table on the sites page in Firefox