| Top of RUL | Index | Table of Contents | Feedback | |
Understanding Rules
This section of Online Help provides an overview of the Rules subsystem. Topics covered include:
Detailed
explanations and instructions for the use of rules can
be accessed from the Subsystem's Table of Contents or via the numerous links provided here.
The Rules Subsystem is used to manage the available rules for Callista, including
RULF3000 is used to control the types of Rules that a particular User Role can be edit.
RULF0100 is used to set whether a colon or a full stop (period) is used to separate Course/Unit Codes from version numbers when creating rules.
Terms Used in the Rules Subsystem
To understand the Rules Subsystem it is necessary to understand the following key terms.
| General Rules |
Generally, a group of rules that are able to be called by other rules and can be defined uniquely by their rule description and return type. These rules are viewable via RULF2001 |
| Specific Rule |
Generally, a rule which must be considered in context, i.e. they are assigned to particular data elements of Callista. For example, Unit Version rules are assigned to particular unit codes and version numbers. |
| Return Type |
The type of result a rule can return. e.g. STRING, BOOLEAN, SET etc. |
How the Rules Subsystem is Used:
Each institution will determine how the rules Subsystem is applied to its own business practices. As a guide, 'non-specialist functions' are limited to modification of rules that return type of STRING.
The remaining functionality is normally used by Subsystem specialists or System Administrators. This functionality includes:
Rules syntax is the available components of language, and their structure that are available for any particular rule. The components and structure are determined dynamically within Callista and are dependent upon either the rule subgroup or the rule description.
| Operators |
The allowable range of symbols or text, representing functionality, available. Example. +, -, AND etc |
Using -AND- and -OR- Rule Operators
If complex rules are created using AND/OR logic, it is recommended that the -AND- and -OR- (High Level Logical) options are used rather than the standard AND and OR operators.
e.g. Must be enrolled in at least 4 units in course teaching period(s) { SEM-1 } -AND- (Must be enrolled in at least 4 units in course teaching period(s) { SEM-2 } -OR- Must be enrolled in at least 4 units in course teaching period(s) { SEM-2 })
The use of the -AND- and -OR- options eliminates 'out of context messages' that may appear when using AND and OR.
| Parameters |
The allowable range of data items and their value. For example, the parameter Sex has values of FEMALE, MALE or UNKNOWN. |
| Functions |
The allowable range of rules that can be called. |
In general, parameters and functions can be considered as one and the same. This is because often, functions (other rules) will return values to the calling rule.
| Variables |
The available range of characters, used to represent variables. For example the numbers 0-9 can be used to represent variables of type numeric. |
Rules for Unit Versions are unique to the Unit Code and Version number. The rule description determines the available syntax that is available, and returns BOOLEAN to Callista i.e. returns true or false. The unit version rules are used to determine conditions that must be met prior to enrolment in a unit. Unit Version rules are viewed via CRSF2700. For the available syntax, see Unit Version Rules.
Rules for Unit Sets are unique to the Unit Set Code and Version number. The rule description determines the available syntax that is available, and returns BOOLEAN to Callista (i.e. returns true or false). The unit set rules are used to determine conditions that must be satisfied prior to enrolment in a unit set, or whether the completion requirements of the unit set have been satisfied. Unit Set rules are viewed via CRSF4230. For the available syntax, see Unit Set Rules.
Rules for Course Versions are unique to the Course Code and Version number. The rule description determines the available syntax that is available, and returns BOOLEAN to Callista i.e. returns true or false. The Course Version rules are used to determine whether or not the requirements of the course have been satisfied; whether the course requirements for an honours level have been met; to derive the commencing student indicator for the statistics Subsystem. Course Version rules are viewed via CRSF1700. For the available syntax, see Course Version Rules.
Rules for Course Stages are unique to the course code, version number, and course stage type. The rule description determines the available syntax that is available, and returns BOOLEAN to Callista i.e. returns true or false. The course stage rules are used to determine whether or not the requirements for a stage of a course have been met. Course Stage rules are viewed via CRSF12D0. For the available syntax, see Course Stage Rules.
Completion Rules
Completion rules can be created at any of three levels in the course structure — Unit Set; Course Stage; Course Version. Refer to the sections above for a broad outline of rules that apply to each level of the course structure and a link to the relevant syntax documentation. For an overview of the concepts behind constructing and applying completion rules, see Completion Rules Overview.
These rules are used to create the messages displayed in PRGF9030 when a student's potential completion of a course, course stage, alternative exit or unit set is tested. Completion message rules can be viewed in RULF2001. A standard set of message rules is supplied with Callista but these can be added to or modified. For available syntax and further information see Completion Message Rules.
Rules for the Progression Subsystem
Concepts relating to the construction and use of progression rules are described in the Progression Rules Overview. For available syntax, see Progression Rules.
Rules for the Admission Correspondence Subsystem
Rules for the Admission Correspondence Subsystem are grouped into four distinct sub groups. These sub groups determine the syntax that is available, and return STRING (e.g. `This is a string!`) to Callista. The rules are used to create text that can be inserted into a word template for an acknowledgment or outcome letter. Admission Correspondence rules are viewed via RULF2001. For the available syntax and the list of released rules, see Admission Rules.
Rules for fee disbursements are unique to the Fee Type, Calendar Type and Fee Disbursement Formula number. The rule description determines the syntax that is available, and returns BOOLEAN to Callista i.e. returns true or false. The fee disbursement rules are used to determine whether or not a fee disbursement formula applies to a student and/or a course. Fee Disbursement rules are viewed via FINF7240. For the available syntax, see Fee Disbursement Rules.
Rules for the Student Finance Subsystem are grouped into one distinct sub group. This sub group determines the syntax that is available, and returns NUMBER (e.g. 99 ) to Callista. The rules are used to calculate the fee liability for a student. Finance rules are viewed via RULF2001. For the available syntax, see Finance Rules.
With the introduction of DIISRTE reforms from 2005, new tax and loan rules will apply. See the end of Finance Rules for further details.
Enrolment Message Rules
These rules are used to create messages to be displayed when a student fails to satisfy a Unit Version rule that is tested on unit enrolment. Different levels of message are available, with Level 1, 2 and 3 messages created using the rules in the HEADING subgroup and Level 4 messages in the MESSAGE subgroup. Enrolment Message Rules are viewed via RULF2001. For syntax and further information see Message Rules.
There are 3 rules in this subgroup. They are:
These rules are a Sub-group of Enrolment rules and can be viewed via RULF2001. For syntax and further information see Enrolment SYS-WIDE rules.
These rules are used to create messages for display when a student’s progress is unsatisfactory. Such messages are displayed when True is returned for a student Progression Rule check. Progression Message rules are viewed via RULF2001. For syntax and further information see Progression Message Rules.
These rules are used to control how rules are applied throughout the system. e.g. Controlling the extent to which unit translation cascades. System rules are viewed via RULF2001. For syntax and further information see System Rules.
These rules are used to define cohorts of Students, Student Course Attempts or Student Unit Attempts. Cohort Rules are viewed via GENF1000. For syntax and further information see Cohort Rules.
These rules are used to Verification standards for Scholarships. Scholarship Rules are viewed via SCHF0600. For syntax and further information see Scholarship Rules.
Last Modified on 28-Apr-2011 10:39 AM
History Information
| Release Information | Project | Change to Document |
| 13.1 | 1666 - Prevent Students from Exceeding Allowable Portion of Online or Distance Learning Limits | Added a paragraph about -AND- and -OR- operators |
| 11.0.0.2.0.0 | 1508 - VET Rules | Updated links and added Rules Configuration section. |