Standards can be used to validate a user’s eligibility to participate. This event type can be used as a guard to control which path is followed in a workflow. To use the event, an Eligibility Standard ID must be provided as well as what resulting condition(s) will allow the workflow to progress past the guard.
The available conditions are:
- Allow Eligible – A typical use case is to advance a person who meets all requirements.
- Allow Soft Failure – A typical use case is to offer a person who fails a grade eligibility check to submit an appeal.
- Allow Hard Failure – A typical use case is to deny a person who fails a conduct probation check.
The Eligibility Standard ID must be defined by IT in the database as follows:
Basic Structure
An eligibility standard (dbo.eligibility_standards) consists of many eligibility rules (dbo.eligibility_rules). Any or all rules in a standard can apply to the user in the eligibility check. Each rule has several eligibility criteria (dbo.eligibility_criteria), each of which must be satisfied to pass the rule. An eligibility criteria is composed of a criteria match string, an operand, and a value (ex. “blinn” “=” “false”). Once a user has passed each criteria for each rule that applies to themself for the standard, they have passed the eligibility check.
Supported Eligibility Criteria
Any criteria that is not satisfied results in a “Soft Failure” except conduct which results in a “Hard Failure”. This is to allow workflows to distinguish when an option for appeals can be offered. An appeals option cannot be offered if conduct eligibility is not satisfied.
Student Eligibility Factors
- “blinn”: Is the Student enrolled at Blinn?
- “conduct”: Does the Student have an active conduct probation record on file? (Hard Failure if not satisfied)
- “enrolled”: Is the Student enrolled for the current or upcoming term?
- “gpa_cumulative”: What is the Student’s cumulative GPA?
- “gpa_latest”: What is the Student’s previous semester GPA?
- “hours”: How many hours is the Student enrolled?
- “time_status”: What is the Student’s enrolled status?
Employee Eligibility Factors
- “employed”: Is the Employee employed?
- “employee_description”: Does the Employee description match?
- “employee_type”: Does the Employee type match?
- “employee_percent_effort”: Does the Employee percent effort meet the requirement?
Supported Operands
‘<’, ‘<=’, ‘=’, ‘=>’, ‘>’, ‘in’
‘in’ describes a situation where a value is contained in an array, the rest of the operands describe scalar comparisons and Boolean truth statements.
Example
Hosted in OrgManagement_Demo, representing Student Rule 41.2 concerning student organization officer eligibility found at https://student-rules.tamu.edu/rule41/.
Schema
Standard: “Student Organization Rule 41.2”: id 3
- Rule 1: id 3 – Undergraduate Students
- “gpa_cumulative >= 2.0” : id 3
- “gpa_latest >= 2.0” : id 4
- “hours >= 6” : id 5
- “conduct = false” : id 16
- Rule 2: id 4 – Professional Students
- “gpa_cumulative >= 2.5” : id 7
- “gpa_latest >= 2.5” : id 8
- “hours >= 6” : id 9
- “conduct = false” : id 17
- Rule 3: id 5 – Graduate Students
- “gpa_cumulative >= 3.0” : id 12
- “gpa_latest >= 3.0” : id 13
- “hours >= 5” : id 15
- “conduct = false” : id 16