Prescriptive Rules - Genius CE & Enterprise

In This Article:

• Overview
• How Prescriptive Rules Work
• Accessing Prescriptive Rules
• Prescriptive Rule Components
  • Basic Info
  • Schedule
  • Action Configuration
  • Filters (Conditions)
    • Filter Operators
• Running and Testing Rules
• Example Use Cases

 

Overview

Prescriptive Rules allow administrators to automate system actions when defined conditions are met.

Each rule evaluates learners against configured criteria and automatically performs an action when those conditions are satisfied.

Prescriptive rules are commonly used to automate enrollment, assign training, and manage structured learning workflows.

 

How Prescriptive Rules Work

Prescriptive Rules follow a simple automation process:

1. Define the conditions that identify learners or records
2. Configure the action that should occur when those conditions are met
3. Schedule when the rule should run

When the rule runs, the system evaluates learners against the defined conditions and executes the configured action for any matching records.

Accessing Prescriptive Rules

Navigate to: Administration → Prescriptive Rules

Prescriptive Rule Components

When creating a Prescriptive Rule, administrators configure the following sections.

Basic Info

Basic information defines the rule itself.

Fields include:

• Name – the name used to identify the rule
• Description – optional details explaining the rule's purpose

Providing clear names and descriptions helps administrators manage and understand existing rules. 
 

Schedule

The Schedule determines when the rule runs.

Available options include:

• Once – run the rule a single time
• Daily – run the rule once per day
• Weekly – run the rule once per week
• Triggered by another Prescriptive Rule – run when another rule executes

A Start Date can also be configured to control when the rule becomes active.

 

Action Configuration

The Action Configuration determines what action the rule performs when conditions are met.

Depending on the selected action type, administrators may configure additional options such as enrolling learners in:

• Sections
• Courses
• Learning Paths

Filters (Conditions)

Filters define the conditions used to identify learners or records affected by the rule.

Administrators can add filters to specify criteria such as learner status, course completion, learning path completion, or other attributes.

Multiple filters can be combined to precisely target the intended learners.

 

Filter Operators

Operators define how the system evaluates each condition.

Not in 
Returns records where the field value does not match any value in a selected list. 
Example: Status not in (Completed, Withdrawn)

Is not 
Returns records where the field value does not exactly match a specified value. 
Example: Status is not Completed

Is 
Returns records where the field value exactly matches a specified value. 
Example: Status is Completed 

Contains 
Returns records where the field value includes the specified text anywhere within it. 
Example: Course Name contains “Math”

Does not contain 
Returns records where the field value does not include the specified text. 
Example: Course Name does not contain “Test”

Starts with 
Returns records where the field value begins with the specified text. 
Example: Email starts with “admin”

Ends with 
Returns records where the field value ends with the specified text. 
Example: Email ends with “.edu”

More than 
Returns records where the field value is greater than the specified number or date. 
Example: Final Grade more than 80

Less than 
Returns records where the field value is less than the specified number or date. 
Example: Final Grade less than 50

After 
Returns records where the date value occurs after the specified date. 
Example: Enrollment Date after 01/01/2025

Before 
Returns records where the date value occurs before the specified date. 
Example: Completion Date before 12/31/2024

In 
Returns records where the field value matches any value in a selected list. 
Example: Status in (Active, Pending)

Running and Testing Rules

From the Prescriptive Rules list, administrators can:

• Manually run a rule to immediately evaluate its conditions
• Use the Affected Learners option to preview which learners will be impacted

These tools help verify rule behavior before applying automation.

Example Use Cases

See the following articles for examples of how prescriptive rules can be used:

• Automating Course Enrollment After Learning Path Completion