Web v5.6 - January 30, 2021
What’s New or Updated
ID | Functional Area | Description | Impact/Risk |
|---|---|---|---|
863 | Email Notifications | Removed 50-user limit for email notifications triggered by randomization and conditional actions | Low |
771 | Form builder | Form annotations can now be exported without the conditional actions included in the form details | Low |
713 | New permission to deny user’s ability to add unscheduled visit dates Denying permission to add unscheduled visits will only be enforced on the web. Users who open subject records in the app will be able to add unscheduled visits. Form permissions should be used to ensure users cannot add/edit specific forms, if applicable. | Low | |
705 | Ability to create new subjects and run edit checks when performing batch imports | Low | |
403 | Study Documents | Removed the ability to delete study documents. Stay tuned for its return in the near future. | Low |
326 | Site Documents | Removed the ability to delete site documents. Stay tuned for its return in the near future. | Low |
398 | Record status report | Improved performance and ability to handle large data sizes | Low |
220 | Report builder | Filters now get the text values for choice fields and ability to quickly clear all filters | Low |
203 | Added role distribution filters and ability to clear all filters in a single action | Low | |
201 | Queries report | Added column sorting on the query dialog column | Low |
190 | Payment management | Now export all payments, both paid and due in one action | Low |
161 | Form builder - data dictionaries | Added visit columns to the form properties export so study builders can see where the forms are currently collected within the study design (Scheduled and Unscheduled visits) | Low |
139 | Data exports | Export data by form can now be given to site users for exporting their own site data | Low |
78 | Action Items report | Minor changes to section headers | Low |
Bug Fixes
ID | Functional Area | Fixed issue | Impact/Risk |
|---|---|---|---|
972 | Email notifications | Randomization notices going to some users more than once | Low |
947 | Export data by form | Field labels/Column headers with apostrophe character caused error | Low |
924 | Site/user audit report | Adding user at host level | Low |
917 | Queries | Creating manual queries at the interval/visit level | Low |
910 | Form builder | Opening forms in the editor which do not exist on the selected version | Low |
906 | Missing Records | Missing records were not getting counted if the study exit was the same date as the high window | Low |
901 | Form auto-valiadation | Validating forms when no records exist in administrative site | Low |
896 | Version difference report | Report errored if multiple similar changes were made within a normalized table in the form builder | Low |
891 | Data entry | Required upload field check only worked on the first save of the record | Low |
890 | Sign In | Google Sign In option was not providing access to the user’s studies | Low |
888 | TrialKit Drive | Subject Visits export still included Admin sites when the configuration did not call for it | Low |
885 | Field blinding | Blinded upload fields had potential to display file names for users who were blinded to the field | Low |
855 | Version migrations | Error when upload fields were being migrated | Low |
847 | Patient Web Portal | Consent completed from the web was not pushing out the consent document after completion | Low |
818 | Deleting subjects | Subject ID is now displayed in the confirmation window | Low |
646 | Report Builder | When the report is filtered, the filters were not getting cleared after exiting and returning | Low |
633 | Form Builder | Incomplete email conditional actions now show error to user when saving | Low |
563 | Queries | Deleting a query from a page caused email notifications to fire if they existed on the form | Low |