Version : 9

Released : 2018-10-29

Changes in this Release

Issue	Type	Module(s)	Description
895	Feature	Custom Properties	Users can now Define Custom Properties for Forms and Fields at the URL level. See Help on Properties for more information on this feature.
2913	Feature	Custom Properties	Custom properties may be deleted from the URL, deleting a custom property definition will remove that custom property from all objects along with any value set.
896	Feature	Custom Properties	A count of Custom Properties appears on the URL home page.
897	Feature	Custom Properties	The "Properties" tab for Forms and Fields shows all custom properties defined at the URL level. Values entered for these properties are exported into the ALS and can be re-imported into TrialGrid. Note that Rave ignores these custom properties.
899	Feature	Custom Properties	Creation of Custom Property Definitions is controlled by a permission at the URL level.
900	Feature	Custom Properties	Custom property names and values are shown in the listing for the Object to which they are assigned (i.e. the Form or Field listings in the Draft area)
901	Feature	Custom Properties	Whether a Custom Property is shown in the Object Lists can be controlled by the "Show in Lists" checkbox on the Custom Property Definition at URL level.
902	Feature	Custom Properties	To avoid confusion with Custom Properties the "Properties" column of the Field and Form lists was renamed to "Summary" since it summarizes key properties of the Form or Field such as Log Direction or whether a field is Log.
892	Bug	Diagnostic	Diagnostic 0041 should explain what the Fix action will do. This explanation was added.
898	Feature	Diagnostic	Diagnostics 0083 and 0084 were added to identify Forms and Fields which do not have Custom Properties set.
791	Feature	Diagnostic	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.
939	Feature	Diagnostic	Changes to Diagnostic settings were not audit trailed. This has been corrected.
945	Bug	Diagnostic	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	Diagnostic	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	Diagnostic	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	Diagnostic	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	Diagnostic	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	Diagnostic	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	Diagnostic	Diagnostic 0016 Includes the Balance PSALUpdate check action.
958	Feature	Diagnostic	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	Diagnostic	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	Diagnostic	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	Diagnostic	Diagnostic 0081 Check text strings for trailing whitespace : when reporting a Field property, the report now includes the OID of the Form.
282	Bug	Diagnostic	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.
136	Feature	Diagnostic	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)
975	Feature	Diagnostic	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	Diagnostic	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	Diagnostic	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	Diagnostic	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	Diagnostic	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	Diagnostic	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	Diagnostic	Diagnostic results PDF now has a table of contents and outline bookmarks added for easier navigation.
985	Feature	Diagnostic	Running Diagnostics now adds an event to the activity history for the Draft.
977	Feature	Diagnostic	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	Diagnostic	Added Diagnostic 0088: Data Entry Fields should participate in Signature. See Diagnostic Catalog for details.
983	Feature	Diagnostic	Added Diagnostic 0089: Data Entry fields should require Verification. See Diagnostic Catalog for details.
984	Feature	Diagnostic	Added Diagnostic 0090: Data Entry Fields should be Visible. See Diagnostic Catalog for details.
986	Feature	Diagnostic	Added Diagnostic 0091: Non-Data entry Fields should not Participate in Signature. See Diagnostic Catalog for details.
987	Feature	Diagnostic	Added Diagnostic 0092: Non-Data entry Fields should not Require Verification. See Diagnostic Catalog for details.
988	Feature	Diagnostic	Added Diagnostic 0093: Non-Data entry Fields should not be Required. See Diagnostic Catalog for details.
989	Feature	Diagnostic	Added Diagnostic 0094 : Non-Data entry Fields should not have Edit Check Query Actions. See Diagnostic Catalog for details.
990	Bug	Diagnostic	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.
937	Feature	Infrastructure / System	Changes to Project roles were not audit trailed. This has been corrected.
922	System	Infrastructure / System	Upgraded infrastructure.
979	Feature	Infrastructure / System	As Diagnostics are changed over time, new settings are added to them and instances of Diagnostics that have been added to Projects should reflect those changes. To ensure that this is the case a new deployment check was added that compares the count of settings for each Diagnostic to the count of settings of each Project Instance of that Diagnostic. If the results do not match then Diagnostics have not been updated properly and the deployment fails.
903	Feature	Permissions	All URL Users Can View setting for Projects is now shown in the Project List.
904	Feature	Permissions	Project Owner Setting in New Project / Project Edit page is now marked with * since a Project must have an owner.
905	Feature	Permissions	When a Project is marked as "All URL Users Can View" any user with the ability to import objects (Forms, Edit Checks etc) in that URL can import from that Project - even if they do not have a Project role in that Project. This is useful for Standard Library Projects to allow all users in the URL to import objects from the Library without being invited to that Project.
906	Feature	Permissions	Users now have all permissions within Projects that they own. If a user is a Project Owner and also has been assigned a Project Role within a Project, their owner rights take precedence. Users no longer need to be invited to projects they own.
907	Feature	Permissions	There is now a separate Project-level permission for managing of Files in a Project.
931	Feature	Permissions	When hovering the mouse over a Permission in the Project Permissions definitions lists, a description of the Permission is now shown as a pop-up hint.
913	Bug	Standards	The 'fingerprints' of Check Actions and Derivations were not being calculated correctly on import of an ALS spreadsheet, leading to incorrect standards compliance comparisons. This has been corrected.
929	Bug	Study build	When using Internet Explorer in a Draft connected to a Standard Library the list of Forms would sometimes not be displayed. This was corrected.
847	Feature	Study build	FixedUnit in Field properties was not enabled for all Field Control types. It is now enabled for all Control types.
887	Bug	Study build	Typing appeared slow in Header Text attribute of Field, especially in Internet Explorer. This was corrected.
909	Bug	Study build	HeaderText, Draft Field Number, Data Format, Fixed Unit, Default Value, SAS Label, SAS Format and AcceptableFileExtensions fields were all set to accept only the same limit characters as Architect.
910	Bug	Study build	When uploading an ALS with a Field text element (such as PreText) longer than the allowed size, the upload would fail. The system now gives a warning that these attributes will be truncated to their acceptable length. It truncates the attributes and the import no longer fails.
914	Bug	Study build	Whitespace was being automatically stripped from Field PreText (label), HeaderText and other text attributes. This auto-removal of whitespace was disabled. Note that Diagnostic 81 will identify Fields with trailing whitespace in these attributes.
917	Bug	Study build	System was blocking some html tags from being entered for field PreText. Rave allows a lot more html tags than are listed in the "allowed html tags" reference for Rave. The system no longer blocks tags being entered but it does ignore some tags for display and show a warning of which html tags are not being displayed.
921	Bug	Study build	When comparing two Drafts Test Steps related to Edit Checks / Derivations would appear in the compare list. These belong only in comparison of Edit Checks and were removed from Draft compare.
912	Bug	Study build	Copying Data Dictionaries by copying and pasting from an existing Dictionary and including the Specify column to create the new dictionary would cause an error on save. This was fixed.
873	Bug	Study build	When Rave Matrix OIDs are long, Architect sometimes removes spaces from the OID in an attempt to fit into the maximum 32 character Excel Worksheet name. This issue was already managed in the system but a test was added to show that the system imports these Matrices correctly.
935	Bug	Study build	When applying an existing Variable to a Field in the Form editor the control type was always changed to text. Now control type is shown in the Variable list and the Control Type is changed to the same as the Variable chosen.
961	Feature	Study build	Rave 2018.1.0 introduced the HH+ and hh+ time formats. These are now supported.
381	Feature	Study build	A description of the Derivation logic is now displayed in the Derivation editor page.
529	Feature	Study build	When editing CQL in Edit Checks, Derivations and Aliases, a Record Position of 0 will be automatically inserted for Standard Fields and a wildcard '*' for Log Fields.
533	Feature	Study build	When editing CQL in Edit Checks, Derivations and Aliases the autocompletion for Fields will show additional information including the Field PreText, Control Type and Data Dictionary. Folder and Form autocomplete lists will show the Name as well as the OID. Search terms will be highlighted with underscores.
944	Feature	Study build	When editing CQL in Edit Checks, Derivations and Aliases the autocompletion for Fields will show additional information including the Field PreText, Control Type and Data Dictionary. Folder and Form autocomplete lists will show the Name as well as the OID. Search terms will be highlighted with underscores. (Duplicate of #533)
693	Feature	Study build	CQL has a new format for Variable only data references, the Variable OID prefixed by a colon, e.g. :AETERM Record Position can be specified after the Variable OID, e.g. :AETERM[0] :AESER[*]
823	Feature	Study build	CQL has a new format for Variable only data references, the Variable OID prefixed by a colon, e.g. :AETERM Record Position can be specified after the Variable OID, e.g. :AETERM[0] :AESER[*] (Duplicate of #693)
751	Feature	Study build	Data Format is displayed in the CQL autocompletion list for selecting Fields.
800	Bug	Study build	CQL comparing the length of a Field using the inequality operator '!=' was incorrectly being translated into a 'LengthIsNotEqualTo' checkstep in the Rave quickedit. Rave has 'LengthIsEqualTo' but not 'LengthIsNotEqualTo' check functions. This CQL will now be converted into 'LengthIsEqualTo' and 'Not' checksteps so that the logic in Rave is correct.
822	Feature	Study build	When editing CQL in Edit Checks, Derivations and Aliases the autocompletion list for Fields can be searched for a specific Form, or across all Forms. More information can be found here: Clinical Query Language
877	Bug	Study build	When editing CQL in Edit Checks, Derivations and Aliases an error message 'Syntax error too many values to unpack' was sometimes displayed when a Custom Function referenced a Datapoint. This has been corrected.
878	Feature	Study build	When editing CQL in Edit Checks it is now possible to use parenthesis immediately before and after the logical operators 'and', 'or' and 'not' without requiring spaces before or after the parenthesis: (1==1)and(2==2)
879	Feature	Study build	The CQL syntax for Custom Functions has changed and Custom Functions are now a 'method' after the data reference: *.AE.AETERM[*].CustomFunction('AlwaysTrue')
884	Bug	Study build	The Edit Check description did not include parenthesis correctly when the 'NOT' function was used. This has been corrected.
943	Feature	Study build	The syntax of data references in CQL has been changed. The Folder, Form and Field OIDs are now separated by the '.' character: FOLDER.FORM.FIELD Folder OID is optional and can be wildcarded, but Form and Field OIDs are mandatory: *.FORM.FIELD Record Positions and Folder/Form repeat numbers are specified like this: FOLDER[1].FORM[1].FIELD[*] Variable only data references are prefixed with the ':' character: :VARIABLE If not specified the reference will default to 'StandardValue'. This can be changed by appending the data value type: *.FORM.FIELD.CodedValue *:VARIABLE.UserValue More information can be found here: Clinical Query Language
953	Bug	Study build	In previous CQL if a field OID is unique, e.g. only exists on FORM1 then it can be referenced in an edit check or derivation without the form: FIELD1 == 1 If a Form FORM2 is copied into the draft and that Form also contains FIELD1 then FIELD1 is no longer unique and the CQL is invalid - this causes an error. New style CQL will prevent this because Fields always have to be qualified with the Form, so the edit check would be unambiguous before and after copying: *.FORM1.FIELD1 == 1
960	Bug	Study build	Data references should not allow a Folder OID of 'SUBJECT'.
980	Bug	Study build	Rave Architect provides for maximum 17 digits and 16 decimal places for Unit Dictionary Constant values. System provided for 10 digits and 5 decimal places. This was corrected to be the same as Rave.
966	Bug	Study build	When downloading individual objects to ALS files (e.g. from Form and Edit Check editors) the downloaded file name would start with a "b" and have quotes around it e.g. b'Draft_8_AE003'.xls. This was corrected (e.g. Draft_8_AE003.xls)
923	Feature	Study build	Checkboxes can only have a DataFormat of 1 but the Form Editor would allow other values to be entered. This was corrected so that if you enter a value other than 1 for the CheckBox field then the DataFormat is changed to 1 automatically.
920	Feature	Tickets	Users ticket list now includes the related Project in the listing and all ticket lists show related Objects.
918	Bug	UX	Clicking on 'URL Team' link when managing the URL team would show an error message. This has been fixed.
971	Feature	UX	A new Search feature is available in the top menu bar, which can be used to search across all objects in Projects and Drafts. More information is available here: Search
908	Bug	Validation	Display/formatting of release notes help page was fixed.
965	Feature	Validation	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.
924	Bug	Validation	The application version number was incorrect in the help documentation on the production site. This has been corrected.