1. Home
  2. Validation rules
  3. ContPrefType_02
Learner

ContPrefType_02

Changes to the latest version will be highlighted

View the validation rules glossary of terms

Name ContPrefType_02
Version 1
Status Active
Category Learner
Severity Error
Error message

The combination of Contact preference type and code is not valid, this learner is not to be contacted

Intent

To ensure that, when the Restricted use indicator is used 'Learner is not to be contacted', there are no other Restricted use indicators used

Guidance

Ensure that where the Restricted use indicator is 'Learner is not to be contacted' there must not be any other Restricted use indicator codes or Preferred method of contacts returned

Description

If the Restricted use indicator is 'Learner is not to be contacted' there must not be any other Restricted use indicator codes or Preferred method of contacts returned

Detailed error condition
Detailed description

If the Restricted use indicator is 'Learner is not to be contacted' ( LearnerContactPreference.ContPrefType = RUI and LearnerContactPreference.ContPrefCode = 3, 4 or 5) there must not be any other Restricted use indicator codes or Preferred method of contacts returned

(error where earnerContactPreference.ContPrefType = RUI and LearnerContactPreference.ContPrefCode = 1, 2, 6 or 7) or ( LearnerContactPreference.ContPrefType = PMC and LearnerContactPreference.ContPrefCode = 1,2,3,4,5,6)

Flow chart ContPrefType_02

Open flow chart in a new window

Flow chart details

Flowchart for 'ContPrefType_02' rule

1. Is the Restricted use indicator 'Learner is not to be contacted' returned?

  • If 'No' then the rule is not triggered

  • If 'Yes' then:

2. Is there another Restricted use indicator code or Preferred method of contact returned?

  • If 'Yes' then the rule is triggered

  • If 'No' then the rule is not triggered

Change summary

Version 1

The rule has been rolled over from the previous year

Status summary

Current SLD severity

Error

Current FIS severity

Error

Is this rule in FIS?

Yes

Field values

ContactPreference.ContPrefType

ContactPreference.ContPrefCode

Need help understanding some of these terms?

View the validation rules glossary of terms