Version: Current

Understanding Validation Rules and Levels

Zudello employs a validation framework to check document data against predefined rules, ensuring data integrity, compliance, and successful integration with external systems like ERPs.

What are Validation Rules?

These are automated checks performed on document data. They can verify things like:

Completeness: Are mandatory fields filled? (e.g., Supplier linked, notes added, user assigned).
Accuracy: Do totals balance? Does the tax calculation seem correct? Is the ABN valid? Do bank details match stored records?
Compliance: Does the data adhere to business policies? (e.g., Item price within limits, using existing contacts/items).

How are Rules Configured?

Validation rules are primarily configured via:

Extensions: Pre-built validation logic enabled on specific Document Types (e.g., Validate purchase total, Check Contact ABN, Validate document notes). Administrators turn these ON/OFF and sometimes configure thresholds.
Form Settings: Marking fields as Required on a Document Type form creates a basic completeness validation.
Automation Sentences (Less Common for Feedback): While Sentences can check conditions and set statuses, they are less commonly used for displaying granular validation feedback directly to the user compared to Extensions.

Validation Levels (Severity):

When a validation rule runs and detects an issue (or confirms success), the result is assigned a severity level:

Error (Red):
- Meaning: A critical issue that violates a fundamental rule or prevents downstream processing (like ERP integration).
- Impact: Blocks key actions like Save and Submit or Approve. The error must be fixed.
Warning (Yellow/Orange):
- Meaning: A potential issue, inconsistency, or deviation from policy that requires review but doesn't necessarily prevent processing.
- Impact: Does not block actions, but alerts users and approvers.
Info (Blue/Grey):
- Meaning: Provides informational feedback (e.g., confirmation of a successful check).
- Impact: None; purely informational.

Overall Document Validation Level:

A document has an overall validation_level field which reflects the highest severity issue currently present (Error > Warning > Info). This overall level can be used in Sentence conditions to route documents (e.g., "If Validation Level Is Error Then Set Status User Review").

Understanding these rules and levels helps users identify and resolve issues efficiently, ensuring data quality and smooth workflow progression.