Before Business Rule Fundamentals
📌 A Before Business Rule triggers when a user submits a form, but before any action is taken on the record in the database (before saving/inserting/updating).
⚙️ Major use cases include aborting updates if conditions aren't met, populating assignment groups before creation, restricting record deletions, and updating dates before insert.
✍️ Before Business Rules can be implemented using configuration only or scripting for more complex logic.

Configurable (Without Scripting) Scenarios
🛑 Abort Insert Example: Users are restricted from creating new incidents if the Category is 'Inquiry/Help' AND the Assignment Group is NOT 'Service Desk'.
🔄 Update Example: Automatically changing the Incident State to 'In Progress' whenever the Work Notes field is updated.
🗑️ Abort Delete Example: Preventing the deletion of an incident record if its State is 'New', thereby protecting active records.

Scripted (With Scripting) Scenarios
🆕 Insert Scripting Example: Preventing a new incident creation if an existing incident shares the exact same Short Description AND the same Caller.
🔗 Update Scripting Example: Preventing a Story's State from changing to 'Work in Progress' unless there is at least one associated Scrum Task record linked to that Story.
🛡️ Delete Scripting Example: Preventing the deletion of a Configuration Item (CI) if there are any associated records in the Task table (such as Incidents or Changes) linked to that CI via its `cmdb_ci` field.

Before Query Business Rule
👁️ A Before Query rule executes before the system queries records, allowing for dynamic filtering of results presented to the user.
🔑 Query Scenario Example: Restricting the visibility of Configuration Item (CI) records so that only CIs with the Operational Status are queried and displayed, unless the user has the 'admin' role.

Key Points & Insights
➡️ Utilize Before Business Rules when you need to validate data, manipulate records, or stop an operation *before* it hits the database commit.
➡️ For simple validation or field setting, use configuration; for cross-record lookups or complex logic, use the advanced scripting tab.
➡️ Before Query rules, executed with `current.addQuery()`, are essential for restricting data visibility dynamically based on user roles or record states, as demonstrated by filtering CIs by Operational Status.

📸 Video summarized with SummaryTube.com on Nov 26, 2025, 20:16 UTC