Holds and Blocks Framework

Regulatory authority, regulation and regulation clause, hold definition, and hold violation objects provide the framework for defining, placing, and resolving student holds. Compliance control objects support rule-based hold creation and assignment at scale.

Required Editions

Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions with Education Cloud license and Education Cloud Advanced Academic Operations for Experience Cloud add-on

Holds and Blocks start with an office or administrative body that’s responsible for defining and managing holds. Each hold has three aspects: reasons, restrictions, and resolutions. Several objects feed data into these aspects. Additional objects store the definition of each hold, create instances of a hold violation, and place a restriction on a student.

These objects support the Holds and Blocks system.

Regulatory Authority

Regulatory Authority
Represents the office or administrative body that defines regulations and manages holds in your institution, such as a department, the library, or the registrar’s office. Define regulatory authorities for your institution as needed.

Hold Definition Objects

A reason uses these objects.

Regulation
Represents the regulatory authority’s policies. Each regulation record groups regulation clause records that represent policies in the same category.
Regulation Version
Stores the effective start and end dates that represent the lifetime of a regulation. Each regulation record has related regulation version records.
Regulation Clause
Describes a specific policy for which the institution places a hold.
Regulation Clause Version
Stores the effective start and end dates that represent the lifecycle of a regulation clause. Each regulation clause record has related regulation clause version records.
Regulation Version Clause Version
A junction that connects a regulation and a regulation clause.

A restriction uses these objects.

Business Operations Process
Describes the process that’s under restriction. For example, a restriction that blocks students from course registration.
Each business operations process record needs to be mapped to a regulation clause version. A mapped regulation clause version defines the validity period of a reason-restriction pairing that applies to a hold violation.

A resolution uses these objects.

Action Plan Template
Represents a task assigned to a student to resolve a restriction.

Hold Definitions

A hold definition uses these objects.

Regulatory Code
Represents the definition of a hold. A hold definition connects regulatory authorities, regulation clauses, and action plan templates.

Hold Violations

A hold violation uses these objects.

Regulatory Code Violation
Represents an instance of a hold that's placed on a student.
Regulatory Code Violation Regulation Clause Version
A junction that connects a hold violation (regulatory code violation) to a specific rule (regulation clause version) in a hold that a student fails to meet.

Rule-based Hold Creation and Assignment

Your institution can take a rule-driven approach to enforce holds on students at scale. These objects implement policy rules that evaluate students and assign holds to them.

Compliance Control
Describes and defines a category of policy rules. Each compliance control record holds multiple compliance control version records.
Compliance Control Version
Stores a policy rule that’s based on an expression set.
Regulation Clause Compliance Control Version
A junction that connects a regulation clause version record to a compliance control version record. This connection gives the regulation clause version access to the expression set that’s used to evaluate students against specific rules in a hold.