Glossary & Index
This section provides definitions of key terms and concepts used throughout this manual.
28.1 Key Terms
Action: An operation executed when a Business Rule condition evaluates to TRUE. QUALIA Rule Engine supports 11 action types including Error, Message, Confirmation, Email, Assign, and others.
Action Type: The specific kind of action (Error=1, Message=2, Confirmation=3, etc.). Determines what the rule does when triggered.
Aggregate Function: A function that calculates across multiple records in a Linked Table (MIN, MAX, SUM, FIR, LAS).
Business Rule: A validation or automation defined in QUALIA Rule Engine consisting of Scenarios (optional), Conditions, and Actions.
Business Rule Set (Validation Set): A collection of related Business Rules that execute on a specific trigger table and trigger type.
Condition: A formula that evaluates to TRUE or FALSE. When TRUE, the condition's actions execute.
Field Placeholder: A reference to a field value using [TableID:FieldID] syntax.
Linked Table (Source Reference): A related table configured to provide data from a different table than the trigger table. Enables accessing related records in formulas.
Placeholder: A dynamic value reference in formulas, such as [18:2] for Customer.No. or [TODAY] for the current date.
Quick Rule: A simplified interface for creating basic validation rules without full configuration complexity. Accessed from the Quick Rule Card page (72777815).
Reference Filter: A relationship definition that connects a Linked Table to the trigger table (for example, Sales Line.Document No. = Sales Header.No.).
Rule Group: A collection of users to whom specific Business Rule Sets apply. Enables department-specific or role-based rules.
Scenario: An inclusion filter written in Business Central filter syntax that defines which records to process. When ALL scenario filters MATCH the current record, processing continues to conditions. When ANY scenario filter does NOT match, processing stops immediately.
Counter-intuitive behavior: The underlying CheckConditions function returns FALSE when filters match (continue processing) and TRUE when filters don't match (stop processing). Users should focus on writing filters that MATCH the records they want to process, not on the TRUE/FALSE return values.
Used for performance optimization by filtering out irrelevant records before expensive condition evaluation.
System Placeholder: A special placeholder for system values like [TODAY], [USERID], or [COMPANYNAME].
Trigger Field: The specific field that triggers rule evaluation when changed. [TableID:0] means any field change triggers the rule.
Trigger Table: The Business Central table where database operations (Insert/Modify/Delete) trigger rule evaluation.
Trigger Type: The database operation type that triggers rules (BeforeInsert=1, BeforeModify=2, BeforeDelete=3).
Validation Log: A table that records all Business Rule executions, including timestamp, user, rule executed, and result. Essential for troubleshooting and auditing.
Validation Set: Synonym for Business Rule Set. The term used in the UI for a collection of related rules.
28.2 Acronyms
BC: Microsoft Dynamics 365 Business Central
LCY: Local Currency
QUA: QUALIA prefix used in all QUALIA Rule Engine object names
UI: User Interface
28.3 Alphabetical Index
A
Actions (Section 2.7, Sections 7-16)
Action Execution Order (Section 17)
Action Types Reference (Sections 7-16)
Advanced Formula Building (Section 19)
Aggregate Functions (Section 19.3, Section 25.7)
Assign Actions (Section 13)
B
Best Practices (Section 21)
Business Rule Card (Section 2.5)
Business Rules Setup (Section 3)
C
Calculations in Formulas (Section 19.4, Section 25.6)
Comparison Operators (Section 25.4, Section 27.1)
Conditions (Section 2.6, Section 4.5)
Confirmation Actions (Section 9)
Core Concepts (Section 4)
Credit Limit Validation Example (Section 5, Section 7.7)
Custom Actions (Section 15)
D
Date Arithmetic (Section 19.5, Section 25.3)
Deployment (Section 23)
Discount Validation Example (Section 8.6)
E
Email Actions (Section 11)
Enable Controls (Section 3.3)
Error Actions (Section 8)
F
Field Placeholders (Section 4.6, Section 25.2)
Formula Building (Section 19)
Formula Operators (Section 27)
G
Getting Started (Section 2)
Glossary (Section 28)
I
Insert Record Actions (Section 14)
Introduction (Section 1)
L
Linked Tables (Section 18)
M
Maintenance (Section 24)
Mathematical Operators (Section 25.6, Section 27.5)
Message Actions (Section 7)
Monitoring (Section 24)
N
Notification Actions (Section 10)
O
Operators Reference (Section 27)
P
Performance Optimization (Section 21.2)
Placeholders (Section 4.6, Section 25)
Power Automate Actions (Section 16)
Q
Quick Rule Card (Section 2.5)
QUALIA Rule Engine Overview (Section 1)
R
Reference Filters (Section 18.4)
Rule Groups (Section 20)
S
Scenarios (Section 2.6, Section 4.4)
Source References (see Linked Tables, Section 18)
System Placeholders (Section 25.3)
T
Table & Field Reference (Section 26)
Testing Framework (Section 6)
Trigger Fields (Section 3.4, Section 4.3)
Trigger Tables (Section 3.2, Section 4.3)
Trigger Types (Section 3.3, Section 4.3)
Troubleshooting (Section 22)
Tutorial (Section 5)
U
URL Actions (Section 12)
User Assignment (Section 20)
V
Validation Log (Section 6.4)
Validation Sets (see Business Rule Sets, Section 2.4, Section 3)
W
Wildcards (Section 25.5, Section 27.3)
Document Information
Document Title: QUALIA Rule Engine User Manual
Version: 1.1.0.4
Copyright: © 2025 QUALIA Technik GmbH. All rights reserved.
Product: QUALIA Rule Engine for Microsoft Dynamics 365 Business Central
Platform Requirements: Microsoft Dynamics 365 Business Central version 22.0 or later
Last Updated: 2025
Disclaimer: This documentation is provided "as is" without warranty of any kind. QUALIA Technik GmbH shall not be liable for any damages arising from the use of this documentation or the QUALIA Rule Engine product.
Contact Information:
Support Email: info@qualiatechnik.de
Website: www.qualiatechnik.de
END OF USER MANUAL
0 Code Business Rules
>
What is Business Rules Management and Why Your Business Needs It
>
QUALIA Rule Engine: The Complete Introduction for Business Central Users
>
Business Rules vs. Custom Code: Which Approach is Right for You?
>
Understanding Trigger Events: How Business Rules Know When to Execute
>
Scenarios vs. Conditions: Mastering the Two-Tier Validation Model
>
The Complete Guide to Placeholders in Business Rules
>
Understanding Rule Sets and Rule Organization
>
Glossary & Index
>
5 Signs Your Business Central Environment Needs a Rules Engine
>
Understanding the Business Rules Lifecycle: From Design to Deployment
Related Posts
Glossary & Index
This section provides definitions of key terms and concepts used throughout this manual.
Understanding Rule Sets and Rule Organization
Imagine opening a filing cabinet where documents are thrown in randomly—no folders, no labels, no organization. Finding what you need would be frustrating and time-consuming. Now imagine that same cabinet with clearly labeled folders, logical groupings, and a sensible structure. The difference is dramatic.
The Complete Guide to Placeholders in Business Rules
Imagine showing a user an error message that says: "Value exceeds limit." While technically informative, it leaves users asking critical questions: Which value? What limit? By how much? What should I do? Now imagine showing: "Credit limit exceeded. Customer ACME Corp has credit limit $50,000 but current balance $45,000 plus this order $10,000 would total $55,000, exceeding the limit by $5,000. Please reduce order amount, collect payment, or request credit limit increase."
