Module : Rave Compatibility

Issue	Type	TrialGrid Version	Description
5683	Feature	93	Import Scripts can now create Matrices with the CreateDraftObject command, and set which Folders and Forms a Matrix holds with the new SetMatrixFolderForm command. A Matrix Name must now be unique within the Draft, as Rave requires, so a Matrix that shares its Name with another must be renamed before it can be saved. Saving the Matrices grid when a Folder or Form it names is no longer in the Draft now says which one, instead of failing.
5499	Feature	92	A new Organization report, Custom Function V2 Conversion, lists each draft that has V1, V2 or Mixed custom functions with its conversion status and counts. It is refreshed monthly and can be filtered by status and exported.
5542	Feature	92	Converting Custom Functions to the V2 API is licensed per Organization by the number of unique Custom Functions converted. Organizations without a conversion license do not see the V2 Conversion tab or the Convert to V2 API action, and the Licenses page shows how many conversions are licensed, consumed and remaining.
5488	Feature	92	The Custom Function Agent writes Custom Functions with the V2 Rave API as well as V1, and says which it used. Which one it writes is set by a Rave URL's new Default Rave custom function API version setting, which starts as V2; the agent does not convert a Custom Function from one to the other. Custom Function reviews are given the knowledge of the API a function uses, and report a function that mixes V1 and V2.
5500	Feature	92	Autocomplete in the Custom Function editor now offers V2 Rave API names as well as V1, chosen by the API the function's code uses. A function using both, or neither yet, is offered both, with the V1 names marked. The V1 names have been updated from Medidata's current Custom Function whitelist.
5489	Feature	92	Custom Functions are classified by whether converting them to the V2 API can be done automatically, shown on the list and in a new V2 Conversion tab that lists the changes each needs and the functions it calls and is called by.
5493	Feature	92	Custom Functions can be converted from the V1 to the V2 API, from a new Action on the Custom Functions list or a button on the V2 Conversion tab. Functions that call each other are converted together, and each conversion is saved only when Designer compiles it with no V1 references left and it keeps the same strings, calls and actions; a function that can't be converted is left unchanged and flagged with the reason.
5507	Bug	92	Custom Function summaries, the Custom Functions list and the unused objects diagnostic now recognise V2 API calls and actions, and no longer mistake text inside strings for comments.
5485	Feature	92	The Custom Functions list shows which Rave API (V1, V2, Mixed or None) each C# custom function uses, and can be filtered by it. When comparing drafts while ignoring comments and whitespace, C# custom functions are now matched on their code: spacing and comments are always ignored, and differences inside strings are always reported.
5486	Feature	92	Custom Function validation now uses Medidata Designer, shows Rave's warnings, such as API Compatibility, alongside errors, and shows a Custom Function's last validation results as soon as it is opened. The Custom Function editor also shows which Rave API the function uses.
5492	System	92	TrialGrid now keeps its knowledge of the Rave custom function API up to date from Medidata Designer's validation results.
5205	Bug	89.4	Test Case Runs against Rave EDC 2026.2.1 are supported, including changes to query text markup display.
5128	Bug	89.3	A Test Case run whose browser crashes or stops responding is now recovered as soon as the problem occurs, on both Veeva and Rave. Previously some browser operations, such as taking a screenshot of a form or opening a page after data entry, hid the failure, so the run carried on issuing commands to a browser that was no longer there. Each of those commands waited for the full timeout before failing, and runs could continue in this state for several hours before finishing or being cancelled. The browser is now relaunched and the run resumed at the point it was interrupted.
4553	Feature	85	Rave 2026.1.0 introduced locale specific downloads in Architect. The system downloads the default selection, it currently does not offer the user an option to select a locale.
3660	Feature	63	Medidata Rave Architect Loader Spreadsheets containing Edit Check, Data and Unit Dictionary OIDs can be uploaded into TrialGrid and will be displayed when editing/viewing the object.
3661	Feature	63	A warning will be displayed if the current name of an Edit Check, Data or Unit Dictionary generates an OID which is different from that imported from Medidata Rave.
3672	Bug	62.2	ActionOptions for SetDatapointVisible action changed in Rave 2024.1.0. This change broke editing of SetDataPointVisible edit checks and Diagnostic 157. This has been corrected while maintaining backward compatibility with prior Medidata Rave versions. The Test Case Advisor has been updated to work with the new (and old) ActionOptions.
2972	Bug	43	When loading core configuration files the core configuration would load but an warning "Error was File is not a zip file" was sometimes shown. This was corrected.
2168	Bug	22	Core Configuration files containing Unicode NULL (�) values cause the Core Config import to fail. This was corrected.
1970	Bug	19	Add Deviation check actions were imported to TrialGrid with Deviation Code and Deviation Class switched. This was corrected.
1903	Bug	17	TrialGrid unit tests were upgraded for compatibility with Rave 2020.2.0. No changes are visible to users.
1638	Feature	16	Rave versions 2019.1.2, 2019.1.3 and 2019.2.0 were added to available Rave versions.
1351	Bug	14	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.
1004	Feature	11	Medidata will release Classic Rave 2018.2.0 on 16th Nov 2018. This new version was added to the list of possible versions for Projects.
1005	Bug	11	Little used month formats mm and mm- did not display correctly in the Form Editor. This has been corrected.
788	Feature	7	ALS files exported from the system did not have Rave Database version information or the default Array Delimiter set. This had no effect on functionality but caused Rave to display warnings. Rave Database version (5.6) and Default Array Delimiter (,) information is now added to the ALS files exported.
785	Bug	7	When trying to upload an ALS with the latest BalancePSALUpdate Checkaction, import would fail. This has been corrected.
365	Feature	2	Rave 2017.2 introduced a new Check Action 'Balance PSAL Update'. This has been added to the list of Check Actions in TrialGrid.
464	Bug	2	HTML Handling in Field PreText is not compliant with Rave. In particular Rave expects <br> tags to be closed (<br/>) and ul (unordered list) and ol (ordered list) tags are supported.
437	Feature	2	Rave 2017.2.0 will be released on Oct 20, 2017. Added Rave 2017.2.0 to possible version selections for URLs.