1. Non-statutory Client Defined Rules
1.1. Rules Builder User Interface
1.2. Tightly coupled with fields?
2. Characteristics
2.1. Rules Return a Result
2.1.1. Boolean
2.1.2. Double
2.1.3. Null
2.2. Business Process Can Leverage One or More Rules
2.3. Tokens
2.3.1. Constant
2.3.2. Business field
2.3.3. Metadata field
2.3.4. Operation
2.4. Context
2.4.1. Client
2.4.2. Country
3. Use Cases
3.1. Eligibility
3.2. Validations
3.2.1. Define processes that require validation
3.2.1.1. Enrollment Rules Helper
3.2.2. Validator takes in an object and returns a result
3.2.2.1. null if rule is obeyed
3.2.2.2. RuleResult if violated
3.2.2.2.1. Status code
3.2.2.2.2. Severity
3.2.2.2.3. Entity identification
3.3. Calculations
3.3.1. Connections / field representation
3.4. Compliance
3.5. Suggestions / Defaults
4. Metadata
4.1. Country Specific Logic Without Code Changes
4.2. Localized Metadata Packages
4.3. Tight Governance Process
5. Fields
5.1. Associate
5.1.1. Birth date
5.1.2. Birth city
5.1.3. Birth state
5.1.4. Birth district
5.1.5. Birth postal code
5.1.6. Birth country
5.1.7. Student
5.1.8. Disability
5.1.9. Disability percentage
5.1.10. Gender
5.1.11. Marital status
5.1.12. Nationality
5.2. Employee
5.2.1. Status
5.2.2. Hire date
5.2.3. Term date
5.2.4. Seniority date
5.2.5. Retirement date
5.2.6. Leave of absence status
5.2.7. Severance status
5.3. Contractor
5.3.1. Status
5.3.2. Hire date
5.3.3. Term date
5.4. National ID
5.4.1. Type
5.4.2. Expiration date
5.4.3. Issue authority
5.4.4. Issue date
5.4.5. Country
5.5. Work Assignment
5.5.1. Start date
5.5.2. End date
5.5.3. Homeshored
5.5.4. Primary
5.5.5. Pay frequency
5.5.6. Scheduled hours
5.5.7. FTE
5.5.8. Status
5.5.9. Pay rate
5.5.10. Rate type
5.5.11. Pay grade
5.6. Position
5.6.1. Seasonal
5.6.2. Temporary
5.6.3. Cost center
5.6.4. Scheduled hours
5.6.5. Country
5.6.6. Organizational unit
5.6.7. Status
5.6.8. Salary structure
5.7. Job
5.7.1. Code
5.7.2. Family