System Rules

These rules are in the SYSTEM Rule Group and are used to control system-wide effects of rule applications.

This rule group contains SET-RULES and MESS-RULE sub-groups which are maintained in RULF2001.

SET-RULES Sub-Group Rule.

This rule is used to define the level of translation expansion to occur for all rules that use sets of units. Whenever the translation of units is performed, the original set of units is always included in the expanded set.

Note: Rule options may also be combined, to produce rules such as 'Single Level Translations(Single Level Translations($1))'. In this example, a translation expansion of two levels will result. THIS ABILITY SHOULD BE USED WITH CAUTION AS UNINTENDED RESULTS MAY OCCUR

Example 1

Where equivalent units exist within an institution, or where a previously offered unit has been expanded to form a new unit, Unit Translation rules may be created. For example, Unit MAA101 might have a rule 'Unit was previously coded as MXX101' and in turn, MXX101 might have a rule 'Unit was previously coded as MZZ101'.

In this case if a rule 'Incompatible with {MAA101}' is created for a unit, then whether or not MXX101 and MZZ101 are also incompatible with this unit depends on the Translation Expansion Level RULE that is in place.

If this rule is of the form $1, then no translations will take place and in the example above only MAA101 will be incompatible.

If this rule is of the form 'Single Level Translations($1)', then one level of expansion will take place and in the example above both MAA101 and MXX101 will be incompatible.

If this rule is of the form 'Cascade Translations($1)', then all translations will be effective and in the example above, MAA101, MXX101 and MZZ101 will all be incompatible.

Example 2

Unit A has a prerequisite rule 'Must have passed a unit in {B}'.

Unit B has a unit translation set rule 'Unit was previously coded {C}'.

Unit C has a unit translation set rule 'Unit was previously coded {D}'.

If the translation expansion rule $1 is in place, only B will be evaluated as a prerequisite for Unit A.

If the 'Single Level Translations($1)' rule is in place, C will be accepted as a prerequisite for A.

If the 'Cascade Translations($1)' rule is in place, both C and D will be accepted as a prerequisite for A.

Snarts Expansion Level (#SET) RULE:

This rule is used to define the level of reverse translation expansion that will occur. This determines the level of expansion that occurs to units that are included in the rule text for Unit Translation Rules.

RULE OPTIONS FOR Snarts Expansion Level (#SET) RULE:

Rule Text	Usage
$1	The set of units is not expanded - translations are not considered. Only the original units - included in the unit set.
Single Level Snarts ($1)	The set of units is expanded by the first level translation. The original set of units is included.
Cascade Snarts($1)	The set of units is expanded recursively, using all levels of translation. The original set of units is included.

Note: Rule options may also be combined, to produce rules such as 'Single Level Snarts(Single Level Snarts($1))'. In this example, a translation expansion of two levels will result. THIS ABILITY SHOULD BE USED WITH CAUTION AS UNINTENDED RESULTS MAY OCCUR

Example Where a Unit Translation rule has been created for unit MAA101 'Unit was previously coded as MXX101', if the system is configured so that no reverse translation occurs, MAA101 is expanded but MXX101 is not affected (unless a corresponding Unit Translation rule is created for it). However if reverse translation can occur then MXX101 will be expanded also.

MESS-RULE Sub-Group Rule.

Format Unit Set Rule:

This rule is used to definehow Unit Set information is displayed by the system.

Rule Options for Format Unit Set Rule:

Rule Text	Usage
UNIT_SET_CD	The code for the Unit Set
UNIT_SET_SHORT_TITLE	The short title of the Unit Set
UNIT_SET_CAT_DESC	Description of the Unit Set category
UNIT_SET_VERSION	Unit Set version
+	Joins together separate elements of the rule in the message
`	Accent symbols are used to enclose free text which will be displayed in the message.

Example If the Format Unit Set Rule is defined as UNIT_SET_CD+' - 'UNIT_SET_SHORT_TITLE only the unit set code and unit set short title will display. So, if the rule "Must have enrolled and completed 2 unit sets in {ACM001.1 or ACM002 or ACM003}" is created via CRSF1700, anywhere else that this rule or its evaluation message is displayed or reported it will display like "Must have enrolled and completed 2 unit sets in {ACM001 – ACCOUNTANCY or ACM002 - COMMERCE,ACM003 - INDUSTRIAL RELATIONS}" and its evaluation message will display like "Has completed 1 unit sets in {ACM001 - ACCOUNTANCY} Still requires 1 unit sets in {ACM002 - COMMERCE,ACM003 - INDUSTRIAL RELATIONS}.

Note Commas included within free text may display as the word "or" in the relevant rule messages. To avoid possible confusion, comas should be avoided in free text in this rule.

Format Special Requirement Rule

This rule is used to define how Special Requirement information is displayed by the system.

Rule Options for Format Special Requirement Rule:

Rule Text	Usage
SPEC_REQ_CD	The code for the Special Requirment
SPEC_REQ_DESC	The description for the Special Requirment
+	Joins together separate elements of the rule in the message
'	Accent symbols are used to enclose free text which will be displayed in the message.

Example If the Format Special Requirement Rule is defined as SPEC_REQ_CD+' - 'SPEC_REQ_DESC both the special requirement code and description will display with a hyphen between them. So, if the rule "Must have completed special requirement of type BM" is created via CRSF1700, anywhere else that this rule is displayed or reported it will display like "Must have completed special requirement of type BM - BRONZE MEDALLION" and its evaluation message will display like "Has not completed special requirement of type BM - BRONZE MEDALLION'.

Last Modified, on 20 December, 2005