The Rule Update screen is used to update existing Rule records.
Note: Field names on the screen with red labels* are required by the screen design you are using. Mandatory fields in the default Vermont Systems design are noted where appropriate. Your design and mandatory fields may vary.
See Also: RecTrac Rules for a detailed description of RecTrac Rules, set up information, and examples.
See Also: Video - Rules
Click here for a list of Criterion Types and their Definitions.
Click here for field definitions for all Criterion Types.
From the bottom of screen....
Click Save to save your changes and return to the previous screen.
Click Cancel to return the previous screen without saving your changes.
Click Previous or Next to move to the next tab on the screen.
Core
Rule Description (SARule_Description)
Enter a description (i.e. a name) for your Rule. This is an alpha-numeric field and will accept up to 100 character.
For Example: Age Requirement - Adults
DeleteRule Option (SARule_RuleOption)
Expand the Drop-down list to select your Rule Option.
- Allow - Allowance rules permit the desired transaction to proceed.
- Disallow - Restriction rules forbid the desired transaction to proceed.
When deciding which to select, think about which option is most straightforward.
For Example: If creating an Age Requirement - Adults" rule ask yourself whether it easier to say that patrons who are aged 18 to 69.99 are allowed to register or easier to say that patrons who are aged 0-17.99 or who are aged 70 and older are disallowed to register. In this case it seems easier to Allow patrons within one age range to register than it is to Disallow patrons NOT between two age ranges to register.
DeleteTransaction Type (SARule_TransactionType)
Select the Transaction Type(s) to which this rule will apply. Multiple selections are allowed.
Press and hold the <CTRL> key and click with your mouse to multi-select.
- Cancellation - Any cancellation in any module.
- Change - Any change in any module.
- Book - Any Tee Time and Court Slot booking/reservation.
- Permit - Any Facility Reservation permit.
- Purchase - Any purchase in any module (i.e. Registering for an Activity or a Pass making a Facility Reservation renting a locker etc.) except Tee Times and Court Slots. Those are handled under Book.
- Renewal - Any renewal in any module (i.e. renewing a Pass renewing a Locker rental etc...).
- Transfer - Any transfer in any module (i.e. transferring an enrollment transferring a Pass etc...).
- Visit - Any fees associated with a Pass Visit.
- Visit Cancellation - Any fees associated with a Cancelled Pass Visit.
- Visit Swipe Out - Any pass swipe that results in a Visit Check Out or the end of any Rental.
- Waitlist - Any fees associated with being added to a Waitlist in any module
- Lottery Enrollment - Any fees associated with Activities set to Lotto Only enrollment where you want to charge a fee for enrollment into the lottery. Lottery Enrollment fees are applied to the balance due for lottery "winners" and are refunded to the non-winners upon completion of the Lottery Spin.
- Lost Card - Any fees associated with lost pass membership cards/key fobs.
- Late Payment - Any penalty fees for late payments.
- Tee Sheet/Court Check in - Any fees associated with/charged during Tee time or Court reservation check-in
- Rental Start - Any fees associated with/charged during the start of rental.
- Rental/Locker Completion - Any fees associated with the end/completion of a rental item or locker type rental.
- No Show - Any fees associated with reservation no shows such as Tee Time No Shows.
- Impound - Any fees associated with locker impound procedures.
- Deposit Refund - Any fees associated with deposit refunds.
Status (SARule_RecordStatus)
Accept the default entry (Active) or expand the Drop-down list to select an alternate status, if desired.
- Active - The rule is active.
- Inactive - The rule is inactive.
- Default - See below for a description
Default Status
Default" status allows you to create exact-copy records upon clicking the Add button from the File Management DataGrid for this module and selecting one of existing Default Options (provided at least one exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings Additional Settings etc.) and tabs (Core Fees* Rules* Questions Comments etc.) will be copied from the default record.
"Default" status records to do not show up in Daily Processing DataGrids. You cannot register for reserve or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a default record to "Active" or "Inactive it will become a regular record" in your database and thus appear in Daily Processing DataGrids.
Options for adding default records are maintained on the Permissions profile Default Record Permissions Group.
* Separate default records for fees and rules can be created as well in their respective File Management program. Permissions must be set to add a Default Record and once added the default record can be linked as needed to any module.
DeleteRule Group (SARule_RuleGroup)
Accept the default (N/A) or expand the Drop-down list and select Rule Group to which this rule belongs, if any. Your options are OrGroup1 through OrGroup5.
When working with single Rules, the criterion of the rule must be met in order for the rule to take effect. For Example: a Men's Softball League might have a allowance rule for Gender=Male. Any patron with a gender other than 'Male' would not be allowed to register.
When working with Rule Groups, the criterion of at least one (1) rule in the Group must be met for the rule to take effect, though multiple criteria may be met. For Example: a Men's Softball League might have an allowance rule for Resident Registration Date any day/time after 08:00am on April 1 and an allowance rule for Non-Resident Registration Date any day/time after 08:00am on April 14. A Patron cannot be both a Resident and a Non-Resident, so the criterion of one (1) Rule only in this Group would have to be met to allow Registration.
Rule Group labels (OrGroup 1 through OrGroup 5) are hardcoded throughout the system. An OrGroup is relevant only to the specific transaction structure/hierarchy to which it belongs. This means that you can chose an OrGroup label and use it more than once to group different rules together, provided the same OrGroup label is not used multiple times within the same transaction structure hierarchy.
For Example: You could have a Group of Rules governing registration policy for your Summer Season programs, and it could be labeled OrGroup1. You could also have a Rule Group governing registration policy for your DayCare activities, and it could be labeled OrGroup1 as well. You could use OrGroup1 as the Rule Group label for both groups of rules provided there is no hierarchical overlap between them where the two groups of rules would come into conflict. An example of a hierarchical conflict would be linking a Rule Group (label=OrGroup2) at the Activity Type level and then linking a second Rule Group with the OrGroup2 label to an Activity within that Type.
DeleteRule Type (SARule_RecordType)
Accept the default (None) or expand the Drop-down list and select Rule Type to which this rule belongs, if any. If your Rule is not for a specific Type listed here, leave the setting at None.
- League Player - This Rule Type is designed for use with player-specific rules that are linked to a League (For Example: age, gender, etc…). When used, this Rule Type will check all of the default team players at the time of registration to determine whether they meet the rule criteria.
- Match Rule with Linked Tee Time/Court Slot - For future use.
- CYMS Reservation - This Rule Type is for CYMS Users who manage Hourly Care programs. CYMS Reservation Rules are used for the CYMS SuperGrid and in WebTrac for CYMS Search for Care logic.
Rule Override Option (SARule_Override)
Expand the Drop-down List to select your Override option for this Rule.
- Warning - The system will advise you that continuing to process the transaction will violate the Rule, but it will not stop you from completing the transaction.
- Override With Rights - The system will advise you that continuing to process the transaction will violate the Rule. Users will be allowed to override the warning and bypass the Rule IF they have an Override Code linked on their Permissions Profile for the applicable module (Core Information Tab • Module Settings Group • <Module Field>). Any Override Code will work.
- Override With Matching Codes - The system will advise you that continuing to process the transaction will violate the Rule. Users will be allowed to override the warning and bypass the Rule ONLY IF they have an Override Code linked on their Permissions Profile for the applicable module (Core Information Tab • Module Settings Group • <Module Field>) that matches any of the Override Codes listed in the Override Codes field.
- Deny - The system will not allow you to override/bypass the Rule. If this field is set to Deny no Override Code will allow you to bypass this Rule.
Permission Override (SARule_PermOverrides)
This field is applicable only if you are using the Override With Matching Codes Rule Override option.
Click the Picklist icon to select the Override Code/Codes you wish to link to this field. In order to override the Rule users must have at least one (1) of the Override Codes entered in this field linked on their Permissions Profile for the applicable module. One match only is needed.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
For Example: This Rule is an Age Restriction for Adults aged 18-69.99. Your Override option is Override With Matching Codes Only. You have Override Codes 'SPORTS' and 'ADMIN' linked here. Clerks who work at the sports complex with Override Code 'SPORTS' linked to their Permissions Profile could override this Age rule. Administrators with Override Code 'ADMIN' linked to their Permissions Profile could override this Age rule. Clerks who work at the Rec Center with Override Code 'RECCEN' linked to their Permissions Profile could not override the Age rule for this program because they do not have a matching Code.
DeleteParent ID (SARule_ParentID)
You will not visit this field.
This is a system-controlled field that displays Parent ID information for this rule.
DeleteParent Table (SARule_ParentTable)
You will not visit this field.
This is a system-controlled field that displays the Parent table to which this rule belongs.
DeleteCloneID (SARule_CloneID)
You will not visit this field.
This is a system-controlled field that displays Clone ID information for this rule if applicable.
Delete