Version : 17
Released : 2020-06-24
Changes in this Release
Issue |
Type |
Module(s) |
Description |
|---|---|---|---|
1883 |
Bug |
Test Case runs were not converting the Unit String into Coded Units for Unit Dictionary Fields. This has been corrected. |
|
1893 |
Bug |
Test Case runs would fail if the Site Number or Subject Name contained a 'smart quote' character. This has been corrected. |
|
1871 |
Bug |
Test Case results were reported incorrectly when checking if queries had been closed if there were other open queries on the same datapoint. This has been corrected. |
|
1886 |
Feature |
A small improvement to the performance of running multiple test cases was made. |
|
1896 |
Bug |
When running Test Cases for Rave EDC (RaveX) timeouts and other settings have been configured to reduce the number of errors when accessing Rave EDC. |
|
1875 |
Bug |
The Test Set Run view would time-out if it contained a large number of Test Cases to run, this was corrected. In addition, the performance of the display was improved. |
|
1873 |
Bug |
When there were a large number of Test Case Runs in a a Test Set run, it was not possible to refresh the page and see the current status of the run. This was corrected. |
|
1416 |
Feature |
The Test Case PDF list now has selection options to control what content is included in the PDF output. |
|
1914 |
Feature |
Test Case runs do not now automatically create a PDF document of the test run results. A PDF of one or more Test Case runs can be generated using the Test Case PDF option on the Test Case List page. |
|
1916 |
Feature |
The Test Case editor will now display an error if a table is inserted after a step which should not have a table. |
|
1904 |
Bug |
When importing a Draft from the filesystem, import messages were not displayed until the import was completed. This was corrected. |
|
1921 |
Bug |
Errors were occurring when viewing test case runs. This has been corrected. |
|
1923 |
Bug |
If an invalid test case is queued to be run the resulting test case run page cannot be viewed because of a system error. This was corrected. It should not be possible to queue invalid test cases to be run. |
|
1922 |
Bug |
Test Case generation would fail if an Edit Check referenced a Field with a numeric format and a numeric Default Value. This has been corrected. |
|
1925 |
Bug |
Test Cases running against Rave EDC (RaveX) would sometimes fail because the test session was logged out to the iMedidata login page. Automated tests will now attempt to login again if this happens and should recover from this situation. |
|
1909 |
Bug |
Spelling Diagnostic 0020 was failing to run after a version upgrade. This has been corrected. |
|
1895 |
Bug |
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. |
|
1910 |
System |
The 'tokenizer' for extracting words from text for Diagnostic 00020 Spell Checking has been changed. |
|
1907 |
Bug |
Diagnostic 0116 did not recognize dd- MMM- yyyy as a valid date. This was corrected. |
|
1911 |
Feature |
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. |
|
1899 |
Bug |
Document generation would sometimes fail because the background generation task was not always in sync with the request to generate the document. This was corrected. |
|
1880 |
Feature |
A new system monitoring endpoint has been added to check that the background queue is not too long. |
|
1881 |
Feature |
When deploying a new version of the application the deployment process will automatically turn off maintenance mode if the application has been placed into maintenance mode. |
|
1882 |
Feature |
The application name, version number and date/time have been added to the installation log and post installation test log which are available in the Validation documentation for that release. |
|
1887 |
Feature |
Test Cases now run in a separate queue from other background tasks. |
|
1903 |
Bug |
TrialGrid unit tests were upgraded for compatibility with Rave 2020.2.0. No changes are visible to users. |
|
1885 |
Feature |
System IQ/OQ checks now include a check that the email server can be accessed. This is a validation activity and does not affect end-users. |
|
1906 |
Feature |
Third-party software packages used by TrialGrid were updated to latest versions. No changes are visible to users. |
|
1910 |
System |
The 'tokenizer' for extracting words from text for Diagnostic 00020 Spell Checking has been changed. |
|
1920 |
Feature |
Emailing support@trialgrid.com will now automatically create an issue in TrialGrid's issue tracking system. An automated reply with the issue tracking number will be received. |
|
1905 |
Feature |
The user messaging subsystem was rewritten to reduce usage of the database. This is a system architecture change that should not affect users. |
|
1924 |
System |
System libraries were updated. Users should not see any functional changes. |
|
1941 |
Feature |
When viewing Tasks and Alerts a maximum of 1000 rows will be displayed. Tasks older than 365 days will be deleted. Alerts older than 30 days will be deleted. |
|
1886 |
Feature |
A small improvement to the performance of running multiple test cases was made. |
|
1903 |
Bug |
TrialGrid unit tests were upgraded for compatibility with Rave 2020.2.0. No changes are visible to users. |
|
1864 |
Feature |
When creating or editing a Value Standard Rule for a Form, the Attribute Name to be affected is now presented as a select list making it easier to create Rules. |
|
1865 |
Feature |
When creating or editing a Value Standard Rule for a Field, the Attribute Name to be affected is now presented as a select list making it easier to create Rules. |
|
1866 |
Feature |
Standard Value rules for View and Entry restrictions are now copied as part of the Create Standard Draft functionality. This makes it possible to set up a Standard Rule such as When the Project is a Phase III Study, the View Restrictions for Form with OID ADJUDICATE must be "Investigator, Coordinator". When a Draft is created from this library using the Create-Draft-From-Library wizard, these view restrictions will be set on the Form when the Project is set as a Phase III study, overriding the normal values from the Standard Library Form. |
|
1867 |
Feature |
Standard Value Rules are now taken into account in comparisons against standard objects. For example if a Standard Form has a help text of "Library Help Text" and a form using that library has help text of "Draft Help Text" then this would notmally be flagged as a difference. However, if there is an active Standard Rule for the library that says that the Help text of this Form should be "Draft Help Text" then this value from the Rule overrides the value from the library. |
|
1870 |
Feature |
Standard Must Exist / Must Not Exist rules are now taken into account when comparing an object against a standard library object. For example, a Form may exist in a Draft and in the Library and be a precise match but if there is a Standard Rule which states that the Form should not exist for this type of Project then the standard compare will show a difference and warn that the Form should not exist. |
|
1891 |
Bug |
After creating a Draft from a Library with Standard Rules, objects did not show as compliant if a custom property is empty in the Library but has a value, assigned by a rule, in the Draft. This was corrected. |
|
1824 |
Feature |
When a Library Test Case is deleted, all objects that rely on it as their standard object for comparisons change to "Not Found". |
|
1872 |
Feature |
The option to 'overwrite' the latest CRF Version when pushing a draft to Rave Architect has been removed because it was not working reliably. |
|
1939 |
Bug |
When pushing a draft to Rave Architect additional error handling code has been added. |
|
1877 |
Feature |
Boolean properties in Comparisons are now shown as True/False rather than Yes/No. |
|
1915 |
Bug |
Alert messages were not properly dismissed once viewed. This has been corrected. |
|
1828 |
Bug |
In validation documents some testing scenarios were not properly presented. This was corrected. |