Version : 6
Released : 2018-05-01
Changes in this Release
Issue |
Type |
Module(s) |
Description |
|---|---|---|---|
655 |
Feature |
In a wiki page users can now @mention other users. Entering an @ pops up a list of users who have a role in the Project and @mentioned names are highlighted in the resulting wiki rendered text. |
|
673 |
Feature |
Users with Commenting permission are now able to comment on Draft Objects (Forms, Edit Checks, Derivations, Unit Dictionaries, Custom Functions, Folders, Data Dictionaries). Similar to comments on Tickets (see issue 670 above) users who are @mentioned receive alerts and email notifications. |
|
694 |
Feature |
A count of open (non-deleted) comments associated with each Draft Object type (Forms, Data Dictionaries, Unit Dictionaries etc)now appears in the Form list. |
|
726 |
Feature |
When a user @mentions a role name (e.g. @admin or @superuser) then all users with that Role in the project are alerted and sent emails notifying them of the mention. |
|
656 |
Feature |
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 |
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 |
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 |
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 |
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. |
|
676 |
Bug |
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 |
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 |
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 |
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. |
|
684 |
Bug |
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. |
|
696 |
Bug |
When on manage Diagnostics Exclusions page, clicking breadcrumbs for Manage Diagnostics resulted in a page not found error. This was fixed. |
|
703 |
Bug |
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. |
|
709 |
Bug |
Diagnostic 0070 failed if there is a non-ascii character in a EmailAlert text field. This was fixed. |
|
707 |
Bug |
The number of database queries needed to run Diagnostics has been reviewed and optimized. Diagnostics will now run faster. |
|
708 |
Feature |
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. |
|
712 |
Bug |
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). |
|
743 |
Feature |
Documentation has been added to online help describing the errors and warnings which might be generated when uploading an ALS. |
|
721 |
Feature |
To further improve performance of TrialGrid web pages, gzip compression has been enabled. No differences should be visible, except for faster page load times. |
|
675 |
Feature |
The ability to apply (or remove) Labels from Tickets is now controlled by the Label permission. |
|
685 |
Feature |
Labels associated with each Draft Object type are now shown in their list. |
|
707 |
Bug |
The number of database queries needed to run Diagnostics has been reviewed and optimized. Diagnostics will now run faster. |
|
732 |
Feature |
The performance of the Edit Checks list page has been improved. |
|
769 |
Bug |
When updating PreText of a Field fast typing would cause the browser to become slow and possibly unresponsive. Responsiveness was improved. |
|
650 |
Feature |
Users currently active role for a Project is displayed in the user information drop down on every page and acts as a link to the definition of the role at the URL level. |
|
674 |
Feature |
Users may now Label Draft objects if they have Labelling permission (the same permission allows users to remove Labels) |
|
722 |
Feature |
Permission to add or delete Rave URLs is now limited to system administrators. |
|
722 |
Feature |
Retired |
Permission to add or delete Rave URLs is now limited to system administrators. |
744 |
Feature |
To improve application security a 'Content Security Policy' HTTP header has been added. |
|
745 |
Feature |
To improve application security a 'Referrer Policy' HTTP header has been added. |
|
746 |
Feature |
To improve application security an 'Expect-CT' HTTP header has been added. |
|
765 |
Bug |
After copying a Data or Unit Dictionary from a Library, the standards compliance status was incorrectly being shown as 'Modified'. This has been corrected and the copy will now 'Match' the Library version. |
|
671 |
Bug |
The Form editor and Diagnostic 0061 (valid HTML tags) were updated to accept the hyperlink <a> tag. |
|
697 |
Bug |
When a Label field was Inactive in the Form editor it could not be made active. This was fixed. |
|
112 |
Feature |
When editing Clinical Query Language in Edit Checks and Derivations, autocomplete now includes StandardValue, CodedValue, UserValue and Datapoint. |
|
687 |
Feature |
New Edit Checks and Derivations now default to Active. |
|
698 |
Bug |
Custom Functions with language 'SQL' were being exported with the Lang column set to 'SQL'. Rave expects 'SQ' or 'C#'. 'VB' has been removed as an option in TrialGrid since Rave no longer supports VB custom functions. |
|
705 |
Bug |
Uploading an ALS with Check Actions that don't match a Check caused an error on import. This was fixed so that a warning is provided. The import will not succeed in this instance. |
|
702 |
Bug |
When an ALS upload failed due to errors in the spreadsheet (for example a Field referencing a Form which does not exist in the spreadsheet draft), the errors messages were being cleared from the screen. This has been corrected and the detailed errors can now be viewed, exported and printed. |
|
704 |
Bug |
Autocomplete when editing Clinical Query Language was not firing when a record position was specified. This has been corrected. |
|
706 |
Bug |
Individual edit page for Matrix did not have standard page headings (user profile links etc) this was fixed. |
|
711 |
Bug |
Data and Unit Dictionaries with more than 1000 entries could not be saved. The limit has been increased to 5000 entries. If you have a Data or Unit Dictionary with more than 5000 entries, please contact us. |
|
710 |
Feature |
Drafts may now be compared using the Compare button on the Draft home page. |
|
714 |
Bug |
The Maximum for Matrices is now defaulted to 0 and if left blank in the Matrix editor will save as 0. Previously users were required to enter 0 manually. This behaviour has been changed to reflect the way Architect handles Maximum values (by defaulting to 0) |
|
713 |
Feature |
It is now possible to import Folders from other Drafts in the same way that Forms and Edit Checks can be imported. |
|
715 |
Bug |
When importing Forms simultaneously, duplicate Data Dictionaries and other objects could result. This has been fixed. |
|
716 |
Bug |
When creating a new (empty) Draft the dialog button now reads "Create Draft" instead of "Save Changes" |
|
719 |
Feature |
A Folder which is set as the Parent of another Folder can no longer be deleted until the child folder is "unlinked" from the parent. |
|
718 |
Bug |
Rave will export Form ConfirmationStyle as either blank or 'NoLink', which are equivalent in Rave. To ensure that the Form 'fingerprints' in TrialGrid match a blank ConfirmationStyle will be converted automatically to 'NoLink' on import. |
|
734 |
Feature |
It is now possible to import Data Dictionaries from other Drafts. |
|
735 |
Feature |
It is now possible to import Unit Dictionaries from other Drafts. |
|
720 |
Bug |
You can no longer delete a Data Dictionary or Unit Dictionary if it is "in use" by a Field. |
|
725 |
Feature |
Field Clone and Delete buttons in the Form editor now have help hints associated with them. |
|
731 |
Feature |
It is now possible to import Custom Functions from other Drafts in the same way that Forms, Folders and Edit checks can be imported. |
|
732 |
Feature |
The performance of the Edit Checks list page has been improved. |
|
739 |
Feature |
When uploading an ALS if there is a Matrix worksheet referencing unknown Forms or Folders then the warning message will only be displayed once for each unknown Form or Folder. |
|
775 |
Bug |
An error was displayed after deleting a Project. This has been corrected. |
|
776 |
Bug |
A quote character in a Static Value in an Edit Check would cause the ALS Upload to fail. This has been corrected. |
|
777 |
Bug |
After copying an Edit Check the list of Edit Checks to copy from became empty. This has been corrected. |
|
766 |
Feature |
The Matrix Explorer provides a way to visualize the Folders/Forms/Fields and Edit Checks associated with a Matrix. |
|
767 |
Feature |
When a Draft has a Default Matrix set then this is the default Matrix selected in the Matrix Explorer |
|
769 |
Bug |
When updating PreText of a Field fast typing would cause the browser to become slow and possibly unresponsive. Responsiveness was improved. |
|
670 |
Feature |
Users with the new permission Can Comment are now able to comment on Tickets. Comments are formatted in the Markdown syntax and can include references to Project wiki pages, other tickets using the #<ticket_number> and other users using the @username syntax. Users who are @mentioned in this way will receive an alert message in the application but also an email notification that they have been mentioned with a link to the location of the ticket/comment. |
|
511 |
Feature |
Tickets associated with an object are displayed in the object summary slide-out area. |
|
695 |
Feature |
A count of open Tickets associated with each Draft Object type are now shown in their list. |
|
657 |
Feature |
Breadcrumbs navigation has been improved with drop-down selection of other views within a Project or Draft. The caret (down arrow) next to a breadcrumb item can be clicked to see a list of views at the same level of the heirarchy. For example, from the Forms list you can click the Forms drop-down in the breadcrumb and select the Data Dictionaries list without having to return to the Draft Home page and then select the Data Dictionaries list. |
|
679 |
Feature |
Similar to the Project and Draft level breadcrumb navigation drop-downs, URL level objects now have breadcrumb drop-down navigation. |
|
701 |
Bug |
From Project breadcrumb navigation drop-down selecting Project Team would navigate you to Project Files. This was fixed. |