Version : 13

Released : 2019-05-14

Changes in this Release

Issue	Type	Module(s)	Description
1123	Feature	Automated Testing	Draft Properties now includes an option to control whether to show UAT Coverage statistics on the Draft Home page. These statistics show how many Edit Checks, Derivations, Forms and Custom Functions have associated UAT Tests and how many passed on their last run.
3562	Feature	Automated Testing	The Test Case list can be filtered by the status of the last run.
1064	Feature	Automated Testing	Clicking the UAT Test Case count on the Draft home page shows a list of UAT Test Cases.
3562	Feature	Automated Testing	The Test Case list can be filtered by the status of the last run.
3563	Feature	Automated Testing	The Test Case list can be filtered by label.
3564	Feature	Automated Testing	The Test Case list can be filtered by validity.
3565	Feature	Automated Testing	The Test Case list can be searched.
1065	Feature	Automated Testing	A Test Case can be deleted from the list of UAT Test Cases.
1066	Feature	Automated Testing	A Test Case editor was added.
1067	Feature	Automated Testing	Entering @EditCheck:EDIT_CHECK_NAME in the Test Case Editor creates a relationships between the Test Case and the Edit Check for test coverage and traceability from test to Check.
1068	Feature	Automated Testing	Similar to other object Editors, users can make comments on Test Cases.
1069	Feature	Automated Testing	Similar to other object Editors, users can assign Labels to Test Cases for workflow.
1070	Feature	Automated Testing	Steps which test Query text in a Test Case such as "Then I should see Query Text...." are checked against referenced Checks (via the @EditCheck:CHECK_NAME) and a warning is given if no referenced Edit Check has an OpenQuery action with that text.
1071	Feature	Automated Testing	Similar to Edit Checks, Derivations may be referenced with @Derivation:DERIVATION_NAME in the Test Case editor.
1072	Feature	Automated Testing	Similar to Edit Checks, Custom Functions may be referenced with @CustomFunction:CUSTOM_FUNCTION_NAME in the Test Case editor.
1073	Feature	Automated Testing	Similar to Edit Checks, Forms may be referenced with @Form:FORM_NAME in the Test Case editor.
1074	Feature	Automated Testing	Reference tags (@EditCheck, @CustomFunction etc) are not case sensitive.
1075	Feature	Automated Testing	Object references are shown in the Test Case list as links to those objects. If a reference tag points to an object that does not exist (@EditCheck:NO_CHECK_OF_THIS_NAME) then the reference is shown in red text and the text is not a link.
1080	Feature	Automated Testing	When a Test Case is related (via @) with an object that does not yet exist, creating that object will activate the link in the Test Case list and remove the red text.
1076	Feature	Automated Testing	In the margin of the Test Case editor, an icon for a referenced object will appear. Clicking the icon in the margin navigates to that object (hint: Ctrl-Click to open in a new tab)
1077	Feature	Automated Testing	Tickets may be referenced in Test Cases via the @Ticket:TICKET_NUMBER or @Specification:TICKET_NUMBER tag. This feature was removed in favor of #1673 in September 2021.
1081	Feature	Automated Testing	New Test Cases are created with a boilerplate example outline of a test to help users get started.
1082	Feature	Automated Testing	When an Edit Check has related Test Cases, this is shown in the side-bar of the Edit Check editor as a robot icon with a count of Test Cases.
1083	Feature	Automated Testing	From the side-bar of the Edit Check editor a new Test Case can be generated for the Edit Check.
1084	Feature	Automated Testing	In the Test Case listing, clicking the Run button creates a Test Set.
1085	Feature	Automated Testing	The Test set created by clicking the Run button in the Test Case listing contains all the visible (filtered) Test Cases. Custom Test sets can be created by filtering the Test Case list.
1086	Feature	Automated Testing	A snapshot of the Test Case (i.e. it's current content) is copied into the Test Set. The original Test Case can then be changed but the version in the Test Set is fixed, will not change and cannot be edited.
1087	Feature	Automated Testing	If a Test Case is included in a Test Set and that Test Case is subsequently changed, a marker appears on the copy of the Test Case in the Test Set to show that it is no longer the same as its source Test Case.
1088	Feature	Automated Testing	If a Test Case is included in a Test Set and the original Test Case is subsequently deleted, the copy of the Test Case remains in the Test Set and a market appears on that copy to show that its source has been deleted.
1089	Feature	Automated Testing	Invalid Test Cases (such as ones that reference Datapoints that do not exist) cannot be added to a Test Set run and will be ignored.
1090	Feature	Automated Testing	Users may delete Test Set Runs. All associated results and screenshot evidence will also be deleted.
1091	Feature	Automated Testing	When running a Test Set, all the roles referenced in the Test Cases are found and the user must provide username/password credentials for them in order to run the Test Set.
1092	Feature	Automated Testing	When running a Test Set the system will identify if a Test Case requires Subject Admin permission and ask for credentials for a user with that Role. Subject Admin permission is required where a step like "Given FormA in FolderB exists" is used.
1134	Bug	Automated Testing	When creating a UAT Test Run if a non-existent Rave URL was entered then an internal error message was displayed. This has been replaced by a readable message.
1135	Bug	Automated Testing	In the UAT Test Case Editor selecting the 'Then I should see form {form} in folder {folder}' step was incorrectly inserting another step. This has been corrected.
1137	Bug	Automated Testing	Because of a bug in Rave Web Services (MCC-147590) the 'Enter Data' step in UAT Test Case was not causing all Fields on a Log Record to be submitted. The Rave Web Service calls have been modified to workaround this bug and the 'Enter Data' step now functions as expected on Log and Standard records.
1156	Feature	Automated Testing	When running a UAT Test Case no screenshot will be taken on a Login step. This is to avoid capturing information about studies other than the study being tested.
1157	Feature	Automated Testing	Before running a UAT Test Case the TrialGrid UAT study must be configured correctly by a system administrator. If it is not configured correctly the Test Case cannot be run. More informative error messages are now displayed explaining what part of the configuration is incorrect.
1122	Feature	Collaboration	Draft Properties now include whether a Wiki page from the list of Project Wiki Pages should be displayed on the Draft Home page. This can be used to provide more information about the Draft such as integrations it includes or current state.
1100	Bug	Diagnostic	Diagnostic 0094 does not correctly report multiple checks linking to a field via VariableOID. This was fixed.
1106	Bug	Diagnostic	When selecting a Project to copy Diagnostics from the dialog will sometimes not enable the Copy button. This was fixed.
1127	Bug	Diagnostic	Diagnostic 99 identified Folder and Form repeats for Checksteps which were not data-related. This was corrected so that it only takes into account data steps.
1132	Feature	Diagnostic	Diagnostics now have an Importance setting. By default all Diagnostics are of "Medium" and users with Manage Diagnostics permission may set a Diagnostic to High / Medium or Low importance.
1175	Feature	Diagnostic	Diagnostic 73 checks Data Dictionary Coded Values against default values in Fields. Diagnostic 73 is case sensitive so a default value of "One" will not match against a coded value of "ONE" in the Data Dictionary. Rave is case-insensitive. A new setting was added to Diagnostic 73 to make the comparison case-insensitive to match Rave.
1177	Feature	Diagnostic	PDF and Excel Diagnostic result download buttons are now shown on the Diagnostic results page. Note that this was was retired in version 53.
1178	Feature	Diagnostic	The Draft Home Page Diagnostics card shows latest result count or if no Diagnostics have yet been run, a link to run Diagnostics. The text of the "Run Diagnostics" button was changed to "Run / View History" when there has been at least one Diagnostic run. This should make navigation clearer.
1179	Feature	Diagnostic	If you navigate from the Draft Run Diagnostics page to the Manage Diagnostics page a navigation button now appears on the Manage Diagnostics page to take you back to that Draft Run page. Previously the navigation to get back was not clear and you would have to use the browser back button.
1187	Bug	Diagnostic	Diagnostic 101 did not manage Formats with + after the decimal point properly (e.g. 3.2+). This was corrected.
1188	Feature	Diagnostic	Diagnostic 101 did not ignore Inactive Checks and Derivations. A setting was added for this with a default of ignoring Inactive Checks and Derivations.
1189	Feature	Diagnostic	Diagnostic 64 did not ignore Inactive Edit Checks. A setting was added for this with a default of ignoring Inactive Checks.
1193	Feature	Diagnostic	Diagnostic 0020 now ignores words contained in URLs and does not attempt to spell check them.
1197	Feature	Diagnostic	New Diagnostic 0102 finds URLs in draft text strings (Field help text for example) and checks if the URL can be accessed.
1194	Feature	Diagnostic	Diagnostic 66 now has an option to ignore Inactive Checks (default = Ignores inactive).
1195	Feature	Diagnostic	Diagnostic 72 now has an option to ignore Inactive Checks (default = Ignores inactive).
1192	Bug	Diagnostic	Diagnostics 0058, 0064, 0066, 0072 and 0098 did not correctly handle pattern-match exclusions, this was corrected.
1198	Feature	Diagnostic	Diagnostic 103 was added. This looks for =NOW Default Values for Fields which are not of the Date/Time control type. This setting can prevent Rave Subject PDFs from generating.
1199	Feature	Diagnostic	Diagnostic 1 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1200	Feature	Diagnostic	Diagnostic 2 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1201	Feature	Diagnostic	Diagnostic 3 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1202	Feature	Diagnostic	Diagnostic 4 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1203	Feature	Diagnostic	Diagnostic 5 now has an option to ignore Inactive Forms (default = Ignores inactive).
1204	Feature	Diagnostic	Diagnostic 6 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1205	Feature	Diagnostic	Diagnostic 7 now has an option to ignore Inactive Forms (default = Ignores inactive).
1206	Feature	Diagnostic	Diagnostic 8 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1207	Feature	Diagnostic	Diagnostic 9 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1208	Feature	Diagnostic	Diagnostic 10 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1209	Feature	Diagnostic	Diagnostic 11 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1210	Feature	Diagnostic	Diagnostic 12 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1211	Feature	Diagnostic	Diagnostic 13 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1212	Feature	Diagnostic	Diagnostic 14 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1213	Feature	Diagnostic	Diagnostic 15 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
134	System	Infrastructure / System	Upgrade to the latest hosting environment. No user impact.
1104	System	Infrastructure / System	Upgrade to the latest Python version. No user impact.
1105	System	Infrastructure / System	Added pre-deployment database version check. No user impact.
1110	Feature	Infrastructure / System	Some email-related system settings were moved from system configuration into code because of the risk of changes between beta / pre-production and production versions. End-users will see no difference and are not affected.
1182	Bug	Infrastructure / System	The process to remove failed tasks did not run on schedule correctly. This was corrected.
1126	Bug	Permissions	Owners of Projects were not able to assign themselves to Tickets. This was fixed.
1110	Feature	Retired	Some email-related system settings were moved from system configuration into code because of the risk of changes between beta / pre-production and production versions. End-users will see no difference and are not affected.
1116	Feature	Standards	Performance of draft import was slow on the production site. This has been improved.
1118	Bug	Standards	Matrix fingerprints were being calculated incorrectly on draft import. This has been corrected. There is no user impact since we do not apply standard compliance to matrices.
1102	Feature	Study build	When importing Drafts direct from Rave the process can fail if a Draft has a large number of Folders. This is a known issue in Rave. The manual workaround is to download the Draft in parts and merge the sheets in Microsoft Excel. The TrialGrid import-from-Rave feature now takes care of this automatically, downloading in sections and then re-assembling for import so that Drafts with large numbers of Folders can now be imported.
925	Feature	Study build	The Form Editor now shows a list of related Derivations and Edit Checks for each Field under the Field Checks tab.
1111	Feature	Study build	When the Matrix List is opened, the Default Matrix is automatically selected. It also has (default) added to its name to make it clear which is the Default Matrix (if any).
1115	Bug	Study build	On FireFox on starting Draft Upload from an ALS spreadsheet if you navigated away from the page then the task list did not update to show progress of the upload running in the background. This was fixed.
1121	Bug	Study build	If you removed an entry from a View, Entry or Review Group list for a Field so that went from some entries to no entries, the property editor for that field would no longer display (it would stay stuck on the previous field). This was corrected.
1124	Feature	Study build	In the Custom Function editor a Validate button has been added. This will verify the source code of the Custom Function against Rave and provide the same errors as the Rave Custom Function editor if there is a problem with the source code.
1131	Bug	Study build	Preview of Custom Functions and Custom Function Templates would render xml content in the Custom Function source code as html - e.g. <input> would be rendered as an input element. This was corrected.
1063	Feature	Study build	The Draft home page now shows a count of UAT Test Cases.
1155	Bug	Study build	Field Help length limit was set to 4,000 characters to match Rave.
1154	Bug	Study build	Field PreText length limit was set to 4,000 characters to match Rave.
1153	Bug	Study build	Form Help length limit was set to 4,000 characters to match Rave.
1152	Bug	Study build	Confirmation text limit was set to 4,000 characters to match Rave.
525	Feature	Study build	Edit Check descriptions have been shortened for Check Actions targetting the same data reference. For example, all AddForm actions referencing the same Folder/Form/Field will be displayed in one section.
686	Feature	Study build	The Fields list now includes the Form Name as well as the Form OID.
969	Bug	Study build	Deleting an entry in a Data Dictionary would sometimes cause other rows to not to be displayed. This has been corrected.
1125	Feature	Study build	Only one row could be pasted into a Unit Dictionary. This has been corrected and multiple rows can be copied/pasted.
1142	Bug	Study build	Displaying Matrices in Drafts with hundreds of Folders and Forms was slow. Now the initial request to display draft Matrices will still take some time to load all the information about Matrix Folder Forms but once loaded switching between Matrices will be fast.
1143	Feature	Study build	When editing Data Dictionaries a warning will be displayed if a comma, semi-colon or double- slash is entered.
1144	Bug	Study build	Copying from Excel into Data Dictionaries sometimes caused extra line breaks to be inserted. This has been corrected. When copying or entering data into Data or Unit Dictionaries line breaks will be automatically removed (as in Rave).
1145	Feature	Study build	Edit Check descriptions have been re-formatted and include the Form and Folder names to make it easier to identify the referenced objects. The description includes an image next to each Folder, Form and Field; clicking on the image will link directly to that object.
1146	Feature	Study build	When searching for Folders, Forms, Fields and Variables in the Edit Check editor, multiple terms, including numbers, can be searched using an underscore to separate terms. For example, 'VIS_1' will find all folders containing 'VIS' and '1'.
1148	Bug	Study build	The description of Edit Check Action "SetVisible" was wrong and has been corrected.
1149	Bug	Study build	Sometimes the count of list items (for example in the Forms list) was incorrect. Now all lists use pagination, with a configurable page size, and the counts of items are correct.
1150	Feature	Study build	The count of Field Checks is now displayed underneath the count of Edit Checks on the Draft home page. Field Checks are QueryFutureDate, QueryNonConformance, LowerRange, UpperRange, NCLowerRange, NCUpperRange. Note that Field Checks can be viewed in the Fields list but are not displayed in the Edit Checks list.
1151	Bug	Study build	When exporting the Fields list to pdf the columns might be truncated at the right of the page. To workaround this you can export to Excel and/or select fewer columns to be displayed and exported.
1164	Feature	Study build	In the Fields list, the Variable OID will only be displayed if it is different from the Field OID.
3346	Feature	Study build	The Fields list can be searched by OID.
1165	Feature	Study build	To improve readability of Edit Check descriptions the Folder and Form names will only be displayed once if there is only one Folder and Form in the Edit Check.
1136	Bug	Study build	When fetching a list of Studies with Architect access from iMedidata, a maximum of 10 studies was found. This was corrected.
1166	Feature	Study build	The Direct Draft (or Version) import now supports logging in with iMedidata credentials.
1167	Feature	Study build	When importing a Draft or Version from iMedidata, the system will prompt for a two-factor authentication code if iMedidata requires one. The user can then authorize TrialGrid for the rest of the TrialGrid session (i.e. until TrialGrid logout) or for 30 days.
1169	Bug	Study build	When selecting a VariableOID from the drop-down list in the Form Editor, Field OID would also be overwritten. Field OID is now only set if it is blank.
1170	Feature	Study build	When working on long Forms it was necessary to scroll to the top to see if the Form saved. The Form Save message is now shown at the top of the screen regardless of where you are scrolled in the Form editor.
1171	Feature	Study build	In the Form editor, when a Field has a related Data Dictionary a link to the Data Dictionary now appears next to the Data Dictionary selector for that field (Ctrl/Cmd-Click to open in a new Window)
1172	Feature	Study build	In the Form editor, when a Field has a related Unit Dictionary a link to the Unit Dictionary now appears next to the Unit Dictionary selector for that field.
1138	Bug	Study build	The Form Editor would allow the entry of invalid Field and Variable OIDs. This was corrected so that Field and Variable OIDs can only contain A..Z, 0..9 and the _ (underscore).
1183	Bug	Study build	In prerelease environment iMedidata import failed with a file creation error. The root cause was fixed.
1184	Feature	Study build	The default URL for iMedidata import or export is now set to https://www.imedidata.com since the majority of users are using the production iMedidata environment.
1196	Bug	Study build	Tags in Form Names such as <font color="blue">Demography</font> would cause breadcrumbs and Form Name edit control in the Form Editor to display incorrectly.
1078	Feature	Tickets	Tickets may be closed and re-opened.
1181	Feature	Tickets	Tickets now have an optional Due date field.
1185	Feature	Tickets	In Ticket listings tickets which are Open and past due show their due date in red text.
1119	Feature	UX	Rave EDC 2018.2.1 and 2018.2.2 were added as possible Rave EDC versions.
1130	Feature	UX	Rave EDC 2018.2.3 were added as possible Rave EDC versions.
1159	Feature	UX	Long activity messages are truncated in the activity lists (the full text is displayed in a tooltip when hovering over the truncated message) and the activity lists have been formatted as tables for improved readability.
1160	Feature	UX	Background tasks which fail are sometimes left in a Pending or Running state. After 72 hours these tasks are marked as failed.
1112	Bug	Validation	Validation docs were no longer showing screenshots in validation portal. This was fixed.
1113	Bug	Validation	Validation docs were showing copyright 2018. This was updated to 2019 for future releases.
1114	Bug	Validation	Validation docs were not showing some text elements in the results section. This was fixed.
1186	Feature	Validation	Static Application Security Testing (SAST) output should be included in the validation package. SAST analysis examines the TrialGrid source code for potential security vulnerabilities. The output of this automated analysis was added to the validation package for TrialGrid releases.