Version : 16
Released : 2020-05-24
Changes in this Release
Issue |
Type |
Module(s) |
Description |
|---|---|---|---|
1508 |
Feature |
There are now Test Case steps to inactivate Folders, Forms and Log Records. |
|
1519 |
Feature |
When searching lists of Folders, Forms and Fields in Test Case editor helpers, the search is now case-insensitive. |
|
1520 |
Feature |
The Test Case editor helpers display lists of Folders, Forms and Fields in Ordinal order. |
|
1521 |
Feature |
There are now Test Case editor helpers for '{subject_name}' steps. |
|
1522 |
Feature |
There are now Test Case editor helpers for '{datapoint}' steps. |
|
1523 |
Feature |
There are now Test Case editor helpers for inactivate Folder, Form and Record steps. Note: The inactivate Folder step has subsequently been retired, see #3381. |
|
1526 |
Bug |
The Test Case editor will display a warning if you change the Test Case Name or steps and try to leave the page without having saved the Test Case. |
|
1528 |
Feature |
The Test Case editor helpers for '{datapoint}' steps let you select the Folder OID, Folder repeat number, Form OID, Form repeat number, Field OID and Record Position. |
|
1530 |
Feature |
The Test Case editor helper for query steps lets you select query text from Check Actions in the Draft or enter some other text which is the expected result of the Test Case. |
|
1531 |
Bug |
If the PreText for a Field used in a UAT test contains a html non-breaking space ( ) PDF generation for the UAT result would fail. This was corrected. |
|
1533 |
Feature |
The Test Case listing now has checkboxes to select test cases to be archived, run or batch deleted. |
|
1538 |
Bug |
UAT Run button ignored checkboxes and would include all filtered entries. This was changed to honor the checked selections. |
|
1529 |
Bug |
When running a set of UAT Test Cases if the background server is restarted or fails for some reason the UAT Run would become stuck in a "running" state but would never complete. The system now detects when a UAT Run was not complete and will restart the task, re-running from the last test not completed. |
|
1540 |
Feature |
Lists with Label columns can now be sorted by label. |
|
1336 |
Bug |
In the Test Case Import dialog, long Test Case names would cause the table of Test Cases to overflow the popup window. This was corrected. |
|
1534 |
Feature |
If an Edit Check has multiple check steps with no Folder specified then the Test Case Advisor will select one Folder to apply to all these steps when it suggests test data. |
|
1559 |
Bug |
The Test Case Advisor will order test data by Folder Ordinal and Form Ordinal. |
|
1560 |
Feature |
The Test Case Advisor will only use 'Other, specify' data dictionary entries if there is no alternative. |
|
1561 |
Feature |
The Test Case Advisor will suggest empty values for data dictionary fields which are compared against a value of 0. This is because Rave treats 0 as being empty when evaluating edit checks for dictionary fields. |
|
1140 |
Bug |
The PDF report generated from the Custom Function list page was incorrectly showing a list of commas in the UAT Test column. This has been removed. |
|
1563 |
Bug |
The PDF report generated from the Test Case list page was incorrectly showing the checkbox selection column. This has been removed. |
|
1577 |
Bug |
In UAT results long data tables caused PDF generation to fail, this was corrected. |
|
1607 |
Bug |
The Test Case editor helper for data values was not refreshing the list of Fields when a Form was selected. This has been corrected. |
|
1412 |
Bug |
If the Test Case Advisor is run concurrently on the same Draft or the same Edit Check there was a risk of failure because of a duplicate Test Case name. This should not now happen, though it is possible that the resulting Test Cases will have identical names. |
|
1565 |
Bug |
If the Test Case Advisor is run concurrently on the same Draft or the same Edit Check there was a risk of failure because of a duplicate Test Case name. This should not now happen, though it is possible that the resulting Test Cases will have identical names. (Duplicate of #1412) |
|
1566 |
Feature |
When the Test Case Advisor has been run it can be re-run without closing and re-opening it. |
|
1567 |
Feature |
When creating Test Cases using the Test Case Advisor with 'delete existing test cases' selected the Test Case Advisor was appending '(1)' to the Test Case name. This is not necessary since existing Test Cases are deleted. |
|
1568 |
Feature |
When creating a Test Case for an Edit Check there are now 2 buttons in the sidebar. 'Add' will create a new Test Case in addition to any existing ones. 'Replace' will create a new Test Case and delete any existing ones for that Edit Check. |
|
1572 |
Feature |
When the Test Case Advisor processes an Edit Check containing a Field which is not visible by default the Test Case Advisor will attempt to find an Edit Check with a SetDataPointVisible check action for that Field and will add data entry steps to make the Field visible. If no check action can be found or if the check action is in an inactive Edit Check or an Edit Check which also references a Custom Function then the additional data entry steps will not be added. |
|
1575 |
Feature |
Comments added by the Test Case Advisor are now displayed in the list of Edit Checks processed. |
|
1630 |
Feature |
Scenario count was removed from the Automated Testing table. It didn't provide a lot of value and we wanted to reduced the visual clutter on that table. |
|
1632 |
Feature |
If a Test Case was edited since it was last entered into a Test Set it now shows it was changed in the Test Case listing. |
|
1633 |
Feature |
If an object related to an Test Case is edited after the Test Case is put into a test set the Related Object should show a Changed marker in the Test Case List. |
|
1640 |
Feature |
Test Cases now have database fingerprints which will be used to add Standards Compliance for Test Cases. No changes are visible to users yet. |
|
1642 |
Feature |
'User Acceptance Testing' has been renamed 'Automated Testing'. |
|
1297 |
Feature |
The Test Case Advisor will now add data entry steps to make Fields visible if they are not visible by default and are referenced in the Edit Check. |
|
1315 |
Feature |
The Test Case Advisor has a link to navigate directly to the Test Cases list. |
|
1426 |
Feature |
If a Field has a Default Value the Test Case Advisor will now attempt to use that value in the suggested Test Case. If the Default Value can be used to generate test scenarios then the Field will not be included in enter data steps and a note will be added to the test scenario. If the Default Value is not used then an alternative value will be provided (if possible). |
|
1573 |
Feature |
Screenshots are now taken of the 'Form exists' step. Note that from TG_UAT draft version 19 and onwards, there will not be a screenshot of the 'Form exists' step. |
|
1574 |
Feature |
When running a Test Case TrialGrid will expand the horizontal width of the screenshot if the page in Rave is wider than the default screen size, for example to display a log record table. |
|
1578 |
Feature |
The Test Case Advisor will now add data entry steps to populate derived Fields which are used in an Edit Check, if the Derivation can be evaluated. |
|
1579 |
Feature |
If the Test Case Advisor cannot suggest any data entry values then it will create enter data steps with no values, to make it easier to manually enter values. |
|
1580 |
Feature |
The Test Case Advisor will create cross-references to any Forms referenced in the Edit Check. |
|
1581 |
Feature |
If the Test Case Advisor cannot create a valid Test Case it will insert a step to document the issues which need to be resolved manually. |
|
1584 |
Bug |
Parent Folders can now be used in Test Cases, see Automated Testing Step Reference |
|
1600 |
Feature |
The Test Case list has a new option to export the selected Test Cases to a pdf document. |
|
1610 |
Feature |
The Test Case Advisor suggested words such as 'TREATMENT' for text Fields. These words were sometimes not appropriate for the Field. Now the Test Case Advisor will use an alphabet string such that a text Field of length 5 characters will have a suggestion of 'ABCDE', up to a maximum of 10 characters. In future TrialGrid will have features to allow pre-defined lists of potential test values to be created. |
|
1615 |
Feature |
When a Form contains a derived Field with a 'NOW' Derivation which triggers Custom Functions to run then the 'enter data' test steps will not trigger the derivation (a limitation of Rave Web Services). To ensure that all expected actions have occurred a new Test Step can be used, e.g.: When I save form "AE" in folder "VISIT" |
|
1624 |
Bug |
When verifying Test Case results, TrialGrid was not taking into account datapoints which had multiple queries and so might report a false result. This has been corrected. |
|
1639 |
Feature |
The Test Case Advisor will use the enter and save data entry step. |
|
1646 |
Feature |
The Test Case list has a new option to export the selected Test Cases to an Excel spreadsheet. |
|
1643 |
Bug |
Copying and pasting a password when running a Test Case could lead to an error. This has been corrected. |
|
1647 |
Bug |
Automated Test pdf files were not being generated because of an error in the location of font files. This has been corrected. |
|
1649 |
Bug |
Automated Test Case run pdf files were not being generated if the content contained an '&' character. This has been corrected. |
|
1650 |
Bug |
The Test Case Run pdf would fail to be created if an Edit Check name contained a ':' character. This has been corrected. |
|
1651 |
Bug |
The Test Case Advisor was not always choosing an appropriate Folder when adding steps to make a Field visible. This has been corrected. |
|
1635 |
Bug |
The Test Case Advisor now only checks Folders in the Subject Calendar if the Folder is in the default Matrix or the Folder is created in the Test case. |
|
1634 |
Bug |
The Test Case Advisor will add an issue and the Test Case will require attention if more than one Form in the same child Folder is not in the default Matrix. |
|
1655 |
Bug |
The Test Case Advisor will now add a 'save form' step for any folder and form which is present in a Check Action but not in the Check Steps. This will ensure that the datapoints on that Form are submitted and the Check Action will run. Note that such Checks might deviate from recommended best practices - see Diagnostic 0058 'Check Actions should have a matching Check Step'. |
|
1656 |
Bug |
The Test Case Advisor will now add steps to create Folders and Forms which are used in a sub-check to make Fields in the main edit check visible and if these Folder/Forms do not exist in the default Matrix. |
|
1657 |
Bug |
The Test Case Advisor was generating values for 'age' derivations the wrong way around, ie. the earliest and latest dates were inverted. This has been corrected. |
|
1653 |
Bug |
The Test Case Run pdf would fail to be created if there were data entry steps containing long Folder, Form or Field OIDs. This has been corrected. |
|
1654 |
Bug |
The Test Case Run pdf would fail to be created if the Test Case referred to an Edit Check which does not exist. This has been corrected. |
|
1625 |
Bug |
The performance of importing Architect Loader Spreadsheets with Automated Test Cases was improved. |
|
1665 |
Feature |
The Test Case helper for data entry steps will not insert a Units column in the step table if no units are specified. |
|
1659 |
Feature |
Automated Test steps which check data values will now match decimal numbers if there is a difference in leading or trailing zeros, e.g. 012.20 will match 12.2. Numbers will still not be rounded so 12.19 will not match 12.2. |
|
1660 |
Feature |
When running Test Cases there is now an option 'Continue on failure'. When set on the Test Case runner will attempt to execute steps after a failed step in a scenario. When off (the default) the runner will stop running steps within a scenario when it encounters a failed step. This option can be useful to report the success or failure of all test steps without having to fix the first issue and then re-run. |
|
1661 |
Feature |
When running Test Cases there is now an option 'Check user roles'. When set on (the default) the Test Case runner will check that the Rave user accounts have the specified role in Rave. When set off the Test Case runner will report that the roles are different but will attempt to execute the tests using the given accounts. |
|
1584 |
Bug |
When a Folder which has a Parent Folder is referenced in a Test Case, the Parent Folder should be specified in the Test Case, using an absolute folder reference. |
|
1675 |
Bug |
< and > characters in query text messages would cause errors when generating the Test Case list pdf document. This has been corrected. |
|
1667 |
Feature |
The Test Case Excel list now contains the description of Edit Checks. |
|
1668 |
Feature |
The Test Case Excel list now contains the Names of related objects such as Forms. |
|
1670 |
Feature |
The Test Case pdf list now contains the description of Edit Checks. |
|
1669 |
Feature |
The Test Case pdf list now contains the Names of related objects such as Forms. |
|
1671 |
Feature |
The Test Case Results pdf now has the Edit Check Description at the start of the main content. |
|
1672 |
Feature |
The Test Case Results pdf now contains the Names of related objects such as Forms. |
|
1678 |
Feature |
Edit Check descriptions now contain the Pretext of Fields to make them easier to understand for all users. |
|
1681 |
Feature |
When a Folder which has a Parent Folder is referenced in a Test Case an editor warning symbol will be displayed if the Folder is part of a nested Folder structure. This is to help avoid surprises because Rave will create the Parent automatically. |
|
1475 |
Feature |
Test cases now have Standards Compliance comparisons against libraries. |
|
1485 |
Feature |
The Test Case list has Standards Compliance information so it can be filtered for objects which are different from the library, not found or modified. |
|
1554 |
Bug |
Test Case editor loading performance was improved. This is especially noticeable with large Test Cases. |
|
1685 |
Feature |
The Test Case Excel list now highlights Folder, Form and Field names in the Edit Check description column. |
|
1497 |
Feature |
Test Case Templates are now supported. See documentation for more details. |
|
1687 |
Feature |
When editing Test Cases, error messages will now be displayed at the bottom of the editor as well as when hovering over the error marker next to the line(s) with error(s). |
|
1689 |
Feature |
Test Case Templates now have placeholders for Folders. See documentation for more details. |
|
1693 |
Feature |
Test Case Templates now have placeholders for Check Action target datapoints. See documentation for more details. |
|
1720 |
Feature |
Automated Test Case runs were consuming more server memory than necessary. This has been improved. |
|
1720 |
Feature |
Automated Test Case runs were consuming more server memory than necessary. This has been improved. A previous attempt to correct this issue was made on 2020-02-06. |
|
1727 |
Bug |
The Test Case 'Save as new' button was not creating a new Test Case. This has been corrected. |
|
1712 |
Bug |
If multiple queries with the same query text were opened then the Test Case Run screenshot would highlight the first on the page, not the one connected to the relevant Field. Now the Field PreText will be used to make sure that the correct Field is highlighted. |
|
1725 |
Bug |
Rave pages containing log records were sometimes truncated on the right or left hand side. This has been corrected and the entire page should now be included in the screenshot. |
|
1726 |
Bug |
The Test Case Result pdf was not generated if test data included symbols such as '<'. This has been corrected. |
|
1683 |
Feature |
If access to the TrialGrid UAT draft has not been correctly configured an error message is displayed. The text of this error message has been improved. |
|
1723 |
Bug |
A javascript error could occur on loading the Test Case list page. This has been fixed. |
|
1439 |
Feature |
Incomplete date and time values can now be specified in Test Cases. See Dates and Times in Test Cases |
|
1732 |
Feature |
The 'Then I should see form' Test Case step will now include a screenshot of the form in the test results. |
|
1737 |
Feature |
Test Cases will now run if the Rave user account uses a non-English locale such as Japanese. Japanese, Chinese and Korean fonts should display correctly in result screenshots. |
|
1744 |
Feature |
Test Case Templates can now use control structures such as 'for' loops. See Test Case Templates |
|
1739 |
Feature |
Test Case Templates can now use optional Folders. See Test Case Templates |
|
1745 |
Feature |
When running the 'subject exists' step in Automated Tests TrialGrid will attempt to create a subject using the EDC Role specified in the Test Case. If this Role does not have permission to create subjects in Medidata Rave then TrialGrid will attempt to create the subject using the "Subject Admin" user, if available. |
|
1734 |
Bug |
A failure to generate the pdf for a particular Test Case run was corrected. |
|
1740 |
Feature |
When copying Test Cases from another Draft or Library there is now an option to select only those Test Cases for which the related Edit Check(s) exist in the target Draft. |
|
1750 |
Bug |
Test Case run screenshots were not capturing the complete page for non-log forms (introduced by changes from #1725). This was corrected. |
|
1751 |
Feature |
The TrialGrid Project and Draft have been added to the Test Case run pdf. |
|
1758 |
Bug |
Test Case results would not highlight query messages containing double-quotes and some other symbols. This has been corrected. |
|
1761 |
Feature |
New parameters are available to format test subject names in Test Cases. See Test Case Subjects |
|
1762 |
Bug |
Line breaks in query text messages were causing errors in Test Case runs. This has been corrected. |
|
1763 |
Bug |
Double quote characters in Form or Folder names were causing errors in Test Case runs. This has been corrected. |
|
1760 |
Feature |
The Test Set Run history now has default ordering of most recent runs first. |
|
1717 |
Feature |
Labels can now be added or removed from multiple Test Cases using the 'Apply Label' button on the Test Case list page. |
|
1765 |
Bug |
The performance of running Test Cases has been improved. |
|
1767 |
Bug |
The 'randint' subject name parameter can now be formatted. See Test Case Subjects |
|
1770 |
Feature |
Test Case subject names are now truncated on the right. |
|
1771 |
Feature |
The default Test Case subject name format is now the first 20 characters of the Test Case name followed by a timestamp. |
|
1772 |
Feature |
The default Test Case subject name format now has additional formatting options which can be configured by TrialGrid on request. |
|
1782 |
Feature |
Test Cases have new steps to check whether a datapoint is submitted, see Automated Testing Step Reference |
|
1787 |
Bug |
When running Test Cases on a Rave EDC (RaveX) URL scenarios after the first scenario would fail. This has been corrected. |
|
1786 |
Bug |
When running Test Cases on a Rave EDC (RaveX) URL the user accounts required will now include Rave EDC roles when required for Test Steps such as 'When I enter and save data'. |
|
1788 |
Feature |
If a Test Case step which requires Rave Subject Admin permission fails then a message will be displayed in the test results asking if the given user account does have Subject Admin permission. |
|
1789 |
Bug |
Test Case result screenshots were displaying out-of-date information in some cases when testing against Rave EDC (RaveX). This has been corrected and the page is refreshed before the screenshot is taken to ensure the latest information is visible. |
|
1790 |
Feature |
When checking Test Case results differences in whitespace characters (in query messages for example) will be noted in the results but will not cause the step to fail. |
|
1791 |
Bug |
Test Case Generation would fail on Edit Checks containing an 'IsEmpty' step and a step referencing a Log Field with multiple default values with a comparison against a default value on a Log Record after the first one. This has been corrected. |
|
1806 |
Bug |
Test Cases could not be copied from another URL if the Test Cases were labelled with Labels not existing in the target Draft. This has been corrected. |
|
1808 |
Bug |
Automated Test results were not being reported correctly when the expected query was different from the actual query. This has been corrected. |
|
1809 |
Feature |
When verifying expected data values the Automated Test results will report if the value in Rave has only whitespace differences from the expected value. |
|
1817 |
Bug |
The Test Case Advisor would fail for Edit Checks containing a date Field with a Default Value of a single pipe character, "|". This has been corrected. |
|
1553 |
Bug |
The performance of the Test Cases list view was improved. |
|
1822 |
Bug |
The performance of deleting Test Cases was improved. |
|
1803 |
Feature |
Test Cases can now be created by uploading a file containing test data. See Uploading Test Data |
|
1826 |
Feature |
Test Case steps have been added to allow creating a named subject at a specified Study Site. |
|
1628 |
Bug |
Data Dictionary 'other' entries are now supported in Test Cases. |
|
1833 |
Bug |
The 'Create or select the subject named {name} at site {site}' Test Case step was creating a subject with the wrong name. This has been corrected. |
|
1831 |
Bug |
The status of Test Case runs was sometimes displayed incorrectly. This has been corrected. |
|
1849 |
Bug |
The 'Create or select subject at site' Test Case step would fail if subjects with the same name were present at different study sites. This has been corrected. |
|
1849 |
Bug |
Data entry would sometimes fail after the 'Create or select subject at site' Test Case step. This has been corrected (continuation of issue fixed on 2020-05-11). |
|
1863 |
Bug |
The Test Data Upload was not processing rows for Fields with Unit Dictionaries if no unit was specified. This has been corrected. |
|
1859 |
Bug |
Uploading a test data file with multiple unit dictionaries would fail. This has been corrected. |
|
1860 |
Feature |
When uploading a test data file an upload name can be entered and this will be included in the names of the created Test Cases. |
|
1813 |
Feature |
Documentation about creating Test Cases for Derivations has been added. See Testing Derivations. |
|
1162 |
Feature |
Configuration settings for Automated Testing can now be set for each Project. See Project Test Configuration. |
|
1107 |
Bug |
Using @ symbol to mention users and groups of users in comments has been enhanced (see issues #1547, #1549, #1550, #1551) |
|
1547 |
Feature |
When a user or project role is mentioned in a comment with the @ syntax, that user (or set of users) receives an email notification. |
|
1549 |
Bug |
When referencing usernames in comments with the @ syntax the system did not recognize usernames with the @ or . characters in the name. This has been corrected. |
|
1550 |
Feature |
When referencing users and groups in comments, the referenced user or group is now highlighted in the comment text. |
|
1551 |
Feature |
When a user or group name has a space in it e.g. ("Study Builder") it should appear in the comment helper and with an underscore replacing spaces ("Study_Builder"). |
|
1490 |
Feature |
Custom Properties can now be defined for Project and Draft objects. |
|
1525 |
Feature |
Custom Draft Properties are exported into ALS files and imported from ALS files via the TG_DraftProperties tab. Rave Architect will ignore this tab in the spreadsheet. |
|
1596 |
Feature |
In the list of custom properties, blank values are not be counted toward the "in use" total. |
|
1597 |
Feature |
When editing a Custom Property definition the system now warns if you make a change and try to leave the page without saving. |
|
1604 |
Feature |
Custom Properties now have a display order attribute which controls the order in which they are displayed in editors and listings. |
|
1608 |
Bug |
When changing a custom property from a text field to a choice field and there are empty values in the choices list, the system will throw an error. This was corrected. |
|
1753 |
Bug |
Custom properties on forms could not be saved without error when Form is matched to a Standard Library (compare fails). This was corrected. |
|
1821 |
Feature |
Custom Properties on objects are now copied as part of the create Draft from Library process. |
|
1858 |
Bug |
The Form list showed custom property values even when "show in lists" was not set for a custom property. This was corrected. |
|
1552 |
Bug |
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 |
Clicking the headings of panels in Diagnostics Findings page now expands/collapses those sections. |
|
1599 |
Bug |
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. |
|
1676 |
Bug |
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. |
|
1691 |
Feature |
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. |
|
1695 |
Feature |
Diagnostic 00121 was added. This checks that Fields on ePRO forms use only supported control types (Text, LongText, DropDownList, Checkbox etc) |
|
1699 |
Feature |
Diagnostic 0122 was added. This checks the DataFormat of Date Fields on ePRO Form are using a DataFormat supported by Patient Cloud. |
|
1704 |
Feature |
Diagnostic 0082 now checks that Fields with a Coding Dictionary do not have a Unit Dictionary or a Lab Analyte. |
|
1062 |
Feature |
Diagnostic 0124 Checkbox Fields should not have Default Values has been added. |
|
1722 |
Feature |
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. |
|
1384 |
Feature |
Diagnostic 0125 was added. This checks that Open Query Check Actions which are set to Requires Response are also set to Requires Manual Close. |
|
1773 |
Feature |
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. |
|
1785 |
Bug |
Settings for Diagnostic 0027 were being shown under the settings for Diagnostic 0023. This was corrected. |
|
1799 |
Bug |
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. |
|
1836 |
Bug |
Diagnostic 0061 Valid HTML Tags would fail if a string contained the invalid tag '</br>'. This has been corrected. |
|
1838 |
Bug |
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. |
|
1462 |
Feature |
On the Draft Home Page there is now an option to generate documents in Microsoft Word format. |
|
1463 |
Feature |
When generating a document you can select the document type you want from the list of those available and adjust settings. |
|
1464 |
Feature |
A count of documents generated appears on the users home page. |
|
1465 |
Feature |
A listing to manage documents generated (e.g. to download or delete documents) is available from the user home page. |
|
1466 |
Feature |
A count of document templates defined for a URL now appears on the URL home page. |
|
1467 |
Feature |
A new URL-level permission was added for the management of Document Templates in the URL. |
|
1468 |
Feature |
Users who do not have the Manage Document Template URL-level permission cannot import Document Templates from other URLs. |
|
1469 |
Feature |
The Document Import dialog allows a user to select Document Templates from other URLs but only lists URLs where Document Templates have been defined. |
|
1477 |
Feature |
On import of an Document Template that has the same name as an existing one, the newly imported Template gets a _n suffix (e.g. Document_1) |
|
1478 |
Feature |
URLs now have a page that lists all the available Document Templates. |
|
1479 |
Feature |
Users with Manage Document Template permission can delete Document Templates from the system. |
|
1480 |
Feature |
Users are able to view the source and settings of Document templates in their URLs. |
|
1562 |
Feature |
The Draft "Documents" button does not show if there are no Document Templates defined for the URL. |
|
1644 |
Feature |
A new step has been added to TrialGrid's internal application testing which will look for Javascript code which might be incompatible with older browsers, such as Internet Explorer 10. |
|
1648 |
Feature |
Some Javascript packages have been updated to the latest versions. No changes are visible to users. |
|
1686 |
Feature |
A new performance monitoring tool has been added to TrialGrid to help identify any potential performance issues. |
|
1720 |
Feature |
Automated Test Case runs were consuming more server memory than necessary. This has been improved. |
|
1708 |
Feature |
The system now has a task that periodically sweeps the database of expired user sessions. Users will notice no difference to functionality, this is a system housekeeping change. |
|
1721 |
Feature |
Python language packages used by TrialGrid were updated to the latest versions. No changes are visible to users. |
|
1502 |
Feature |
New contols have been added to TrialGrid to improve the security of web pages. No changes are visible to users. |
|
1720 |
Feature |
Automated Test Case runs were consuming more server memory than necessary. This has been improved. A previous attempt to correct this issue was made on 2020-02-06. |
|
1731 |
Feature |
New settings have been added to the TrialGrid web server to help manage web server memory. No changes are visible to users. |
|
1735 |
Feature |
A configuration setting was added to the background queue process to help manage memory usage. No change is visible to users. |
|
1764 |
Bug |
Creating PDFs for Test Case runs with large numbers of screenshots used a lot of memory. This was corrected. Users are unaffected by this system change. |
|
1807 |
Feature |
Changes were made to support Disaster Recovery. No changes are visible to users. |
|
1837 |
Feature |
A system command was added to generate an Excel listing of Active Diagnostics for a project and their settings. Users see no change but this is a precursor to adding an Excel report Export of Diagnostic settings. |
|
1874 |
Bug |
Long running background tasks, such as Test Case runs, were being duplicated leading to errors. This has been corrected. |
|
1515 |
Feature |
Labels applied to Projects are visible on the Project home page and in the URL Project listing. |
|
1524 |
Feature |
Labels applied to Drafts are visible on the Draft home page and the Project Draft listing. |
|
1598 |
Feature |
When editing a Label definition the system now warns if you make a change and try to leave the page without saving. |
|
1752 |
Bug |
The visual appearance of Labels in editor side bars was inconsistent with Labels elsewhere and has been corrected. |
|
1625 |
Bug |
The performance of importing Architect Loader Spreadsheets with Automated Test Cases was improved. |
|
1554 |
Bug |
Test Case editor loading performance was improved. This is especially noticeable with large Test Cases. |
|
1556 |
Bug |
Form list performance when displaying Standards Compliance information was improved. |
|
1557 |
Bug |
The Data Dictionaries list was inefficient when showing standards information. Performance was improved. |
|
1720 |
Feature |
Automated Test Case runs were consuming more server memory than necessary. This has been improved. |
|
1720 |
Feature |
Automated Test Case runs were consuming more server memory than necessary. This has been improved. A previous attempt to correct this issue was made on 2020-02-06. |
|
1735 |
Feature |
A configuration setting was added to the background queue process to help manage memory usage. No change is visible to users. |
|
1765 |
Bug |
The performance of running Test Cases has been improved. |
|
1553 |
Bug |
The performance of the Test Cases list view was improved. |
|
1820 |
Bug |
The performance of the Field list view was improved. |
|
1822 |
Bug |
The performance of deleting Test Cases was improved. |
|
1545 |
Bug |
It is no longer possible to assign tickets to users who are invited but not yet active in the system. |
|
1546 |
Bug |
It is no longer possible to reference users who are invited but not yet active in the system in comments. |
|
1569 |
Bug |
In the URL Team list, users with Manager permission would only see users related to Projects which they themselves had access to. Users with Manager URL permission now see all useres in all Projects in the URL. |
|
1603 |
Bug |
If a user attempts to delete a Project from the Project List when they do not have permission to do so, no deletion happens but no error message is shown. This was corrected. |
|
1590 |
Bug |
If the owner of a Project was assigned a Project Role and then that role was removed from the owner, the Owner lost the permission to view the Project. This was corrected. This issue did not affect all pages under the draft (mostly just ones related to Diagnostics) this was due to differences in the ways these pages checked permissions. This was also fixed. |
|
1591 |
Feature |
If a user can view a project in a URL they can also view the URL level information. For security only users with Manage Team permission may now view the URL Level Team page since this shows all users and their permissions. |
|
1592 |
Feature |
Users who do not have Manage Team permission no longer see the URL Team Members card on the URL home page. |
|
1609 |
Feature |
When I have "manager" permission at the URL level I can see all projects in that URL. |
|
1611 |
Feature |
Users who have view access to a Project are now able to view the settings for a project. |
|
1613 |
Feature |
A project cannot be set to be owned by a user who has not yet activated their TrialGrid account. |
|
1614 |
Bug |
Project owners were unable to invite new users to the Project or remove users from a Project. This was corrected. |
|
1616 |
Feature |
When a user is not able to view the URL Team then they no longer see the breadcrumb link to the team page. |
|
1694 |
Feature |
TrialGrid Super users can now always manage teams in a URL (previously they had to have a role in the URL) |
|
1638 |
Feature |
Rave versions 2019.1.2, 2019.1.3 and 2019.2.0 were added to available Rave versions. |
|
559 |
Feature |
When exporting an ALS file, custom TG_ tabs are placed at the end of the ALS file generated i.e. the last tabs in the spreadsheet. |
|
1594 |
Feature |
Retired |
Custom Properties now have associated data types (text, boolean or a choice of values) |
1502 |
Feature |
New contols have been added to TrialGrid to improve the security of web pages. No changes are visible to users. |
|
1784 |
Feature |
If TrialGrid encounters a Cross Site Request Forgery (CSRF) error it will display a warning and prompt the user to log in again. |
|
1827 |
Bug |
A security issue has been addressed. |
|
1842 |
Feature |
On login the system will not redirect the browser to a web page that is not part of the application. (e.g. /login?next=https://www.google.com) |
|
1690 |
Feature |
Drafts in a Standard Library now have the count of related Rules in the Draft Summary section (e.g. similar to count of Forms and Edit Checks) |
|
1692 |
Feature |
Breadcrumbs for a Standards Library Draft now include a link to Rules. |
|
1696 |
Feature |
Drafts within Standard Libraries now have a listing of Standard Rules. |
|
1719 |
Feature |
Standard Rules may be created from the Standard Rules listing for a Draft in a Standard Library. |
|
1724 |
Feature |
Standard Rules may now be deleted from the list of Standard Rules. |
|
1733 |
Feature |
The home page of Drafts that are linked to a Library now show a count of active Standard Rules These are Rules which are selected from the Standard Library Rules list because the Drafts Project Custom Properties activate those Rules. |
|
1766 |
Feature |
It is now possible to filter the Rules list similar to a spreadsheet autofilter function. |
|
1759 |
Feature |
Rules are now imported/exported to and from Architect Loader Spreadsheets. Rave Architect will ignore these tabs of the spreadsheet. Note that Rules are only imported/exported for Standard Library Drafts (Drafts which are imported into or exported from Projects which are marked as libraries) |
|
1768 |
Feature |
Forms in Libraries now show a list of Rules related to that Form under the Standards Control tab. |
|
1769 |
Feature |
Fields now have a summary of related Standard Rules when they appear in a Standard Library. This is in addition to the list of Standard Rules for a Form. |
|
1778 |
Feature |
It is now possible to create a Draft from a standard library with Standard Library Rules applied. |
|
1810 |
Feature |
Library drafts with no Rules are not listed in the creating a Draft from Library Dialog (because with no Rules to evaluate no import would occur) |
|
1214 |
Feature |
Standards compliance summary and PDF now show which standard library was effective at the time of comparison. |
|
1543 |
Bug |
When a Draft has a Standard Library and you save a Form with no changes a record was added to show that the Form standard library was changed. This was corrected. |
|
1640 |
Feature |
Test Cases now have database fingerprints which will be used to add Standards Compliance for Test Cases. No changes are visible to users yet. |
|
1475 |
Feature |
Test cases now have Standards Compliance comparisons against libraries. |
|
1677 |
Feature |
Compliance status of objects is now recorded with the object to enable data reporting and for performance reasons. This means that the change of an object causes compliance calculation for that object to be immediately performed. When a Draft is switched to a new or different standard library a mass calculation for objects in that Draft must be performed. |
|
1485 |
Feature |
The Test Case list has Standards Compliance information so it can be filtered for objects which are different from the library, not found or modified. |
|
1666 |
Feature |
For Standards Compliance it is now possible to explicitly set an OID/Name to match on in the associated Library. For example, you can set a Form with OID "VITALS1" in a Draft to match against a Form with OID "VITALS" in a Library. |
|
1684 |
Feature |
For Standards Compliance it is now possible to set the library to match against in the sidebar of the object Editor. This allows users to control on an object-by-object basis which library it should be compared against (e.g. a Therapeutic Area library vs a Core Library) |
|
1588 |
Feature |
The Edit Check editor now shows Standards Compliance information in the sidebar. |
|
1587 |
Feature |
The Derivation editor now shows Standards Compliance information in the sidebar. |
|
1586 |
Feature |
The Custom Function editor now shows Standards Compliance information in the sidebar. |
|
1682 |
Feature |
When compliance is being recalculated for a Draft it is not be possible to change the Draft Standards Parent. This block is removed when compliance has been recalculated for the Draft. This block is removed after 5 minutes so that if the compliance recalculation fails it can be changed again. |
|
1709 |
Bug |
The Allowed Changes list in the Form Editor was not being displayed correctly. This has been corrected. |
|
1711 |
Bug |
When copying a Data Dictionary or Unit Dictionary from a Standard Library the Compliance state of the Data Dictionary or Unit Dictionary would stay "Not Found" until a change was made to force recalculation of compliance. This was fixed. |
|
1728 |
Bug |
Under some conditions the PDF Compliance Report could not be created. This was corrected. |
|
1749 |
Bug |
If a Form is compared against a different library than the Draft default then the Form listing will not display (introduced by changes from #1728). This was corrected. |
|
1774 |
Bug |
Copying Edit Checks with Custom Function actions where the Custom Function called other Custom Functions using 'PerformCustomFunction' caused an error. This has been corrected. |
|
1756 |
Bug |
When saving a Project, Activity Records were created for all Project Custom Properties even if they were not changed. This was corrected. |
|
1729 |
Feature |
When using Standards Compliance compare it was possible to set the compare to be against an object in the library with a different OID or Name. However, standards compare would still show that the OID or Name was different. This was corrected. |
|
1780 |
Feature |
When comparing two objects such as Forms the comparison view will now include text to indicate if the only change is in the ordinal of child objects such as Fields. |
|
1795 |
Bug |
The "Entries can be removed" and "Entries can be added" checkboxes on Data Dictionaries in Standard Libraries were not being displayed if checked. This has been corrected. |
|
1830 |
Bug |
Changing the draft standard library did not change the library associated with draft objects, this was corrected. |
|
1510 |
Feature |
Project attributes Protocol and Description are no longer required fields. |
|
1029 |
Bug |
When moving a Field to a different position in the Form Editor the Field list will auto-scroll at the top or bottom of the display. The auto-scroll has been improved and should work more reliably, though it might still be necessary to move the mouse to continue auto-scrolling on long forms. |
|
1294 |
Feature |
When editing Form and Field Restrictions, all EDC Roles defined in the URL Configuration are displayed, which makes it easier to see which are selected and which are not selected. |
|
1509 |
Feature |
The Field Properties sheet in the Form Editor can be hidden and shown. |
|
1511 |
Feature |
The Field Properties in the Form Fields area can be hidden and shown. |
|
1512 |
Feature |
Form Fields can be displayed with styles matching Rave Classic or Rave EDC (RaveX). |
|
1513 |
Feature |
A Field with of no particular type can be added in the Form Editor. |
|
1514 |
Feature |
New Fields can be added at the top or bottom of the Form, or before or after the selected Field. |
|
1516 |
Feature |
Form Fields can be displayed with a selected EDC Role. Fields which are View Restricted for that Role and/or are Inactive will be greyed out. Fields which are Entry Restricted for that Role will have the data entry control disabled. |
|
1517 |
Feature |
The Form Editor has a Print button to print the Form Fields. |
|
1542 |
Bug |
When you update a Field on a Form an activity record is added to show that the Form was also changed and that last-updated date is changed for the Form. |
|
2628 |
Feature |
Form preview shows changes to pre-text properties live on change. |
|
2629 |
Feature |
IsLog and Inactive fields are indicated in the Form Field list. |
|
2630 |
Feature |
Changes to Field Properties are saved when the Form is saved. |
|
1641 |
Feature |
Source code has been removed for Edit Check and Derivation 'unit tests'. These have been replaced by Automated Testing. |
|
1589 |
Feature |
When exporting a Draft to Rave the list of Drafts already existing in Rave will be displayed if the Project Name in TrialGrid is the same as the Project Name in Rave. |
|
1582 |
Bug |
Changes to ConstantA-K values in the Unit Dictionary editor were not being saved. This was corrected. |
|
1625 |
Bug |
The performance of importing Architect Loader Spreadsheets with Automated Test Cases was improved. |
|
1637 |
Feature |
The Custom Function editor will now display errors in the Custom Function source code automatically, after a short delay, and will indicate the line(s) on which error(s) are present if possible. |
|
1678 |
Feature |
Edit Check descriptions now contain the Pretext of Fields to make them easier to understand for all users. |
|
1679 |
Feature |
The description of AddForm Check Actions now uses the Form Name rather than the Form OID. |
|
1556 |
Bug |
Form list performance when displaying Standards Compliance information was improved. |
|
1557 |
Bug |
The Data Dictionaries list was inefficient when showing standards information. Performance was improved. |
|
1710 |
Bug |
The Active and Signature Required properties in the Form Editor were not being saved after a change. This has been corrected. |
|
1713 |
Bug |
Long text strings were not not completely visible in the standards comparison view. This has been corrected. |
|
1736 |
Bug |
The Form Editor now supports Coding Dictionary setup including Priority, Coding Level, Locale, Supplemental Terms, Component Terms and other workflow elements. Note that the system does not have information about which Coding Dictionaries are set up for the URL. See Field Coding Configuration for more information. Note that currently coding information related to Fields is not included in Standards Compliance calculations. |
|
1747 |
Bug |
The cloning function for Fields on a Form was broken by recent changes to the Form editor to support Coding information. This was corrected. |
|
1748 |
Feature |
When a Field with coding information is copied into another study, the coding information is now also copied with it. |
|
1341 |
Bug |
Edit Checks with a Variable only check step and a Folder Repeat Number but no Folder specified were not being accepted as valid. This has been corrected. |
|
1776 |
Bug |
Duplicate Custom Functions could be created when copying Edit Checks. This has been corrected. |
|
1777 |
Feature |
Boolean (TRUE/FALSE) columns in Architect Loader Spreadsheets are now imported in a case-insensitive way (TRUE = true = TrUE). Previously TRUE/FALSE values as exported by Rave Architect were expected. |
|
1781 |
Feature |
Labels can now be added/removed from objects selected in the Draft Comparison view. |
|
1779 |
Bug |
Edit Checks with a Variable only check step and a Form Repeat Number but no Form specified were not being accepted as valid. This has been corrected. |
|
1794 |
Bug |
When adding new Fields to a Form, updating view and entry restrictions would affect all newly added Fields. This was corrected. |
|
1801 |
Bug |
The Edit/Delete buttons were not visible on the Custom Function list at smaller screen sizes. This has been corrected. |
|
1804 |
Bug |
After selecting a Draft from which to copy Forms another Draft could be immediately selected leading to duplicate Forms displayed in the list. This has been corrected. |
|
1805 |
Bug |
When displayed the list of Forms to copy the buttons to copy Forms were sometimes not visible. This has been corrected. |
|
1811 |
Bug |
When creating a new Form in a library the user would see Javascript errors. This was corrected. |
|
1820 |
Bug |
The performance of the Field list view was improved. |
|
1792 |
Feature |
When Forms are imported from a Draft Library via Standard Library Rules, Form Ordinals are renumbered to be in the original order but with consecutive values. |
|
1793 |
Feature |
When Folders are imported from a Draft Library via Standard Library Rules, Folder Ordinals are renumbered to be in the original order but with consecutive values. |
|
1852 |
Bug |
When editing field Pretext, entering HTML tags <br></br> was changed into <br/></br> which is incorrect and not accepted by Rave. This was corrected. |
|
1861 |
Bug |
A javascript error on the checks list page was corrected. |
|
1862 |
Bug |
The Test Case Advisor would sometimes log internal error messages when processing an edit check using an AddHour check step. |
|
1541 |
Feature |
The Ticket list now has a comment count column. |
|
1631 |
Feature |
When there are no tickets associated with Test Cases the Related Tickets column is hidden in the Test Cases list. |
|
1673 |
Feature |
It is now possible to select a TestCase from the Ticket editor to be related to the Ticket. This is the same mechanism as is used for Forms, Custom Functions etc. Test Cases may still have links to Tickets via the @ticket:ticket_number text in the Test Case script. The @ticket reference method was retired in September 2021. |
|
1544 |
Feature |
In the Form Editor the Standard Compliance Draft selector for the Current Draft Default is now indicated by (Draft Default). This makes it clear when a Form is being compared to a Standard Library Draft different from the default for the Draft (e.g. if you imported a Form from a different Library) |
|
1570 |
Feature |
In the URL level Team list there was no indication that a user was the owner of a particular Project and if they had no other assigned role in the Project then that Project was not listed at all. This was corrected by adding an "Owner" indicator and by including Projects in the listing where the user only had an Ownership connection with the Project. |
|
1593 |
Feature |
The slider controls used in the URL Team Members page were changed to checkboxes. |
|
1612 |
Feature |
A project does not have to have an Owner. It can be "Not Set". |
|
1658 |
Feature |
Styling of tables in Project Wiki pages was improved. |
|
1663 |
Feature |
Library Projects now have an icon in the breadcrumbs indicating that they are a library. |
|
1688 |
Feature |
If a user already has an account and they are invited to a new Project they receive an email but there was no link to login which can be confusing. A link to the login page was added to the notification message. |
|
1775 |
Feature |
Activity records are now created for additions or changes to EDC Roles in the Core Configuration. |
|
1829 |
Feature |
Rave versions 2020.1.0 and 2020.1.1 were added to the list of Rave versions. |
|
1845 |
Feature |
Disaster recovery information in the validation plan now references the Quality Management System instead of repeating this information. This change only affects the validation plan which is reviewed by auditors. |