Version : 4
Released : 2018-02-05
Changes in this Release
Issue |
Type |
Module(s) |
Description |
|---|---|---|---|
623 |
Feature |
When a wiki page that does not yet exist is referenced, e.g. [[No Such Page]] then it appears in an orange color with a broken-link icon following it. A wiki page which exists is shown as a link with the standard blue color with a link icon following it. |
|
618 |
Bug |
Non-ASCII characters in Edit Check or Derivation names were causing some Diagnostics to fail. This has been corrected. |
|
620 |
System |
Some Diagnostics were generating errors in the system log when reporting results of fixing back to the user. This had no impact to users but has been corrected. |
|
637 |
Feature |
Diagnostic 00074 has been added to identify Form Redirect settings which are not valid for RaveX studies (currently only "NoLink" setting is valid) |
|
639 |
Feature |
Diagnostic results are now ordered by the reference number of the Diagnostic (e.g. 0001, 0002...) PDF reports generated before this change still appear in the previous ordering. |
|
646 |
Feature |
A new Project Level permission (Explain Diagnostic Result) was introduced which controls whether a user may explain a diagnostic result or reset a diagnostic explanation. |
|
2655 |
Feature |
Users can reset diagnostic explanations if they have permission to do so. |
|
2654 |
Feature |
Users can explain diagnostic findings if they have permission to do so. |
|
166 |
Bug |
The number of findings for the latest diagnostic run for a Draft is now updated when findings are fixed or explained, so that the number of unresolved findings is displayed. |
|
604 |
Bug |
Diagnostic 0020, Spell checking, can generate multiple findings for the same Draft object, for example, several entries within a Data Dictionary may have findings. Prevoiusly entering an explanation for one finding for the Dictionary would explain all findings for that Dictionary. Now each explanation applies to one finding only. |
|
605 |
Feature |
Findings from Diagnostic 0020, Spell checking, now have links to Data and Unit Dictionaries. |
|
607 |
Feature |
When an explanation of a Diagnostic finding is reset, the Fix button will be re-displayed when a fix is available. |
|
608 |
Feature |
Findings from Diagnostic 0020, Spell checking, now display the Form OID for findings related to a Field in addition to the Field OID. |
|
647 |
Bug |
Diagnostic 0020, Spell checking, was incorrectly reporting findings if an html tag separated two words, for example 'severe<b>reaction</b>' would be reported as 'severereaction'. This has been corrected. |
|
620 |
System |
Some Diagnostics were generating errors in the system log when reporting results of fixing back to the user. This had no impact to users but has been corrected. |
|
641 |
Feature |
A new Project Level permission (Edit Objects) was introduced which controls whether users may add, edit or delete objects in a Draft. |
|
652 |
Feature |
When a user with no Standards Compliance workflow permissions opens the Explain dialog a warning is shown that the user has no permissions to change the state of the Explanation. |
|
653 |
Feature |
Only users with Create Draft permission are now able to edit Draft properties. |
|
654 |
Bug |
Retired |
Custom Function and Custom Function Template name inputs now have styling consistent with other controls on the editor page. |
622 |
Bug |
Some security policies were blocking application/ms-excel download of Drafts. As a result of this investigation the content type for downloading Drafts was changed to application/vnd.ms-excel which is the correct content type. |
|
625 |
Bug |
Resetting the users password through the forgot password functionality did not reset the failed login attempts count (potentially locking the user out indefinitely) this was fixed. |
|
592 |
Bug |
On adding a new Form to a Draft that is linked to a standard library (and does not exist in the Standard), the compliance summary showed that Fields may not be added or deleted. These directions were not meaningful and are no longer shown. |
|
613 |
Bug |
Clinical Query Language was incorrectly allowing Variables to be wild-carded. This has been corrected, and the online help updated. |
|
612 |
Bug |
If an Edit Check references a Form with wild-carded Variables then the Edit Check list would generate a Server Error. This has been corrected. |
|
617 |
Bug |
Non-ASCII characters in Edit Check or Derivation names were causing errors when creating or saving. This has been corrected. |
|
619 |
Bug |
When creating and updating Derivations there is now a check to ensure that there is not already a Derivation targeting the same Variable. |
|
270 |
Bug |
When a Form is used in Edit Checks / Derivations or referenced in a Matrix it can no longer be deleted and if a user tries to delete the Form then an error is shown that it is "in use" |
|
626 |
Bug |
When importing a Form from a Library only the first 10 fields of each Form were shown for import. This has been fixed. |
|
638 |
Feature |
Form, Edit Check, Derivation, Unit Dictionary, Data Dictionary and Custom Functions now offer an option to export to a ALS from the Action menu. An ALS created in this way contains only the tabs for the CRFDraft and the object being exported. These small ALS files can be loaded into Rave Architect in a few seconds as a merge - note that a merge will add new sub-objects (e.g. Fields in a Form) and change existing objects but will not delete existing sub-objects. |
|
640 |
Feature |
Layout of Edit Check and Form import views made it tempting to click the link to view the source object rather than to select the object to be imported. The view link was moved away from the object name and if clicked now opens the source object in a new browser tab/window. |
|
609 |
Bug |
When editing Quickedit in a Derivation an error message 'Does not evaluate to True or False' was being displayed. This should not be displayed for Derivations and has been fixed. |
|
610 |
Bug |
When using the Firefox browser, opening and then quickly navigating away from an Edit Check would sometimes display an empty dialog box. This has been fixed. |
|
616 |
Bug |
The Clinical Query Language parser was generating incorrect quickedit when a Field OID was different from the Variable OID. This has been fixed. |
|
527 |
Feature |
When editing Clinical Query Language in an Edit Check or Derivation, the position of the error will be highlighted if possible, for example when a Field OID does not exist in the Draft. |
|
631 |
Feature |
When copying Forms and Fields from a Standard Library or other Project, the list will display Forms containing Fields which do not exist in the target Draft, even if the Form does already exist in the target. This allows Fields to be copied from multiple Libraries or Projects into a Form in the target. |
|
651 |
Bug |
If the quickedit in an Edit Check or Derivation was incomplete an interal error message was being displayed. An informational error message is now displayed describing which step is missing. |
|
621 |
Feature |
Markup syntax for tickets and wiki pages has been made identical. As part of this change, existing Wiki pages were converted to the new Markdown syntax. Users can now reference tickets by number in ticket text and in wiki pages (e.g. #123 is rendered as a link to ticket #123) |
|
636 |
Feature |
In Wiki and Ticket pages, typing #<number> to reference a ticket by its number now pops up a listing of tickets starting with that number (e.g. #1 -> #1, #10, #11, #12...#100..) This makes it easier to ensure that the correct ticket is referenced. |
|
654 |
Bug |
Custom Function and Custom Function Template name inputs now have styling consistent with other controls on the editor page. |