Module : Standard Rules

Issue	Type	TrialGrid Version	Description
3863	Bug	68	When rules for matrices or matrix folders are active for a draft, trying to view the active rules for the draft resulted in an error. This was corrected.
3726	Feature	66	It is now possible to create standard rules for custom objects.
3759	Bug	65	When an parent object such as an edit check had a must not exist rule but did exist, in compares only the name of the object and the rule text was shown, the comparisons of other attributes was not shown. This was corrected.
3761	Feature	65	When an object passes a MUST EXIST rule, in compares you now see that the object passed the rule. Previously this was not shown, only failed MUST NOT EXIST rules were shown.
3658	Bug	61.1	When a draft linked to a library activated more than one must-exist rule for an object, missing object calculations did not occur properly and compliance for objects was not properly calculated on save. This has been corrected.
3546	Feature	59	When downloading an ALS for a library there is now an option to download Standard Rules. Previously they were automatically included.
3504	Bug	57	When creating a draft from a library, copied checks do not check the objects referenced by AddForm, CustomFunction and Add/MergeMatrix actions to see if copying those objects is allowed. This was corrected.
3443	Bug	55	A large study with a large number of rules would use a lot of memory when creating a draft from library which could cause the process to be stopped by the server infrastructure. Memory usage was improved.
3392	Bug	53	When creating a standard rule precondition with an "and" statement in it, it was possible to create an invalid precondition without error. This has been corrected.
3371	Feature	52	It is now possible to explain why objects required by MUST EXIST rules are missing in bulk from the Draft Missing Object view.
3317	Feature	50	"May Exist" Standard Rules may now be created. Objects identified by May Exist rules are copied from the Library during "Create Draft from Library" operations but are optional in the study so may be deleted from the study draft without triggering a Missing Object deviation as a Must Exist rule would.
3318	Feature	50	In standards compares it is now possible to hide Rules passed messages since with a large number these can be distracting.
3320	Feature	50	When a rule enforces a value that is the same as the library value this is now reported as a match rather than a rule passed because if the rule did not exist it would still be a match to the library value. For example if a rule requires SDV to be True for a field and the field has SDV=True and the library has SDV=True then the rule has passed but there is no deviation from the library anyway so this is now reported as MATCH rather than Rule Passed.
3225	Bug	47	When importing a draft with Rules, the internal data type for the rule was not set which affected reporting of missing objects. This was corrected.
3147	Bug	45.3	The Draft Comparison report was failing when comparing Library Drafts containing Standard Rules. This has been corrected.
3137	Bug	45.2	Standards Compliance Calculations looked for rules related to the object identifier, not the standards object identifier which meant that when an object in a draft was linked to a library object with a different name, rules would not be found during compliance calculations. This was corrected.
2086	Feature	44	When a Draft is linked to a library with Rules a listing of missing objects is shown on the Draft home page.
3061	Feature	44	It is now possible to explain why objects required by MUST EXIST rules are missing.
3068	Bug	44	When cloning a draft the order of Check actions in the clone did not always match the order in the original checks. This was corrected.
2679	Feature	43	Description column now appears in the rules listing. Note that not all columns of the rules listing are available at all screen widths.
2981	Feature	43	Wildcard value attribute rules for non-string values (e.g. Field IndentLevel which is numeric) would silently fail and the rule would be ignored. This was corrected.
3046	Bug	42.3	Rules created to set ParentFolder attribute of a Folders to empty value (i.e. to remove parent folder value) were failing and being ignored. This was corrected.
3047	Bug	42.3	Rules created to set ParentFolder attribute of a Folders to empty value (i.e. to remove parent folder value) were showing different in compares even when the ParentFolder was blank. This was corrected.
2923	Bug	41	In the Create Draft from Library process, if an Edit Check has a MUST EXIST rule and references a Form with a MUST NOT exist rule then the draft creation process would not complete. This was corrected.
2928	Feature	41	In the Create Draft from Library process, Derivations are now automatically copied if their Folder/Form/Field references exist in the generated Draft.
2934	Feature	41	In a standard compare the description of a rule is now shown (if set) as well as the logic of the rule which can be cryptic for users.
2855	Feature	40	In the create draft from library dialog when there are warnings about unset Project properties the link now takes the user direct to the metadata tab
2681	Bug	35	Wildcard Object Identifiers and rules were being taken into account in standards compliance compares but not in the calculations. This was corrected.
2684	Bug	35	Links to Standard Rules from the compare dialog did not correctly open the rule in the rule list view. This was corrected.
2685	Bug	35	When creating a draft from a library, if View/Entry Restrictions were set to empty value by an attribute rule then this change would fail with an error. This was corrected.
2672	Bug	35	Standard Rules were not being exported from Library Drafts in ALS exports. This was corrected.
2647	Feature	35	Standard Rules override standard settings controls. For example, a form may allow fields to be deleted but if a rule says a field must exist then the Rule gets precedence.
2650	Feature	35	When creating a draft from a library via Standard Rules Matrices are now processed before edit checks so that AddMatrix and MergeMatrix check actions can be incorporated from matrices.
2651	Feature	35	It is now possible to define wildcard Must Have Attribute Standard Rules. A wildcard Must Have attribute rule is not setting a value, it is ensuring that a value matches a pattern.
2374	Feature	35	Duplicate of #2651 above.
2652	Feature	35	It is now possible to select the Attributes of Edit Checks in the Rule editor.
2519	Feature	34	Wildcards can now be entered as object identifiers in Standards Rules. This allows Rules to be written that are applied to all objects that match the Wildcard. Wildcards use regular expressions to match objects by name as explained in the help.
2523	Feature	34	Object Identifier selections (including wildcards) can now be tested from the Rule Editor dialog. This allows you to see which objects from the library draft would be selected by this identifier.
2433	Feature	31	There is now an option to show greater detail in the Draft from Library dialog. This helps to understand why objects are copied into the Draft from the Library.
2313	Bug	26	When a Draft was created via Rules from a Standard Library the count of field level checks was not being updated (it showed 0 field level checks). This was corrected.
2282	Feature	25	When creating a Draft from a Standard Library users are now prompted how to fix missing metadata references.
2265	Feature	25	The listing of Rules activated for a Draft now include links to related Draft objects where they exist.
2290	Feature	25	In the Rule Editor it was possible to enter invalid Object Identifiers. This was corrected and help was expanded to explain how to create valid identifiers for some object types where the object names contain period (.) characters.
2242	Feature	23	Rules which use single quotes rather than double quotes are now properly displayed.
2244	Feature	23	Standard compare results now show the original library value even when it is overridden by a "Must have Attribute Rule"
2149	Feature	22	Standards Rules are now displayed in a more human readable way.
2150	Feature	22	On the Draft home page a count of active Standards Rules is only shown if the related Library has Standard rules defined.
2153	Feature	22	On the Draft home page a list of active rules is now available. This shows which rules have been activated by the Project Property settings.
2151	Feature	22	Standard Rules display for Fields in the Form editor now includes the description from the Standard Rule if any.
2046	Feature	22	Objects in a Library Draft which have related Standard Rules now have a tab which displays those rules (previously only the Form editor had this tab).
2155	Feature	22	When creating Drafts from a Library the objects copied have their copied-from information set to the library object they were copied from so that their source is recorded.
2156	Feature	22	When creating Drafts from a Library the Draft attributes such as Primary Form, Primary Matrix and signature prompt etc should be copied from the Library draft.
2170	Feature	22	When generating a draft from the library, appropriate matrices and their folder/form combinations are now also copied over. See help on generating Drafts from Libraries for more information.
2804	Feature	21	When creating a Draft from a Library, the Project the Draft is to be created in must have values set for all Custom Project Properties that the Library uses to resolve the rules. i.e. If an active Rule relates to a "Therapeutic Area" then the Project must have the Therapeutic Area property set or the Rule would not be able to be resolved.
1999	Feature	19	Standard Rules were changes to allow entering a logical expression. This allows more complex Standards Compliance rules to be created.
2000	Feature	19	When a custom property is deleted which relates to a Standard Rule, uses of that Rule are re-evaluated.
1891	Bug	17	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.
1864	Feature	17	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	17	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	17	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	17	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	17	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.
1778	Feature	16	It is now possible to create a Draft from a standard library with Standard Library Rules applied.
1810	Feature	16	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)
1768	Feature	16	Forms in Libraries now show a list of Rules related to that Form under the Standards Control tab.
1769	Feature	16	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.
1766	Feature	16	It is now possible to filter the Rules list similar to a spreadsheet autofilter function.
1759	Feature	16	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)
1733	Feature	16	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.
1724	Feature	16	Standard Rules may now be deleted from the list of Standard Rules.
1719	Feature	16	Standard Rules may be created from the Standard Rules listing for a Draft in a Standard Library.
1696	Feature	16	Drafts within Standard Libraries now have a listing of Standard Rules.
1690	Feature	16	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	16	Breadcrumbs for a Standards Library Draft now include a link to Rules.