Version : 14

Released : 2019-08-30

Changes in this Release

Issue	Type	Module(s)	Description
1237	Bug	Automated Testing	Rave 2018.2.3 and 2018.2.4 restrict access to the Rave API from within Custom Functions. The TrialGrid UAT draft has been updated for compatibility with these Rave versions.
1235	Feature	Automated Testing	In the UAT Test Case editor, the test step "I am logged in with Role" is now checked against the core configuration in TrialGrid and a warning is shown if the EDC Role name is not present or the role is present but inactive.
1245	Feature	Automated Testing	The 'I am logged in with role "{role}"' UAT test step now has an associated editor which can be accessed by clicking the icon in the margin of the Test Case editor. A dialog opens which allows the user to choose an EDC role from the core configuration or to enter a new role name.
1249	Feature	Automated Testing	The "folder {folder ref} exists" UAT test step now has an associated editor which allows selection of a Folder OID and the entry of Folder paths such as FOLDER1[1]/CHILD_FOLDER[2].
1255	Feature	Automated Testing	The "form {form_ref} exists in folder {folder_ref}" UAT test step now has an associated editor for the selection of Form and Folder OIDs and the entry of Form references containing repeats e.g. "AE[2]" and Folder paths.
1256	Feature	Automated Testing	The "I enter data" UAT test step now as an associated editor. This allows the selection of Folder / Form / Field / Data Dictionary and Unit Dictionary values (where required).
1313	Bug	Automated Testing	The UAT Test Case Helper for the 'When I log in with role "{role}"' step would change the step text to 'When I am logged in with role "{role}"' which was invalid. This was corrected.
1314	Bug	Automated Testing	When selecting a Step to insert in the Test Case editor it was not possible to add the same step repeatedly. An "Add" button must now be clicked to add the step to the Test Case editor. This allows a step to be selected and then added each time the Add button is clicked.
1319	Bug	Automated Testing	A Helper (wrench icon) was shown for the 'Then I should see "{datapoint_ref}" has value "{value}"' UAT step in the Test Case editor when it should not have been shown. This was corrected.
1316	Bug	Automated Testing	If an Edit Check referenced a numeric Field by value and by 'IsEmpty' or 'IsNotEmpty' check steps then the Test Case Advisor would fail to generate a Test Case. This has been corrected.
1320	Bug	Automated Testing	The Test Case runner would sometimes record a failure when trying to take a screenshot of a Log Form. This has been corrected.
1321	Bug	Automated Testing	The Test Case Advisor has been changed to suggest Test Cases with 'I enter only this data' steps rather than 'I enter data'. This works better for Edit Checks comparing values across standard and log Fields in Rave. Some Edit Checks which use Custom Functions might be better run with 'I enter data', this will need to be reviewed and tested. 'I enter data' submits all datapoints on the form. 'I enter only this data' submits only those datapoint which are included in the Test Case.
1322	Bug	Automated Testing	The Test Case runner would fail when verifying an Update Form or Update Folder Name action if the Check Action referenced a date Field. Rave uses a mixed case date to update the Folder or Form Name (for example 'AE 10 Jun 2010') even if the date on the form is in upper case ('10 JUN 2010'). Now the Test Case runner will perform a case-insensitive verification on Folder and Form names.
1326	Bug	Automated Testing	The Test Case Advisor was not generating suitable values if a date Field, with 'yyyy' format, was being compared against another date Field with 'dd MMM yyyy' format. The suggested test values would not satisfy the logic of the Edit Check. This has been corrected.
1329	Bug	Automated Testing	The Test Case Advisor was not incorrectly inserting a sub-folder reference on Merge Matrix Check Action steps. This has been corrected.
1330	Bug	Automated Testing	If a Folder has a parent Folder then the parent will be included in suggested Test Cases. For example, a Folder 'AE_P' has a parent 'AE'. Suggested Test Cases will have steps like: When I enter data: | DataPoint | Value | | AE/AE_P.SAE.AETERM[1] | HEADACHE |
1331	Bug	Automated Testing	If an Edit Check included static values then the Test Case Advisor would include them in the suggested Test Case even if they would be non-conformant for that Field. This has been corrected.
1335	Bug	Automated Testing	The Test Case runner would fail if the User Data String in a Data Dictionary Entry contains a single quote. This has been corrected.
1337	Feature	Automated Testing	The Test Case Advisor will base date values around a date 2 years before the current date. It will suggest values (depending on the data format) which are 1 day, 1 week, 1 month and 1 year before and after the base date (2 years ago). This will avoid future dates being included in the suggested data.
1328	Feature	Automated Testing	If an Edit Check references a Dynamic SearchList Field the Test Case Advisor will add a comment to the suggested Test Case, which will be categorised as requiring review. TrialGrid Test Cases can verify values within a Dynamic SearchList and can enter data into a DSL Field, but the values cannot be suggested automatically and must be inserted into the suggested Test Case.
1342	Feature	Automated Testing	If an Edit Check references a FileUpload or Signature Field the Test Case Advisor will add a comment to the suggested Test Case, which will be categorised as requiring review. TrialGrid Test Cases cannot test FileUpload or Signature Fields.
1343	Feature	Automated Testing	The Test Case Advisor will check Field view and entry restrictions. If a Field is view or entry restricted to the default role then an additional 'When I log in with role "{role}"' step will be inserted before the restricted Field. If further Fields are not restricted then a log in step for the default role will be inserted after the restricted Field steps. A comment will be added to the suggested Test Case, which will be categorized as requiring review.
1344	Feature	Automated Testing	The Test Case Advisor will choose Lower and Upper range values for numeric Fields in preference to the maximum possible values. This leads to more realistic Test Data.
1345	Feature	Automated Testing	The Test Case Advisor will now generate Test Cases for Edit Checks which have Logical Record Position check steps. A comment will be added to the suggested Test Case, which will be categorized as requiring review.
1346	Bug	Automated Testing	The Test Case Advisor was suggesting values for Set Datapoint Check Action steps using the Coded Data value (for Fields referencing a Data Dictionary). The Test Case expects this to be the User String. This was corrected.
1403	Feature	Automated Testing	The Test Case Advisor will now add a comment if the Edit Check references an inactive or invisible Field, or an inactive Form.
1404	Bug	Automated Testing	If a SetDatapoint check action has a value which is not present in the Data Dictionary for the target Field (if that Field has a Data Dictionary) then the Test Case Advisor will use the value in the Check Action and will add a comment to the Test Case.
1365	Bug	Automated Testing	In UAT Run page Study Site Number was whitespace-sensitive meaning a space at the start or the end of the Study Site Number would cause the system to not match the study site. This was corrected.
1366	Feature	Automated Testing	When running UAT tests invalid username/password messages now make clear when the issue is with Rave Classic accounts.
1415	Feature	Automated Testing	If a Draft object (Form, Edit Check, Folder, Custom Function, Dictionary or Test Case) is copied from a Library or another Draft then the sidebar will contain informaton about which object and Draft it was copied from. Standards Compliance information is now displayed in the object sidebar. Note that Derivations cannot be copied yet - this will be added in a future release (issue #1428). (Duplicate of #733)
1429	Bug	Automated Testing	If a failure occurred in an early part of the processing for a UAT run before any test cases were executed, the error was not reported to the user, the task would simply fail. This was corrected and these errors are now reported to users and test cases are shown with a Failed status.
1431	Bug	Automated Testing	Infrastructure changes caused UAT result live-update to fail. This was corrected.
1427	Bug	Automated Testing	Some Test Cases containing unicode characters would fail to run. This has been corrected.
1423	Bug	Automated Testing	Test Case result screenshots were not always showing open log records. This has been corrected. Note that Rave EDC (RaveX) Test Cases will open log records for screenshots if there are fewer than 100 log records. Test Cases with more than 100 log records will run but without taking screenshots of log records after 100.
1424	Bug	Automated Testing	Test Case results for Rave EDC (RaveX) now show the whole screen when a screenshot is taken.
1438	Bug	Automated Testing	UAT tests would not run against a Rave URL with the Core Configuration setting 'All upper case' enabled. This was corrected.
1042	Feature	Diagnostic	Diagnostic 104 was added to check that %% style Form Help Text entries which link to resources are set correctly.
1043	Feature	Diagnostic	Diagnostic 105 was added. This Diagnostic checks that Form DDE Options are set to "Never". It is provided for clients who do not use DDE in their Rave studies.
1044	Feature	Diagnostic	Diagnostic 106 was added. This Diagnostic checks that Form IsTemplate is set to False. It is provided for clients who do not use Template Forms in their Rave studies.
1098	Feature	Diagnostic	Diagnostic 107 was added. This Diagnostic checks that an All-Forms Matrix contains all Forms that are defined in the Draft (optionally excluding Inactive Forms).
1222	Feature	Diagnostic	Diagnostic 108 was added. This Diagnostic checks that a PDF / All-Visits Matrix is a superset of all other Matrices for a study (i.e. that a Folder/Form combination has not been missed out) with options to ignore a set of Matrices (e.g. an All-Forms style matrix)
1230	Bug	Diagnostic	Diagnostic 72 should not report empty values separated by | symbols.
1231	Feature	Diagnostic	In Diagnostic findings, any diagnostic with more than 20 results has its results section closed to start with. This makes viewing results easier.
1228	Feature	Diagnostic	Diagnostic 64 now shows a link to Data Dictionaries that it reports.
1288	Bug	Diagnostic	Feature 1231 added collapse of diagnostic results where there were greater than 20 findings to improve readability. This had the unintended side-effect of disabling the Fix All button for those listings. This was corrected.
1253	Feature	Diagnostic	In the Diagnostic results the settings section was set to use a smaller font. Being able to see the settings is important but it should not draw attention away from the findings.
1292	Bug	Diagnostic	The Project level setting "URL Users Can View" was not being honored for the import of Diagnostics from other projects in the URL. If you tried to import Diagnostic settings from a Project where you did not have a Project Role assignment but the Project was set "URL Users Can View" you should be able to import those Diagnostics but you could not. This was corrected.
1291	Bug	Diagnostic	The Project level setting "URL Users Can View" was not being honored for viewing the Diagnostics settings page for a Project. This was corrected.
1270	Feature	Diagnostic	The explanation for Diagnostic 0026 (Inactive Forms/Fields referenced in an Active Edit Check) was expanded to include a warning that a Draft containing Checks which reference inactive Fields or Forms cannot be published to a Version in Rave Architect.
1271	Feature	Diagnostic	Examples were added to the description of Diagnostic 0050 (Fields related to Data Dictionaries have appropriate DataFormats). A setting to ignore inactive Fields and Fields on inactive Forms was also added with a default of True (on).
1272	Feature	Diagnostic	An exclusion setting for Inactive Fields was added to Diagnostic 0032 (Date and Datetime fields set to Query Future Date) with a default of True (on).
1300	Feature	Diagnostic	Diagnostic 0051 (Fields should have SAS Format Specified) had a setting "Ignore Inactive" added set by default to True to ignore Fields which are inactive or which are on Inactive Forms.
1277	Feature	Diagnostic	The description for Diagnostic 0052 (SAS Format should match Rave Field format) was expanded with examples and an option to ignore inactive Fields / Fields on inactive Forms was added.
1047	Feature	Diagnostic	Diagnostic 0109 was added (Fields should NOT have SAS Format Specified). This is the opposite of Diagnostic 0051 for organizations which rely solely on the default SAS formats provided by Rave.
1280	Feature	Diagnostic	Additional description was added to Diagnostic 0061 to explain effect on PDF generation of unsupported HTML tags. Diagnostic also had an option added to ignore inactive Fields and Fields on inactive Forms with a default of True (on).
1287	Feature	Diagnostic	Diagnostic 0081 (detect trailing whitespace) now has an option to ignore Form and Field Help. This is set to True by default.
1281	Feature	Diagnostic	Additional description was added to Diagnostic 81 to explain that trailing whitespace can affect PDF generation.
1285	Bug	Diagnostic	Diagnostic categories included "Coder" and "Coding". Diagnostic categories were changed to just "Coding".
1286	Feature	Diagnostic	Diagnostic 0110 "ePRO Forms should not require signature" was added. It detects Forms which are set as ePRO (Patient Cloud) and which are set "Requires Signature".
1052	Feature	Diagnostic	Diagnostic 0111 was added. This checks that a set of named Custom Functions exist in a Draft.
1251	Bug	Diagnostic	Diagnostic 0105 had duplicate exclusions settings. Exclusion settings for Diagnostic 106 had been assigned to Diagnostic 105. This was corrected.
1283	Feature	Diagnostic	Diagnostic 0063 (Dynamic Search Lists should be related to one Field) was re-written to identify an issue in Rave. Each unique Variable that appears in a Set Dynamic Search List Check action, must be referenced in the Check Steps of at least one Edit Check with a Set Dynamic Search List Check action against that Variable. If condition is not met then the Draft cannot be published and a warning "An invalid Edit Check setup was detected for the Dynamic SearchList field" is shown. For example, if I have a Draft with only one Edit Check and that Edit Check sets with CheckAction SetDynamicSearchList for FormA/FieldA/VariableA, I will not be able to publish this Draft unless the Edit Check contains a Check Step which also references VariableA (in any Form/Field, the Variable is the important thing). If I add a second Edit Check which has a SetDynamicSearchList action for FormB/FieldB/VariableA (same variable) and THIS Edit Check has a Check Step referencing FormB/FieldB/VariableA (same variable) then I will be able to publish the Draft. Diagnostic 0063 was renamed "Variables targeted by Set DSL Actions are referenced by Check Steps"
1306	Feature	Diagnostic	Diagnostic 0112 was added. This checks that Variables which are set as the target of a Set Dynamic Search List Check Action have a control type of DynamicSearchList.
1305	Feature	Diagnostic	Diagnostic 0113 was added. This checks that Fields with a ControlType of DynamicSearchList do not appear on the Primary Form.
1045	Feature	Diagnostic	Diagnostic 0114 was added. This checks that all Forms have the Save Confirm option checked except any that are specifically identified by OID.
1307	Feature	Diagnostic	Diagnostic 0087 (Appropriateness of Form-level signature=Yes) ignored inactive Forms and inactive Fields. A new setting was added to control whether inactive Forms and Fields should be ignored with a default of True (on).
1308	Feature	Diagnostic	The Diagnostic Category "Rave EDC" and references to Rave EDC in Diagnostic descriptions have been updated to "Rave EDC (RaveX)" to avoid confusion with Rave Classic EDC.
1304	Feature	Diagnostic	Diagnostic 0074 (Rave EDC/X only supports NoLink confirmation style) was changed to make it applicable to Rave Classic users who want to limit confirmation styles to a subset. It now allows you to select which save confirmation styles are allowed. The default is to allow only the "NoLink" style and the automatic fix is only available if the only allowed style is "NoLink" and continues to change the confirmation style to "NoLink" so the behaviour is the same as before for RaveX use but can now be configured for Classic Rave. In addition an option to ignore inactive Forms was added - defaulted to True (on).
1051	Feature	Diagnostic	Diagnostic 0116 was added. This checks that a Form/Field combination has Set Observation Date of Folder set. This supports studies where the subject calendar is used.
1309	Feature	Diagnostic	Diagnostic 0117 was added. This checks that the Primary Form for the Draft has a name that matches one of a set of standard names. This is for clients that want to ensure that their Primary Forms are named in specific ways such as "Subject Identification".
1040	Feature	Diagnostic	Diagnostic 0118 was added. This checks that the Confirmation Message and Signature Prompt for the Draft exactly match standard wording provided by the Diagnostic settings.
1048	Feature	Diagnostic	Diagnostic 0119 was added. This checks that controls of type CheckBox are not used except on Form OIDs that match a specific pattern or on Field OIDs that match a specific pattern. Some organizations choose not to use CheckBox controls for site-level data input.
1339	Bug	Diagnostic	Diagnostics 0088-0094 Diagnostic settings for Entry Restrictions were labelled as View Restrictions. This had no effect on functionality and was corrected.
1347	Bug	Diagnostic	Diagnostics 0001,0064 and 0066 were ignoring the "ignore_inactive" setting. This was corrected.
1354	Bug	Diagnostic	Diagnostic 0001 does not take into account "Ignore Inactive" setting for Long Text fields which should be short (separate issue from 1347 above)
1348	Feature	Diagnostic	A new setting was added to Diagnostic 0086 (Length of static values in Check and Derivation Steps) to ignore inactive Checks and Derivations with a default of true (on).
1349	Feature	Diagnostic	A new setting was added to Diagnostic 0076 (Non-Zero Recordposition for Log Fields) to ignore inactive Checks and Derivations with a default of true (on).
1355	Bug	Diagnostic	Diagnostic 0003 (SAS Field OID length) did not ignore Label fields. This was corrected.
1356	Feature	Diagnostic	Diagnostic 0003 had a new option added to exclude Forms which match a name or pattern.
1359	Feature	Diagnostic	Diagnostic 0023 (naming of DateTime control types) did not have an option to ignore Inactive Fields / Fields on Inactive Forms. This was added with default of True / on.
1360	Feature	Diagnostic	Diagnostic 0023 (naming of DateTime control types) now allow you to define a "contains" string so that you can ensure some string (like DAT) appears in the Field OID.
1361	Feature	Diagnostic	Diagnostic 0027 (Recordposition 0 for Standard Fields) has an option to ignore inactive Checks and Derivations. This was added with a default of True / on.
1362	Bug	Diagnostic	Diagnostic 0001. The logic to select LongText was Greater Than Threshold not Greater Than or Equal To Threshold. This was corrected.
1363	Bug	Diagnostic	Diagnostic 0015 modified to report "RadioButton (Horizontal) was expected" rather than the less precise "RadioButton was expected".
1364	Feature	Diagnostic	Diagnostic XLS report now includes a column "Settings" which shows which settings were in effect for the Diagnostic run when the result was generated.
1369	Feature	Diagnostic	A new setting was added to Diagnostic 0058 (Check Actions match Check Steps) to ignore inactive Checks with a default of true (on).
1311	Feature	Diagnostic	The number of findings displayed in the panel heading for each diagnostic on the diagnostic results page now decreases when findings are fixed so that it displays the current number of unresolved findings.
1312	Feature	Diagnostic	Diagnostic findings are now collapsed when opening the diagnostic results to make it easier to see an overview of which diagnostics have findings.
1437	Bug	Infrastructure / System	If a formatting mistake is made in the latest release or release notes then the document generation will display with these tables unformatted. The content is present but looks ugly. A test was added to ensure that these tables are formatted correctly.
1240	Feature	Permissions	Object lists now show a 'View' button if a user does not have access rights to edit or delete.
1108	Feature	Permissions	The URL Teams page now has a button to remove a user entirely from a URL. Previously a user would be removed from the URL when they were removed from their last project in that URL (so if they only had one Project and it was removed, so were they). A new button in the URL Team page is now the only way a user is permanently removed from all projects and the URL.
1258	Feature	Permissions	The URL Teams page "Teams" permission has been renamed "Manager" since this represents the master permission to change any of the other permissions for users.
1351	Bug	Rave Compatibility	Rave 2019.1.0 changed the way publish in place is reported. This affected the "Publish in Place" functionality of direct-Rave exports (causing it to fail). This was corrected.
1351	Bug	Rave Integration	Rave 2019.1.0 changed the way publish in place is reported. This affected the "Publish in Place" functionality of direct-Rave exports (causing it to fail). This was corrected.
1433	Feature	Retired	Unit Tests for Edit Checks and Derivations have been removed following the introduction of User Acceptance Tests.
1218	Bug	Standards	The Standard Compliance dropdown was not fully visible for rows at the bottom of object lists. This was corrected.
1350	Feature	Standards	ALS exports now include standard-library related properties for Forms, Fields, Data Dictionaries and Data Dictionary Entries. This allows standard library related metadata to be exported from one TrialGrid environment (e.g. beta) to another (production) via ALS export/import.
733	Feature	Standards	If a Draft object (Form, Edit Check, Folder, Custom Function, Dictionary or Test Case) is copied from a Library or another Draft then the sidebar will contain informaton about which object and Draft it was copied from. Standards Compliance information is now displayed in the object sidebar. Note that Derivations cannot be copied yet - this will be added in a future release (issue #1428).
1217	Bug	Study build	Some Custom Functions were not displaying correctly in the Object comparison view. This has been corrected.
1219	Bug	Study build	The Activity Record for setting the Standard Library for a Draft contained html markup. This has been removed.
1221	Bug	Study build	The list of Matrices was overflowing its panel container if the Draft contained more than 20 Matrices. This was corrected.
1223	Bug	Study build	The Object comparison view was incorrectly showing objects as being the same if the only difference was a line break at the end of a text property (Custom Function Source Code, for example). The objects were correctly shown as different elsewhere.
1224	Feature	Study build	The list of Matrices should be searchable.
1225	Feature	Study build	It is now possible to show or hide the highlighted difference between two objects in the Object Comparison view.
1226	Feature	Study build	It is now possible to show or hide the properties for the source or target object in the Object Comparison view.
1227	Feature	Study build	The number of changes within Custom Function Source Code is now displayed in the Object Comparison view.
1236	Bug	Study build	After making a change on the Draft Edit or Project Edit pages an alert is now shown if the user tries to leave the page before saving it.
1241	Bug	Study build	When a user does not have edit permission on a draft the message on the Unit Dictionary page incorrectly referred to 'Data Dictionary'. This has been corrected.
1244	Bug	Study build	After clicking the button to download a Draft the page scrolled to the top. This has been corrected.
1120	Bug	Study build	Matrix Editor now shows Inactive Forms with (Inactive) after the Form name and a red square at the intersection of Form and Folder instead of a blue one.
267	Feature	Study build	When 'multi-select' is enabled in the Matrices page 'Select all' and 'Select none' buttons are displayed and can be used to select all Matrices which are currently in the list (ie. the list can be searched and then the resulting Matrices selected), or clearing the selection.
1259	Feature	Study build	The Matrix grid can be printed, showing the Forms and Folders for the selected Matrix or Matrices.
1260	Feature	Study build	When 'multi-select' is enabled in the Matrices page the cells are color-coded: grey: no matrices have that Folder/Form green: one matrix has that Folder/Form orange: two matrices have that Folder/Form red: three or more matrices have that Folder/Form This makes it easy to spot matrices which have overlapping Folder/Forms.
1261	Feature	Study build	The Matrix grid can be expanded to occupy the full width of the screen.
1264	Feature	Study build	Clicking on a row header in the Matrix grid will open the corresponding Form. Clicking on a column header will open the corresponding Folder.
1289	Bug	Study build	Users could access a page to view or edit the Subject folder in a draft. This has been prevented and users will be re-directed to the Folders list in this case.
1298	Feature	Study build	The tooltip in the Matrix editor now displays the Matrices in which a Folder/Form combination are present (if any).
841	Feature	Study build	Entries in Data and Unit Dictionaries can be sorted by clicking on the Coded Data or User String column heading.
1414	Bug	Study build	The Edit Checks list would not display in Internet Explorer 11. This has been corrected.
1433	Feature	Study build	Unit Tests for Edit Checks and Derivations have been removed following the introduction of User Acceptance Tests.
1216	Bug	UX	Long Project or Draft names were causing an overflow in Activity lists. This has been corrected.
1233	Feature	UX	Generated user avatars displayed in the header bar now have a light background. Previously a dark avatar did not display well on a dark background.
1340	Feature	UX	Classic Rave versions 2018.2.4 and 2019.1.0 were added to the possible Rave versions.
1434	Feature	Validation	Validation documents now include a link between references in the source code to an issue and the documentation for that issue. This provides a link for auditors between an issue and the testing code that shows the issue is addressed or feature implemented.
1435	Feature	Validation	Validation documents now include a link between an issue and any testing scenarios (feature tests) related to that issue. This provides a link for auditors between the issue and the evidence that issue was addressed or feature implemented with visual test evidence.
1436	Bug	Validation	In validation documents some steps where text was input were not displayed correctly. This was corrected.