Module : Diagnostic

Issue	Type	TrialGrid Version	Description
3978	Feature	72	There are new settings to allow selection of which Rave and custom properties should be checked for diagnostics 0020, 0070, 0081, 0165, 0177.
3979	Feature	72	Diagnostics 0070, 0081, 0165 can now check custom properties and custom objects.
3971	Feature	72	Diagnostic PDF and Excel files which were generated more than 365 days ago will be automatically deleted. The number of days after which they will be deleted can be configured by contacting support@trialgrid.com.
3967	Bug	71	Diagnostics 0130, 0171, 0172, 0173, 0174, 0175 have been renamed for consistency and to correct duplicate names.
3906	Feature	69	Diagnostic 177, string substitution, was added. Diagnostic 29 performs word replacements but it splits text into words based on whitespace and punctuation and performs a case-sensitive replacement of a single word at a time. Diagnostic 177 acts more like a search and replace for a run of text across draft strings.
3907	Bug	69	When new Diagnostic settings are added to Diagnostics which have no original settings, the new settings are not automatically added to the existing Project Diagnostic instance. This could affect the copying of Diagnostic settings between drafts, causing the copy to fail. This was corrected.
3867	Feature	69	Diagnostic 169 was added that checks numeric formats of fields related to Lab Analytes.
3539	Feature	69	Diagnostic 170 was added to find placeholder text in Field PreText values.
3870	Feature	69	Diagnostic 171 was added. This checks that lab analyte fields do not have prompt for clinical significance set. This is the opposite of Diagnostic 130.
3871	Feature	69	Diagnostic 172 was added. This checks that lab analyte fields only have Control Types of Text and DropDownList.
3872	Feature	69	Diagnostic 173 was added. This checks that lab analyte fields do not have fixed units specified.
3873	Feature	69	Diagnostic 174 was added. This checks that lab analyte fields are not associated with Data Dictionaries which have the "Specify" option set since this is not supported functionality.
3874	Feature	69	Diagnostic 175 was added. This checks that lab analyte fields do not appear on mixed forms with both log and non log fields.
3875	Feature	69	Diagnostic 176 was added. This checks that Forms have Save Confirmation set to No Save Confirmation. It is the opposite of Diagnostic 114.
3821	Feature	68	Diagnostic 48 now allows a standard suffix as well as a standard prefix.
3822	Feature	68	Diagnostic 168 was added to check that the number of Fields on a Form is not over a limit.
3745	Feature	65	A new Diagnostic, 0167, will find any Log Forms which have Lab Analyte fields. This can cause performance issues in Rave.
3733	Feature	65	A new Diagnostic, 0166, will find any OpenQuery Check Actions which have a Marking Group different from the one specified for this Diagnostic, which defaults to 'Site from System'.
3697	Feature	64	It is now possible to filter the Forms list by both active and inactive Forms.
3700	Feature	64	A diagnostic settings report can now be downloaded as an Excel format file.
3682	Feature	63	Diagnostic 0020 (Spellcheck) now has an option to ignore custom properties and attributes where the attribute or custom property name matches a pattern.
3683	Feature	63	Diagnostic 0020 (Spellcheck) now has an option to ignore acronyms equal or greater in length than some user supplied value.
3684	Bug	63	In diagnostic results the reset selected explanations button was not always visible when there were explanations to reset. This was corrected.
3609	Feature	63	Diagnostic 0165 was added. This Diagnostic will find unbalanced quotes in text strings such as query messages.
3610	Feature	63	Diagnostic 0104 was updated so that the Form OID can be included in the expected path for a resource in the Help Text.
3670	Bug	62.1	Diagnostic 0020 (Spellcheck) would fail if an object had multiple custom properties, not all of the custom properties were excluded from checking and one of the excluded custom properties had a spelling finding. This has been corrected.
3632	Feature	62	Diagnostic 0020 (Spellcheck) will now spell check text custom properties with the ability to exclude named properties.
3616	Feature	61	It is now possible to reset a group of diagnostic explanations similar to the ability to explain a group of findings in the Diagnostic result and explanation management pages.
3573	Bug	60	Diagnostic 15 did not support length settings of a single value like "1" the value has to be entered as "1-1" or the diagnostic would fail. This was corrected.
3530	Feature	58	Diagnostic 164 was added. This can be configured to ensure a set of log fields have Default values that exactly match the list of entries in their related Data Dictionary (e.g. for Inclusion/Exclusion criteria default log lines).
1049	Feature	57	Diagnostic 163 was added that checks that defaulted fields are entry restricted against a set of EDC Roles.
3496	Feature	57	Diagnostic 161 was added. It reports on Check Step Static Values greater than 50 characters in length which are not allowed in Rave Architect.
3497	Feature	57	Diagnostic 162 was added. It reports on Derivation Step Static Values greater than 256 characters in length which are not allowed in Rave Architect. This check was also added to the Derivation editor.
3477	Feature	57	Diagnostic 104 now has a regex pattern match option so that help texts can be checked against more complex patterns.
3491	Feature	57	Diagnostic 108 now has an option to ignore form/folder combinations added by addform actions. This is set off by default.
3481	Feature	56	Diagnostic 141 identified inactive Forms, Fields, Edit Checks and Derivations. These have now been split into Forms (141), Derivations (158), Checks (159) and Fields (160) All existing settings are automatically migrated.
3460	Feature	56	Diagnostic 0026 now has an option to deactivate Checks and Derivations which reference inactive Forms and Fields.
3452	Feature	56	Diagnostics 108 and 133 now have Form exclusion options.
3456	Feature	56	Diagnostics now have an option per-diagnostic to allow fixes.
3440	Feature	56	Diagnostics 44 and 45 which find strings for replacement in Data Dictionary entries and Field Default values respectively now allow finding by regular expression pattern. This allows you to find all values within < and > for example (e.g. "<DrugName>" and "<CompanyName>" could both be found with an expression "/<.*?>/" See help or ask support for assistance with formulating expressions.
3428	Bug	54	There were some typographical errors in Diagnostic descriptions and setting descriptions. These were corrected.
3429	Bug	54	Diagnostic 0044 did not have enough options. The number of keywords was increased to 50.
2383	Feature	54	It is now possible to explain Diagnostic results in bulk.
1177	Feature	54	PDF and Excel Diagnostic result download buttons are no longer shown on the Diagnostic results page. Users were confused that updates to the page were not reflected in the output of these reports. To get updated reports, re-run diagnostics.
3247	Feature	54	An "Additional Information" field has been added to Diagnostic settings. This can be varied by Project and used to reference customer-specific checklists for example.
3393	Feature	53	Diagnostic 0001 now has an option to exclude by FormOID.
3394	Feature	53	Diagnostic 0002 now has an option to exclude by FormOID.
3395	Feature	53	Diagnostic 0006 now has an option to exclude by FormOID.
3396	Feature	53	Diagnostic 0013 now has an option to exclude by FormOID.
3397	Feature	53	Diagnostic 0013 now allows multiple prefix or suffix options.
3398	Feature	53	Diagnostic 0033 now has an option to exclude by FormOID.
3192	Feature	53	Diagnostic 0157 was added which checks that Fields which are IsVisible=False have a CheckAction in an Active Check to SetDataPointVisible(TRUE)
3367	Bug	51	When activating diagnostics on page 2 or higher of the Manage Diagnostics list, the view was changing to page 1. This has been corrected.
3362	Feature	51	Diagnostic 0028 now defaults to checking Data Dictionary Coded Data for double backslash characters. Existing project settings are not modified.
3268	Feature	51	Diagnostic 123 (Unsupported ePRO Field Settings) has been modified so that it will not report on Fields with default values if the ePRO control is 'NoCloudDisplay'.
3351	Feature	51	Diagnostic 155 has been added. This diagnostic checks that ePRO controls have been configured correctly. See Diagnostic 00155 : ePRO controls should be configured correctly for a list of the rules applied by this diagnostic.
3355	Feature	51	Diagnostic 156 has been added. This diagnostic checks that ePRO Forms have been configured correctly.
3347	Feature	51	Diagnostic 00147 (Folder/Form combinations included in a Matrix and an AddForm Check Action) was updated to match on Folder and Form.
2752	Feature	51	Diagnostic 152 was added. This Diagnostic checks Date/Time Field Data Formats against a list of acceptable formats.
1386	Feature	51	Diagnostic 153 was added. This Diagnostic checks that Matrices with Allow Add set also have a Maximum specified.
1387	Feature	51	Diagnostic 154 was added. This Diagnostic checks that Checkbox Fields do not have IsRequired set.
3343	Feature	51	The Diagnostics results page will display findings which are open before findings which have been explained.
3338	Bug	50	Diagnostic 00146 (Folder/Forms in overlapping matrices) did not properly handle wildcard exclusions (e.g. *PDF). This has been corrected.
3328	Bug	50	Diagnostic 0062 (Default values in Log Fields in a Form are consistent) could fail when multiple Log fields with different numbers of defaults were present on a Form. This has been corrected.
1269	Feature	50	Diagnostic 146 was added. This Diagnostic checks if Folder/Form combinations exist in more than one Matrix.
2178	Feature	50	Diagnostic 0069 now has a setting to exclude Matrices.
3155	Feature	50	Diagnostic 147 was added. This Diagnostic checks if a Form is included in a Matrix and in an AddForm Check Action for an active Edit Check.
3193	Feature	50	Diagnostic 148 was added. This Diagnostic checks if a Matrix is added or merged by more than one Check Action.
3195	Feature	50	Diagnostic 149 was added. This Diagnostic checks if an Edit Check has more than one Add or Merge Matrix Check Action.
3196	Feature	50	Diagnostic 150 was added. This Diagnostic checks if an Edit Check has an Add or Merge Matrix Check Action on a log Field or Variable.
3273	Feature	50	Diagnostic 151 was added. This Diagnostic checks if a Form is included in more than one AddForm CheckAction with the same Folder, or wildcarded Folder.
3313	Bug	49.2	When applying a fix, Diagnostic 70 was not updating fingerprints of CheckActions and the related Check. This was corrected.
3314	Bug	49.2	When applying a fix, Diagnostic 81 was not updating fingerprints of CheckActions and the related Check. This was corrected.
3272	Feature	49	Diagnostic 145 was added. This Checks that Form names do not contain individual words which are longer than 25 characters. These form names do not display well in Rave Classic.
3184	Feature	49	Diagnostic 143 was added. This Diagnostic checks if Data Dictionary Entries have Specify = True for customers who do not use Data Dictionary Specify option and prefer to have Specify always False with a separate "Other, Specify" field.
3183	Feature	49	Diagnostic 144 was added. This Diagnostic checks if Data Dictionary Entries Coded Data or User Data String contain html or "<string>" values since these block rendering in RaveEDC and in PDF Generator output.
3135	Feature	46	Diagnostic 26 would report Edit checks using variables which were inactive on ANY Form because it was understood that an Edit Check referencing such a Variable could not be published. The Diagnostic was changed to report only Variables which have no active instance at all. Now if the Variable is active for at least one Form then Diagnostic 26 does not report a variable-only step using that variable.
1378	Feature	46	Diagnostic 32 would report Fields which were the target of Variable-only Derivations. These Fields should have been ignored by this future-date check. This was corrected.
3077	Feature	45	Diagnostics 88, 89, 90, 91, 92, 93 and 94 now have an option to consider Log Fields with Default values ending in | as non-entry fields. An addition, fields with Default values can also now be considered non-entry fields via a setting.
2384	Feature	45	Diagnostics 88, 89, 90, 91, 92, 93 and 94 now have an option to ignore inactive Forms. Inactive fields are ignored by default.
3066	Feature	45	There is now a button to deactivate all Diagnostics from the Diagnostic management page.
1755	Feature	44	Diagnostic 142 was added to identify pipe (|) symbols in Default values for standard (non-log) fields. These can cause data-page save errors after a migration.
2883	Feature	44	Duplicate of 1755 above.
672	Feature	44	Duplicate of 1755 above.
3005	Feature	44	Diagnostic 55 was updated to include options for finding Forms with no active Fields as well as forms with no Fields at all.
2978	Feature	43	Diagnostic 70 option was changed from Ignoring all Field Pretext to ignoring Label fields (i.e. non-data entry fields).
2952	Bug	42	If Diagnostic 20 exclusions had linux-style line endings rather than Windows style (/r/n) the exclusions were ignored. This was corrected.
2953	Feature	42	Diagnostic 70 now allows entry of character numbers as well as unicode characters to ignore. You can now enter ß,160,å (160 is character code for non-breaking space).
2963	Feature	42	Diagnostic 70 now has options to ignore HelpText from Fields and Forms and Field PreText values.
2753	Feature	40	Diagnostic 00136 will check if more than a maximum number of Review Groups are set in Field properties.
2753	Feature	40	Diagnostic 00137 will check if more than a maximum number of Marking Groups are set in Check Actions.
2889	Feature	40	Diagnostic 00138 will check if any Field OIDs start with a number.
2691	Feature	40	Diagnostic 00139 will check that Forms with Lab Analyte Fields also have a Field which sets the Observation date (record or datapage date).
2890	Feature	40	Diagnostic 00140 checks that standards fields are positioned before log fields (with the exception of derived and label fields).
2882	Feature	40	Diagnostic 00141 finds inactive Forms, Fields, Checks and Derivations. The auto-fix will remove the inactive objects.
2866	Feature	40	The default for Diagnostic Import Settings is now Overwrite.
2867	Feature	40	The Activity Record for Diagnostic Import Settings now includes whether it was an Overwrite or Merge.
2868	Feature	40	Diagnostic 0047 has new settings. Coded Data can be checked case-sensitively only, and User Strings can be excluded from checking for duplicate entries.
2869	Bug	40	Merging Diagnostic Settings into a Project could lead to duplicate setting values. This has been corrected.
2816	Feature	40	Diagnostic 0033 now has an 'ignore inactive' setting, and will report on Fields which are not visible.
2808	Feature	40	Diagnostic 0134 will report text Fields with a format of $200 or longer which do not have query non-conformance set.
2809	Feature	40	Diagnostic 0135 will report Forms which are set to be EPRO Forms.
2810	Feature	40	Diagnostic 0016 has a new setting 'All Checks'. When this is set, the Diagnostic will report all Edit Checks which do not have Bypass During Migration set.
2817	Feature	40	Diagnostic 0016 has a new setting 'Ignore Inactive'.
2758	Feature	39	Diagnostic 0132 will find Forms and Fields which are View or Entry Restricted to specified EDC Roles.
2759	Feature	39	Diagnostic 0133 will find Forms and Fields which are View Restricted to specified EDC Roles.
2777	Feature	39	Diagnostic 0011 now reports findings grouped by Data Dictionary with all Fields listed.
2778	Feature	39	Diagnostic 0011 has a new configuration setting to exclude Data Dictionaries.
2774	Bug	37	Diagnostic #70 (find non-unicode characters) would not accept unicode whitespace characters such as non-breaking space (character 160) in the exclusion list. This was corrected.
2730	Feature	37	The 'Fix' button for Diagnostic findings will be labelled 'AutoFix' if the Diagnostic has AutoFix enabled. 'Fix All' will be labelled 'AutoFix All'.
2731	Feature	37	There will be a prompt to confirm that AutoFix should be run on all findings for the Diagnostic when 'AutoFix All' is clicked.
2713	Feature	36	Diagnostic 0035 (Missing SAS Label) now reports on invisible Fields and has a settings to Include Inactive Fields.
2715	Feature	36	The links to objects (Fields, Edit Checks, etc) in Diagnostic findings will now open in a modal window.
2716	Feature	36	When an object is open in a modal window it can be opened in the main window.
2623	Feature	35	When viewing Diagnostic results, the number of open findings and the number of explained findings will be displayed in the header for each Diagnostic.
2653	Feature	35	When viewing Diagnostic results, you can choose to view only Diagnostics which have open findings.
2657	Feature	35	Diagnostics can now have an associated TrialGrid Project Role.
2658	Feature	35	When viewing Diagnostic results, the list can be filtered to view only Diagnostic with a selected TrialGrid Project Role.
2659	Feature	35	The 'Category' column is now not displayed on the Manage Diagnostics page.
2660	Feature	35	Users require Manage Diagnostics permission to add Diagnotics to a Project or to change Diagnostic settings.
2507	Bug	32	When fixing text found by Diagnostic 0070, Check text for non-ASCII strings, if the text contained line breaks then the line breaks were being removed by the fix. This has been corrected.
2508	Feature	32	When fixing text found by Diagnostic 0070, Check text for non-ASCII strings, a textarea control is now used so that more text is visible.
2486	Feature	32	A new Diagnostic, 00130, will check that Fields with an Analyte Name also have Clinical Significance set.
2401	Bug	30	A typo was fixed in the description of Diagnostic 0058.
2339	Feature	27	A new Diagnostic, 0129, will find any Fields which are enterable by a Site Role (as defined in a configuration setting for the Diagnostic) and which do not have either the IsRequired Field level check set, and are not in an active Edit Check which has an OpenQuery Check action and the Field is in a Check step with an 'IsEmpty' step.
2328	Bug	26	Diagnostics with more than 60 field exclusion lines would cause the Report settings PDF to fail. This was corrected.
2310	Bug	26	Diagnostic 0091 would not accept an empty list of roles on save. This was corrected.
2302	Bug	26	Diagnostic 0069 reported Custom Functions using a Form OID that were not part of the current draft being checked. This was corrected.
2281	Bug	24	The ALS import function could import empty rows from Coder related tabs. This caused Diagnostic 0057 to fail with an error. This was corrected.
2271	Bug	24	Diagnostic 0026 now reports references to inactive Forms and Fields for Check Actions and Derivations as well as Check Steps.
2057	Bug	21	When Diagnostic 0076 made a change to a Field via a Fix it was not recording that it had made the change in the activity (audit) record. This was corrected.
1402	Bug	21	When Diagnostic 0027 made a change to a Check Action via a Fix it was not recording that it had made the change in the activity (audit) record. This was corrected.
2115	Bug	21	Diagnostic 81 setting "Ignore Form and Field Help" appeared in the settings for Diagnostic 0001. This was corrected.
2051	Bug	19	When Merging Diagnostics a Merge operation would fail for all Diagnostics that had already been added and deactivated. This was corrected.
2031	Feature	19	Diagnostic 0127 was added. This checks that the field SDV flag is not set for any Field. Typically you would use this Diagnostic when not using SDV at all or when relying only on Targeted SDV (TSDV) tiers with no default SDV set.
60	Feature	19	Diagnostic 0128 was added. This checks that the Field OID and FieldName are identical. Only organizations that enforce this requirement should use this Diagnostic.
1907	Bug	17	Diagnostic 0116 did not recognize dd- MMM- yyyy as a valid date. This was corrected.
1911	Feature	17	Diagnostics 0088 / 0089 / 0090 / 0091 / 0092 / 0093 and 0094 are designed to flag inconsistencies with "Data Entry" fields. In order to know which fields can be entered by Site Users a list of EDC Role View / Entry restrictions must be configured. Unless this configuration is done the Diagnostic will return false positives. These Diagnostics will now fail with a warning if they are not configured to stop users running them and being confused by results.
1910	System	17	The 'tokenizer' for extracting words from text for Diagnostic 00020 Spell Checking has been changed.
1909	Bug	17	Spelling Diagnostic 0020 was failing to run after a version upgrade. This has been corrected.
1895	Bug	17	Diagnostic 0015 was changed due to issue #1363 to display "RadioButton" as "RadioButton (Horizontal)" to distinguish it clearly from "RadioButton (Vertical)". However, this introduced a bug that using the Diagnostic Fix to change a value to the RadioButton type (non-vertical) changed the actual control type to "RadioButton (Horizontal)" which Rave does not accept. This should be "RadioButton". This was corrected.
1838	Bug	16	Diagnostic 0052 would suggest DATETIME22.3 for time fields (fields with formats like HH:nn). Time fields are stored as strings (not dates) in the database and should have string SAS formats. The Diagnostic was changed to suggest string formats for these fields. Generally, unless you have a good reason for setting a particular format it is better to leave SAS Format blank and allow SAS On Demand to choose SASFormats. Diagnostic 0109 can help you find any fields which have SAS Formats set.
1836	Bug	16	Diagnostic 0061 Valid HTML Tags would fail if a string contained the invalid tag '</br>'. This has been corrected.
1799	Bug	16	Diagnostic 0020 (Spell Check) was not creating an Activity Record against the Edit Check and was not updating the Edit Check fingerprint. This has been corrected.
1785	Bug	16	Settings for Diagnostic 0027 were being shown under the settings for Diagnostic 0023. This was corrected.
1773	Feature	16	Diagnostic 0126 was added. This ensures that Open Query actions have both RequiresResponse and RequiresManualClose set to True. This Diagnostic is useful to organizations that set up their Open Query Checks with these settings.
1384	Feature	16	Diagnostic 0125 was added. This checks that Open Query Check Actions which are set to Requires Response are also set to Requires Manual Close.
1062	Feature	16	Diagnostic 0124 Checkbox Fields should not have Default Values has been added.
1722	Feature	16	Diagnostic 0123 was added. This checks ePRO field settings for Default Value, Unit Dictionary and Data Dictionary with Specify options - none of which are supported by ePRO.
1699	Feature	16	Diagnostic 0122 was added. This checks the DataFormat of Date Fields on ePRO Form are using a DataFormat supported by Patient Cloud.
1704	Feature	16	Diagnostic 0082 now checks that Fields with a Coding Dictionary do not have a Unit Dictionary or a Lab Analyte.
1695	Feature	16	Diagnostic 00121 was added. This checks that Fields on ePRO forms use only supported control types (Text, LongText, DropDownList, Checkbox etc)
1691	Feature	16	Added Diagnostic 00120 Do not prefix Form OIDs with ECOA/EPRO - use Is Patient Cloud Form setting instead. A Prefix of ECOA or EPRO forces the Form to always be a Patient Cloud Form regardless of settings.
1676	Bug	16	Diagnostic PDF generation would fail if the content of a cell in the output table became longer than the page length. This could happen for long lists of excluded fields or long result output. In addition the limitation on 1,000 character output for a single Diagnostic result (one row) was removed and the display font was changed to a unicode aware font to support non-latin characters.
1599	Bug	16	Diagnostic 108 when a Folder/Form Combination exists only in the Merged Matrix being checked and in a Matrix excluded from comparison then the Diagnostic fails with an error. This was corrected.
1552	Bug	16	Diagnostic 0048 did not apply Field OID exclusions to Fields referenced via VariableOID. So if the exclusion was all Field OIDs with OID "DER_NOW" but the Derivation used a VariableOID reference like ":V_NOW" the Diagnostic did not apply exclusions to Fields with Variable OID "V_NOW" with Field OID "DER_NOW". This was corrected.
1558	Feature	16	Clicking the headings of panels in Diagnostics Findings page now expands/collapses those sections.
1450	Bug	15	Diagnostic 0051 (Fields should have a SAS Format specified) would fail on Fields with Numeric formats containing the + symbol such as 1+ or 3+.1+ This was corrected.
1311	Feature	14	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	14	Diagnostic findings are now collapsed when opening the diagnostic results to make it easier to see an overview of which diagnostics have findings.
1292	Bug	14	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	14	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	14	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	14	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	14	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	14	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	14	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	14	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	14	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	14	Diagnostic 0081 (detect trailing whitespace) now has an option to ignore Form and Field Help. This is set to True by default.
1281	Feature	14	Additional description was added to Diagnostic 81 to explain that trailing whitespace can affect PDF generation.
1285	Bug	14	Diagnostic categories included "Coder" and "Coding". Diagnostic categories were changed to just "Coding".
1286	Feature	14	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	14	Diagnostic 0111 was added. This checks that a set of named Custom Functions exist in a Draft.
1251	Bug	14	Diagnostic 0105 had duplicate exclusions settings. Exclusion settings for Diagnostic 106 had been assigned to Diagnostic 105. This was corrected.
1283	Feature	14	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	14	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	14	Diagnostic 0113 was added. This checks that Fields with a ControlType of DynamicSearchList do not appear on the Primary Form.
1045	Feature	14	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	14	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	14	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	14	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	14	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	14	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	14	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	14	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	14	Diagnostics 0088-0094 Diagnostic settings for Entry Restrictions were labelled as View Restrictions. This had no effect on functionality and was corrected.
1347	Bug	14	Diagnostics 0001,0064 and 0066 were ignoring the "ignore_inactive" setting. This was corrected.
1354	Bug	14	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	14	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	14	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	14	Diagnostic 0003 (SAS Field OID length) did not ignore Label fields. This was corrected.
1356	Feature	14	Diagnostic 0003 had a new option added to exclude Forms which match a name or pattern.
1359	Feature	14	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	14	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	14	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	14	Diagnostic 0001. The logic to select LongText was Greater Than Threshold not Greater Than or Equal To Threshold. This was corrected.
1363	Bug	14	Diagnostic 0015 modified to report "RadioButton (Horizontal) was expected" rather than the less precise "RadioButton was expected".
1364	Feature	14	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	14	A new setting was added to Diagnostic 0058 (Check Actions match Check Steps) to ignore inactive Checks with a default of true (on).
1288	Bug	14	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	14	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.
1230	Bug	14	Diagnostic 72 should not report empty values separated by | symbols.
1231	Feature	14	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	14	Diagnostic 64 now shows a link to Data Dictionaries that it reports.
1042	Feature	14	Diagnostic 104 was added to check that %% style Form Help Text entries which link to resources are set correctly.
1043	Feature	14	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	14	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	14	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	14	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)
1194	Feature	13	Diagnostic 66 now has an option to ignore Inactive Checks (default = Ignores inactive).
1195	Feature	13	Diagnostic 72 now has an option to ignore Inactive Checks (default = Ignores inactive).
1192	Bug	13	Diagnostics 0058, 0064, 0066, 0072 and 0098 did not correctly handle pattern-match exclusions, this was corrected.
1198	Feature	13	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	13	Diagnostic 1 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1200	Feature	13	Diagnostic 2 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1201	Feature	13	Diagnostic 3 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1202	Feature	13	Diagnostic 4 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1203	Feature	13	Diagnostic 5 now has an option to ignore Inactive Forms (default = Ignores inactive).
1204	Feature	13	Diagnostic 6 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1205	Feature	13	Diagnostic 7 now has an option to ignore Inactive Forms (default = Ignores inactive).
1206	Feature	13	Diagnostic 8 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1207	Feature	13	Diagnostic 9 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1208	Feature	13	Diagnostic 10 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1209	Feature	13	Diagnostic 11 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1210	Feature	13	Diagnostic 12 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1211	Feature	13	Diagnostic 13 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1212	Feature	13	Diagnostic 14 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1213	Feature	13	Diagnostic 15 now has an option to ignore Inactive Fields and Fields on Inactive Forms (default = Ignores inactive).
1193	Feature	13	Diagnostic 0020 now ignores words contained in URLs and does not attempt to spell check them.
1197	Feature	13	New Diagnostic 0102 finds URLs in draft text strings (Field help text for example) and checks if the URL can be accessed.
1187	Bug	13	Diagnostic 101 did not manage Formats with + after the decimal point properly (e.g. 3.2+). This was corrected.
1188	Feature	13	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	13	Diagnostic 64 did not ignore Inactive Edit Checks. A setting was added for this with a default of ignoring Inactive Checks.
1132	Feature	13	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	13	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	13	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	13	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	13	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.
1100	Bug	13	Diagnostic 0094 does not correctly report multiple checks linking to a field via VariableOID. This was fixed.
1106	Bug	13	When selecting a Project to copy Diagnostics from the dialog will sometimes not enable the Copy button. This was fixed.
1127	Bug	13	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.
1059	Bug	11	Diagnostic 099 would fail with an error message for Folders Actions with no Folder OID set but Folder repeat number set. This was fixed.
1020	Feature	11	Diagnostic 86 finds StaticValue Check steps with $ formats and incorrect lengths. It now also reports on invalid data string formats like "$2a", "$3.1" or "$" (no number).
1021	Bug	11	Diagnostic 86 was updated to check Derivation StaticValue steps as well as Check steps.
1024	Feature	11	Diagnostic 86 was updated with a new option to ignore $ formats which are too long for their value. e.g. TEST ($10) has a format which is 6 too long but this does not affect Rave.
1022	Bug	11	Diagnostic 04 was creating Activity Records with confusing descriptions e.g. "Form: 2 Field: AE DataFormat changed from AESLIFE to 1". This was corrected.
1012	Feature	11	Diagnostic 99 was added. This checks for Check Steps, Derivation Steps and Check Action Steps which have a FolderRepeat set but no Folder selected or a FormRepeat set but no Form selected. This is valid in Rave but is usually a mistake.
1017	Feature	11	Diagnostic 74 now has the Fix-All option.
431	Feature	11	Rave Clinical Views can include data from a maximum of 144 Fields per Form across all published versions and including Fields which are Active in any of those versions. Diagnostic 100 identifies Forms with a Field count greater than the limit you set. The Diagnostic may also inspect all Drafts in the Project for unique Fields.
1009	Feature	11	Diagnostic 101 was added. Like Diagnostic 86 it examines Step static values for Checks and Derivations. It identifies invalid Date/time and Numeric data formats as well as unknown Data Formats. For example, it can identify when DataFormat and Static value have been switched which Rave allows but is not valid.
1003	Feature	11	Diagnostic 96 was added. This checks that FieldOID is equal to VariableOID for Fields. Note that not all organizations have this standard check.
1001	Feature	11	Diagnostic 97 was added. This checks that Fields of type Signature are not used.
1000	Feature	11	Diagnostic 98 was added. This checks the length of SAS Labels. Rave allows up to 256 characters but some organizations have stricter limits. This diagnostic will find SAS Labels greater than a certain length. Note that in Clinical Views (and SAS On Demand) if no SAS Label is set for a Field then the Field Name is used. This Diagnostic can also check these default values.
997	Feature	11	New Diagnostic 0095, Lab Analyte should be unique in Form will find Fields on the same Form which have the same Lab Analyte Name.
975	Feature	9	Diagnostic 0071 : It is now possible to enter a list of EDC Roles that will be considered "Site Roles" (i.e. site data entry roles) by this diagnostic - overriding the "Site Role" switch in the URL Configuration. EDC Roles that exist in the configuration are colored Blue and Roles which are not present in the configuration are colored Orange as a warning that the system does not recognize these Roles.
976	Feature	9	Diagnostic 0085 was added. This checks the appropriateness of Signature Required setting for Forms where Signature Required=No (unchecked) but at least one Field Participates in Signature (at least one Field has DoesNotParticipateInSignature unchecked). Where Form Signature Required=No but there are fields which Participate In Signature then the Fields may not be able to be locked because they have not been signed.
978	Feature	9	Diagnostic 0087 was added. This checks the appropriateness of Signature Required setting for Forms where Signature Required=Yes (checked) but there are NO (active/visible) Fields on the Form. In this case there are no Fields which can be signed.
968	Feature	9	Diagnostic 0086 was added. This checks that Static Values with $ formats in Check Steps are the correct length. For example, a value of "YES" with $2 appears to Rave as "YE" so this should be a $3 format.
864	Bug	9	If Diagnostic results contained HTML (e.g. because a Field PreText contained HTML content) then this content would not be displayed properly in Diagnostic PDF reports or might cause the PDF generation to fail entirely. HTML content is now properly handled in Diagnostic PDF reports.
970	Bug	9	Diagnostic 0053 was taking into account Field Ordinals and would fail to find differences in the use of the same VariableOID when Fields had different Ordinals (e.g. VariableOID name used in two Fields but with different Formats - which is impossible in Rave but can happen if you edit the ALS and upload it). This was corrected.
981	Feature	9	Diagnostic results PDF now has a table of contents and outline bookmarks added for easier navigation.
985	Feature	9	Running Diagnostics now adds an event to the activity history for the Draft.
977	Feature	9	The Diagnostic report is now available as an .xlsx download (Microsoft Excel) as well as a PDF download. The Excel version is simplified and appears in just one sheet so that it can be easily filtered.
982	Feature	9	Added Diagnostic 0088: Data Entry Fields should participate in Signature. See Diagnostic Catalog for details.
983	Feature	9	Added Diagnostic 0089: Data Entry fields should require Verification. See Diagnostic Catalog for details.
984	Feature	9	Added Diagnostic 0090: Data Entry Fields should be Visible. See Diagnostic Catalog for details.
986	Feature	9	Added Diagnostic 0091: Non-Data entry Fields should not Participate in Signature. See Diagnostic Catalog for details.
987	Feature	9	Added Diagnostic 0092: Non-Data entry Fields should not Require Verification. See Diagnostic Catalog for details.
988	Feature	9	Added Diagnostic 0093: Non-Data entry Fields should not be Required. See Diagnostic Catalog for details.
989	Feature	9	Added Diagnostic 0094 : Non-Data entry Fields should not have Edit Check Query Actions. See Diagnostic Catalog for details.
990	Bug	9	Diagnostics reporting strings with <core:string in them (e.g. spellcheck) cause PDF generation to fail. These are now rendered correctly in the PDF and do not cause it to fail.
136	Feature	9	When a change is made via a Diagnostic, this is reflected in the audit trail with a small badge next to the audit trail entry which shows the short-id number of the Diagnostic (e.g. 0001) In the full audit listings (at user, URL, Project and Draft level) Diagnostic short names also have their own column in the table. Note this badge is only shown for Diagnostic results from runs made after this change, not historical results. (Duplicate of #965)
945	Bug	9	Updated Diagnostic 0015 Dictionary Fields are of appropriate display type. The Diagnostic now allows overlap in ranges which provides greater flexibility. The Diagnostic has also been split to provide ranges for Portrait Forms separate from Landscape Forms since on Landscape grid Forms Dictionaries are often set as DropDowns in order to conserve space. See the Diagnostics page for more details on the change to this Diagnostic.
948	Feature	9	Diagnostic 0040 Field OIDs should be Unique : category was changed from Best Practice to TrialGrid Diagnostic and its description updated to make clear that Rave does not require Field OIDs to be unique across all Forms. This Diagnostic exists for organizations which have this practice. The reporting message was clarified and the Audit Trail record also updated to show where VariableOID is also changed (VariableOID is changed to match FieldOID if VariableOID = FieldOID)
547	Feature	9	Diagnostic 0040 Field OIDs should be Unique : category was changed from Best Practice to TrialGrid Diagnostic and its description updated to make clear that Rave does not require Field OIDs to be unique across all Forms. This Diagnostic exists for organizations which have this practice. The reporting message was clarified and the Audit Trail record also updated to show where VariableOID is also changed (VariableOID is changed to match FieldOID if VariableOID = FieldOID) (Duplicate of #948)
956	Feature	9	Audit records created by Diagnostic 0076 (Correct Recordposition for log fields) now includes the name of the Check or Derivation and when Recordposition is changed to a wildcard this is now reported as a change to "wildcard" rather than "".
947	Feature	9	Add help to Diagnostic 0002, 0003 and 0030 to make clear where a Diagnostic is testing for a length (e.g. an OID length) whether the length value is inclusive or exclusive.
916	Bug	9	Diagnostic 0016 Bypass During Migration for Balance Check Actions would fail on fix for SendMessage actions. Note that Rave cannot import SendMessage actions from an ALS so it is not advised to edit these with TrialGrid. The fix failure was corrected and a link to the Check was also added to the report message to make it easier to review the Check.
894	Feature	9	Diagnostic 0016 Includes the Balance PSALUpdate check action.
958	Feature	9	Updated Audit Messages for greater detail for Diagnostics 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008, 0009, 0010, 0013, 0014, 0016, 0022, 0023, 0024, 0025, 0031, 0032, 0033, 0034, 0035, 0036, 0037, 0038, 0040, 0041, 0042, 0044, 0045, 0046, 0047, 0048, 0052, 0053, 0056, 0061, 0065, 0067, 0071, 0073, 0074, 0078, 0083 and 0084.
949	Feature	9	A new option was added to Diagnostic 0028 Valid Data Dictionary Coded values. Rave 2018.1.0 allows commas (,) and semicolons (;) but does not allow double backslash (\). The new option sets this Diagnostic to Rave 2018.1.0+ mode.
938	Feature	9	Print options for Diagnostics were changed to generate only a PDF version of the current Diagnostic listing. This PDF version includes all settings. Previously the print options did not include the settings.
962	Feature	9	Diagnostic 0081 Check text strings for trailing whitespace : when reporting a Field property, the report now includes the OID of the Form.
282	Bug	9	Inactivating a Diagnostic would remove all explanations for that Diagnostic and re-activating it would reset all settings to their defaults. The design was changed to correct this.
939	Feature	9	Changes to Diagnostic settings were not audit trailed. This has been corrected.
892	Bug	9	Diagnostic 0041 should explain what the Fix action will do. This explanation was added.
898	Feature	9	Diagnostics 0083 and 0084 were added to identify Forms and Fields which do not have Custom Properties set.
791	Feature	9	A "Fix All" button was added for Diagnostics which are Auto-Fix. This will auto-fix all Diagnostic results, running a task in the background so that the user is not blocked from continuing to work. Note that results with Explanations are not modified.
866	Feature	7	Diagnostic 81: Strings Ending in Whitespace now includes Constant value Check Steps.
867	Bug	7	Diagnostic 50 would fail if a Float or Integer DataFormat included the + modifier to ensure exact number of digits. Diagnostic would also not recognize negative numbers as valid for numeric formats. These issues were corrected.
872	Bug	7	PDF of Diagnostic results did not handle newlines correctly which affected readability of results. This was corrected.
856	Feature	7	Added Diagnostic 0080 : Medical-Coded fields may not have Data Dictionaries associated with them.
840	Feature	7	Updated description for Diagnostic 0055 to note that it Deletes unused objects from the Draft.
837	Feature	7	Added Diagnostic 00081 : Look for Whitespace at the end of Text values (e.g. Carriage Return at end of Query Text)
858	Feature	7	Added Diagnostic 0082 : Medical-Coded fields must have a Text Format. Note that Diagnostic 0057 does this for Coder-related fields.
815	Feature	7	Diagnostic 0079 was added to identify Edit Checks with SendMessage Check Actions. These cannot be loaded into Rave via ALS correctly because of Rave issue DEV-3145 so should be checked when imported into Rave.
135	Feature	7	When Diagnostics have a Fix option there is now a description of what the Fix will do.
783	Feature	7	New Diagnostic 00078 checks for use of 'DataStatus' in Edit Checks and Derivations, fixing it to 'DataPoint'.
792	Feature	7	Diagnostic 00027 (Standard Fields in Edit Checks and Derivations which do not have RecordPosition 0) did not include the Derivation target. This has been corrected.
803	Bug	7	Sometimes when activating diagnostics the list would move position and scroll. This has been fixed. The Diagnostic Category is now displayed as a column in the table and not as a row group.
805	Feature	7	New Diagnostic 00077 checks for use of File Upload control, which is not compatible with RaveX.
807	Bug	7	Diagnostic 00063 was incorrectly reporting results if 2 or more Edit Checks referenced the same DSL with the same Action target. This has been corrected.
808	Feature	7	New Diagnostic Categories have been introduced, replacing the previous categories. See Diagnostics.
793	Bug	7	Diagnostic 0015 would fail if values were left out of the settings. Leaving a setting (e.g. RadioButton Horizontal) to empty or 0-0 will now make the Diagnostic ignore that category.
712	Bug	6	Entering an explanation for an object with an identifier (e.g. Edit Check Name) of greater than 50 characters causes an error and the explanation is not saved. This was fixed with identifiers now allowed up to 2000 characters).
707	Bug	6	The number of database queries needed to run Diagnostics has been reviewed and optimized. Diagnostics will now run faster.
708	Feature	6	When Diagnostic 00020 (Spell Check) finds new words which are not in the TrialGrid dictionary it will log the word and suggested correction (if any) for review by TrialGrid administrators, who will decide whether or not to include it in the TrialGrid dictionary.
709	Bug	6	Diagnostic 0070 failed if there is a non-ascii character in a EmailAlert text field. This was fixed.
703	Bug	6	Diagnostic 0058 - Checking Edit Check Steps and Actions was checking that ALL check actions have a matching check step when there needs to be only one matching Step/Action. This was fixed.
696	Bug	6	When on manage Diagnostics Exclusions page, clicking breadcrumbs for Manage Diagnostics resulted in a page not found error. This was fixed.
684	Bug	6	Diagnostic 0068 did not work correctly where there were Variable-only Derivations (e.g. Derivations that only reference the VariableOID, no Field reference). This was corrected.
676	Bug	6	Diagnostic 0068 (Date Fields not covered by configured Edit checks) was incorrectly identifying fields only by VariableOID. The Diagnostic now takes into account Form and Field OID where these are set in a Check Step.
677	Feature	6	Diagnostic 0075 was introduced to check Data Dictionary names. Some users have requirements for the naming of Data Dictionaries. This Diagnostic uses regular expressions to determine valid patterns for the naming of Data Dictionaries. Regular expressions are powerful but can be complex to write. If you have a requirement for Data Dictionary naming we will be happy to assist you with writing the regular expression.
678	Feature	6	Diagnostic 0027 is used to report situations where Standard Fields are not referenced with RecordPosition=0 in Edit Checks and Derivations. This is a stylistic finding which will not always affect the performance of an Edit Check or Derivation. However, 0027 also reports a more serious condition of Log fields being Referenced with RecordPosition=0 which is a more serious error. For that reason, this Log Fields with RecordPosition=0 references are now reported in a separate Diagnostic 0076.
648	Bug	6	Diagnostic 0062 (Data Dictionary Field Default Values appear in Data Dictionary) was duplicated by Diagnostic 0073 which had the same functionality. Diagnostic 0062 was re-programmed to check for Log Field Default Value consistency.
656	Feature	6	Diagnostic 0074 recognizes a Link style of "" as NoLink. Previously if an ALS was uploaded with an empty LinkStyle the diagnostic would report it as not supported by RaveX which was incorrect.
664	Feature	6	Diagnostic 0032 (Dates with Query Future Date not set) now has an option to ignore Inactive Forms. Diagnostic will need to be inactivated and then re-activated to include this option.
662	Feature	6	Diagnostic 0069 (Forms not used in Study) now has an option to ignore Inactive Forms. Diagnostic will need to be inactivated and then re-activated to include this option.
663	Feature	6	The Diagnostic results page now shows the values of Diagnostic settings to make it clear what is being excluded from checks. The PDF report already showed this information.
666	Bug	6	Time Fields were removed from the checking performed by Diagnostic 0038 (Fields which do not require non-conformance checks). Data entry in time Fields may be non-conformant.
166	Bug	4	The number of findings for the latest diagnostic run for a Draft is now updated when findings are fixed or explained, so that the number of unresolved findings is displayed.
604	Bug	4	Diagnostic 0020, Spell checking, can generate multiple findings for the same Draft object, for example, several entries within a Data Dictionary may have findings. Prevoiusly entering an explanation for one finding for the Dictionary would explain all findings for that Dictionary. Now each explanation applies to one finding only.
605	Feature	4	Findings from Diagnostic 0020, Spell checking, now have links to Data and Unit Dictionaries.
607	Feature	4	When an explanation of a Diagnostic finding is reset, the Fix button will be re-displayed when a fix is available.
608	Feature	4	Findings from Diagnostic 0020, Spell checking, now display the Form OID for findings related to a Field in addition to the Field OID.
647	Bug	4	Diagnostic 0020, Spell checking, was incorrectly reporting findings if an html tag separated two words, for example 'severe<b>reaction</b>' would be reported as 'severereaction'. This has been corrected.
646	Feature	4	A new Project Level permission (Explain Diagnostic Result) was introduced which controls whether a user may explain a diagnostic result or reset a diagnostic explanation.
2655	Feature	4	Users can reset diagnostic explanations if they have permission to do so.
2654	Feature	4	Users can explain diagnostic findings if they have permission to do so.
637	Feature	4	Diagnostic 00074 has been added to identify Form Redirect settings which are not valid for RaveX studies (currently only "NoLink" setting is valid)
639	Feature	4	Diagnostic results are now ordered by the reference number of the Diagnostic (e.g. 0001, 0002...) PDF reports generated before this change still appear in the previous ordering.
618	Bug	4	Non-ASCII characters in Edit Check or Derivation names were causing some Diagnostics to fail. This has been corrected.
620	System	4	Some Diagnostics were generating errors in the system log when reporting results of fixing back to the user. This had no impact to users but has been corrected.
576	Feature	3	Diagnostic 00020 (Spell Check) has a new option to exclude Folder, Form and Field OIDs from the spell check. To activate this option on existing Project Diagnostics, please inactivate and reactivate the Diagnostic (note this will clear any existing exclusion settings).
263	Feature	3	Diagnostic 00054 (Unused Objects) now reports if a Custom Function might be called by another Custom Function.
578	Feature	3	Diagnostic 0070 (Non-ASCII characters) was expanded to cover Data Dictionary Name, Unit Dictionary Name, Custom Function Name and Matrix Name.
597	Bug	2	Diagnostic 0011 "fix" code was taking too long to run in some instances. Code was refactored to improve performance.
598	Bug	2	When working with Diagnostic display list previous value of Diagnostic fix was displayed then replaced with the current default (or empty if no default). This value is now cleared after every fix and Fix button now also shows a "working" icon while diagnostic is running.
601	Bug	2	On the Draft Home page the date of the last Diagnostic run was displaying as 'Unknown date' in the Firefox browser. This has been corrected.
588	Feature	2	Diagnostic PDF Report was redesigned to make better use of space / less paper if printed.
137	Feature	2	Reviewed Diagnostics 1-18 for effects of deleted or changed objects since diagnostic was run. This prevents fix failures if object has been changed or deleted since diagnostic ran.
446	Feature	2	When copying Forms, Edit Checks or Diagnostics Settings from another Project or Draft the list will be ordered by URL, if the user has access to more than one URL.
556	Feature	2	Added <small> tags to the list of html tags allowed by Rave in Field Pre Text (question text) and by Diagnostic 0061. Note that <small> tags render as normal sized text in Rave PDFs.
549	Feature	2	Added Diagnostic 0073 which will detect if the Default Value(s) of a Field linked to a Data Dictionary are valid for that Data Dictionary.
455	Bug	2	Diagnostic 00054 'Unused Objects' was incorrectly reporting Custom Functions as being unused if they were used in a Set Dynamic Search List Check Action. This has been corrected.
551	Feature	2	Diagnostic 00011 'Fields using the same dictionary have identical format' now suggests a Data Format based on the longest entry in the Data Dictionary.
554	Bug	2	Diagnostic 00069 'Identify Forms not included in a Matrix or in an AddForm Check Action' was reporting the Primary Form as being not included. The Primary Form will not now be reported since it is automatically available on creation of a new Subject in Rave.
555	Feature	2	Diagnostic 00069 'Identify Forms not included in a Matrix or in an AddForm Check Action' will search Custom Function code for references to the Form OID and include any such Custom Functions in the diagnostic finding.
508	Bug	2	Diagnostic 70 (Non-ascii characters) now checks Field Number property, this was omitted before.
465	Bug	2	Diagnostic 61 (html tags) did not support ul and ol tags. This was fixed.
276	Feature	2	Diagnostic 00072 will detect any Edit Checks which have the same check logic and check actions. The Diagnostic can also be configured to detect Edit Checks which have the same check logic but have different actions, and/or Edit Checks which have different check logic but the same actions.
439	Feature	2	Added Diagnostic 00071 which identifies Required fields which are not visible/editable by the site
441	Bug	2	EDC Role Diagnostic 0021 fails in usage but not in tests. Issue was found and fixed.
394	Feature	2	Diagnostics: Import settings from multiple Projects, combining the settings. This feature was added by introducing a selection between "Overwrite" and "Merge". See the help from the Diagnostic management page for more detail.
261	Feature	2	DataDictionary Specify/QueryNonConformance Diagnostic (0042) should have link for the Field. Link to Field was added.
304	Feature	2	Added Diagnostic to find Forms not in Matrices and not in an AddForm Check Action on an active Check. Diagnostic includes ability to exclude Forms (00069)
209	Feature	2	Added Diagnostic for non-ascii characters in text fields. These can render poorly in PDFs and are often introduced by accident via Cut & Paste from other sources. Includes capability to exclude certain characters (00070)
406	Bug	1	Diagnostic 00042 says it excludes by Data Dictionary Name but actually excludes by Field OID. Fix was to update the diagnostic help text and to add a new parameter that excludes by Data Dictionary Name. Users may need to remove (inactivate) and re-activate this diagnostic to see this change. Note, de-activating a diagnostic will remove any settings already entered so manage this change with care.
353	Bug	1	Diagnostic result endpoint used to request fixing diagnostic findings can return a 500 Server Error Response for Diagnostic 61. The diagnostic was fixed. NOTE: Diagnostic results created prior to this fix may still exhibit this error when you try to "fix" because the code to fix the issue is stored in the database and is now out-of-date. Re-run diagnostic and fix will work.
361	Bug	1	HTML Content Diagnostic (61) should provide a link to the folder when correcting Folder Name. Folder link was added.
330	Bug	1	Diagnostic 00020 (Spell check) would fail to fix the reported spelling mistake if the correction contained unicode characters. This has been fixed.
230	Feature	1	A new setting has been added to the following Diagnostics to allow objects (Fields, Data Dictionaries, Edit Checks, etc) to be excluded if the object identifier is excluded or matches an exclusion pattern: 00022 FormOIDs should not start with numbers 00023 Date Fields should have a consistent naming suffix or prefix 00024 Time Fields should have a consistent naming suffix 00025 Date/Time Fields should have a consistent naming suffix 00026 Active Checks should not reference inactive Forms or Fields 00027 Valid Record Positions for Standard and Log Fields in Edit Checks and Derivations 00028 Data Dictionary CodedData should not contain commas or semicolons. 00030 Custom Function length 00031 Edit Check SYS_ prefix 00032 QueryFutureDate should be set for Date and DateTime Fields 00033 Numeric fields should have query non-conformance set 00034 Fields which require translation should not also be marked as required 00035 Data entry Fields should have a SAS Label 00036 Fields with default values should not have SDV set 000037 Fields with default values should not be set as Required 00038 Checkbox, Data Dictionary and Time Fields should not be set to Query for Non-Conformance 00039 All question Fields should have a pre-text label 00040 Field OIDs should be unique 00041 Data Dictionaries should not have a coded value of 0 (Zero) 00042 Consider setting QueryNonConformance for Fields related to Data Dictionaries with a Specify option 00043 Data Dictionaries should be unique 00044 List of keywords to be substituted in Data Dictionary 00045 List of words to be substituted in Draft Field Default Value 00046 Place Sticky Check Action should not contain HTML tags 00047 Data Dictionaries should not have duplicate Coded Values or User Values 00048 Derived Fields should have a standard prefix 00049 Data format must be valid for Field control type 00050 Data format must be valid for associated Data Dictionary 00051 Fields should have a SAS Format specified 00052 SAS Format should match Rave Field Data Format 00053 Variables should have consistent properties 00054 Unused objects (Data Dictionaries, Unit Dictionaries, Custom Functions) 00055 Empty objects (Forms, Data Dictionaries, Unit Dictionaries, Custom Functions, Matrices) 00056 Fields associated with Coder Dictionaries should have an OID of less than 20 characters length 00057 Fields associated with Coder Dictionaries should have string formats 00058 Check Actions should have a matching Check Step 00059 Custom Functions used in RaveX should not use blacklisted methods 00060 IsPresent Check Action 00061 Valid HTML tags 00062 Default Values should be in associated Data Dictionary 00064 Edit Check Coded Value steps should be compared against valid Data Dictionary Entries 00065 Fields which are not Date or Time Fields should not have date related properties set 00066 Checkbox Fields should not have an IsEmpty or IsNotEmpty step in Edit Checks 00067 Forms should have unique names
278	Feature	1	A diagnostic that checks that date fields are compared against at least one other date field is required. Diagnostic 0068 was added with this function.
279	Feature	1	Diagnostics should have a visible unique identifier to make referring to them easier. A unique identifier was added to the display of diagnostics in the Diagnostic results and Diagnostic Management pages. The identifier was included in the PDF output of Diagnostic results.
280	Bug	1	Diagnostics management form does not filter by properties after a reload of the page. This bug was fixed.
281	Bug	1	When a new setting is added to a diagnostic, the Project instance of that Diagnostic is not updated with the new setting. Code was added to achieve this and a database migration was also added to update any existing Diagnostics with new settings (e.g. new Field/Form exclusion settings from last release)
266	Feature	1	Matrices have been added to the Empty Objects Diagnostic and will be raised as findings if there are no Folders/Forms in a Matrix
256	Bug	1	Rave gxml such as '<core:link folderoid="AE" formoid="SAE" text="SAE form"></core:link>' was incorrectly flagged as invalid by the Place Sticky HTML Diagnostic, and caused Diagnostic pdf generation to fail. The Invalid HTML strings Diagnostic will correctly flag gxml as being not allowed, and will now autofix invalid strings. It will also flag forbidden HTML tags and attributes such as '<body>' and 'onclick'.
259	Feature	1	The Invalid HTML strings Diagnostic now checks Folder Names in addition to Field strings.
240	Feature	1	Derived Fields are excluded from the Diagnostic which checks if QueryNonConformance has been set on numeric Fields
241	Feature	1	Derived Fields are excluded from the Diagnostic which checks if QueryFutureDate has been set on date Fields.
170	Feature	1	The layout of the Diagnostics help page was improved to make Diagnostic titles clearer.
3701	Feature	1	It is now possible to search and filter diagnostics in the diagnostic management page.