Rules

rules overview rules can be defined by users and may also be found in published standards rules define how content in a standard can be used in other standards or studies in other words, rules that are created in a standard apply to content that derives from that standard ryze ensures that rules in a derived standard are compatible with its parent standard for example, when content from a sdtm ig 3 3 standard is imported into a new stdm standard, the new standard will inherit any rules present in the parent stdm ig 3 3 standard users may then configure additional rules in the new standard if the new standard is used in a subsequent study, content in the new study is restricted by the rules imposed from the new standard, as well as the rules imposed from the parent sdtm ig 3 3 standard rules can define how assets are used for example, requirement rules can be used to ensure that a property is completed by the user or pattern rules can be used to allow only certain permitted characters in a property the type of rule that is available depends on the type of property that it is applied to for example, a restriction rule can be used to limit the maximum value for an integer property example scenario a standard contains a single form with rules applied meaning that all sections on the form are mandatory, and all questions in those sections are mandatory when this form is imported into a study, all sections and all questions must appear on the form this is true whether the imported asset is in a study or in a standard if it is imported from a standard, the rules of that parent standard determine how the content is used rules can be displayed by clicking the filter icon and selecting show rules available rules the following rules are available in ryze requirement the following requirement rules can be set on reference properties, for example, terminologies in a question required the input value must be set by the user in order to be saved fixed the input value cannot be changed by the user the options that are displayed depend on the property that the requirement rule is applied to for example, some requirement rules can be set to either fixed or required and some rules may be set to fixed only the following requirement rules can be set on reference list entries, for example, terms in a terminology required the referenced asset must be present in order for the parent asset to be saved conditional this is a flag used for variables in adam datasets and functions the same as permissible rules permissible the referenced asset can be present this is the default setting when creating a new term not suggested the referenced asset should not normally be present, but is permitted a warning is displayed indicating that the property is not suggested as an option non extensible extensible properties are lists that can have additional entries added to them such as reference lists (for example, terms in the nci controlled terminology standard) or embedded lists (for example, aliases on a question) non extensible properties cannot contain additional entries non orderable orderable properties are lists that can have their list order changed for example, the order of terms in a terminology non orderable properties cannot be reordered pattern pattern rules can be set on properties with a ‘text’ datatype pattern rules allow you to define a regular expression (regex) that a property must conform to if a property does not comply with a pattern rule, the asset is flagged as non compliant in ryze you can read more about regex https //developer mozilla org/en us/docs/web/javascript/guide/regular expressions restriction restriction rules can be set on properties with an ‘integer’ datatype restriction rules allow you to set a maximum value for a property for example, the length of a variable can be restricted to a maximum value of 200 importing assets with rules when content is imported from another standard, all existing rules are imported from the parent standard rules in the imported standard must be compatible with the parent standard the user can choose to make a rule more strict but not less strict this means that a derived standard is compatible with its parent standard for example, a property on an asset in a standard cannot be set to orderable if it derives from a parent asset that is defined as being non orderable see the following examples fixed (requirement) rules cannot be removed from properties in the imported asset required (requirement) rules cannot be removed from reference lists in the imported asset for example, terms in a terminology non extensible rules cannot be removed or changed from properties in the imported asset non orderable rules cannot be removed or changed from properties in the imported asset length rules cannot be increased if there is a maximum set in the parent standard