Accuracy Rules

In this series of detailed workshops we're going to:

Understand the business value and ROI of implementing business rules
Master the 7 Data Quality Dimensions in PDC
Create and configure business rules with detailed step-by-step guidance
Implement rule actions (Status, Tags, Webhooks) and understand their purpose
Organize rules using rule groups for operational efficiency
Monitor and interpret rule execution results for continuous improvement

Accuracy rules verify that data correctly represents reality. This is different from completeness (data exists) or validity (data follows format rules). Accuracy asks: "Is this information TRUE?"

Accessing your Catalog

To get started using the Data Catalog, log in using the address and credentials provided by your Data Catalog service user or administrator.

To access your catalog, please follow these steps:

Open Google Chrome web browser.
Navigate to:

https://pdc.pentaho.labpdc.pentaho.lab

Enter following email and password, then click Sign In.

Username: [email protected] (mapped to Business Steward role)

Password: Welcome123!

Valid Email Addresses

Scenario: Email addresses must follow standard format patterns.

Business Rule Configuration:

Rule Name: Email_Format_Accuracy
Description: Validates email addresses follow RFC-compliant format
Data Quality Dimension: Accuracy
Schedule: Daily
Target: Person.EmailAddress

SQL Query:

SELECT 
    COUNT(*) AS total_count,
    SUM(CASE 
        WHEN EmailAddress LIKE '%_@__%.__%' 
        AND EmailAddress NOT LIKE '%[^a-zA-Z0-9.@_-]%'
        THEN 1 ELSE 0 
    END) AS scopeCount,
    SUM(CASE 
        WHEN EmailAddress NOT LIKE '%_@__%.__%' 
        OR EmailAddress LIKE '%[^a-zA-Z0-9.@_-]%'
        THEN 1 ELSE 0 
    END) AS nonCompliant
FROM Person.EmailAddress

Incomplete Product Information

Scenario: Verify that order SubTotal matches sum of line items.

Business Rule Configuration:

Rule Name: Order_SubTotal_Calculation_Accuracy
Description: Validates SubTotal equals sum of all order line items
Data Quality Dimension: Accuracy
Schedule: Daily
Target: Sales.SalesOrderHeader

SQL Query:

SELECT 
    COUNT(*) AS total_count,
    SUM(CASE 
        WHEN ABS(h.SubTotal - COALESCE(d.LineTotal, 0)) < 0.01 
        THEN 1 ELSE 0 
    END) AS scopeCount,
    SUM(CASE 
        WHEN ABS(h.SubTotal - COALESCE(d.LineTotal, 0)) >= 0.01 
        THEN 1 ELSE 0 
    END) AS nonCompliant
FROM Sales.SalesOrderHeader h
LEFT JOIN (
    SELECT SalesOrderID, SUM(LineTotal) AS LineTotal
    FROM Sales.SalesOrderDetail
    GROUP BY SalesOrderID
) d ON h.SalesOrderID = d.SalesOrderID
WHERE h.OnlineOrderFlag = 1

Hands-On Task:

Create this rule in PDC
Run the rule immediately
Review results on the History tab
Identify which product categories have the most incomplete data

PreviousCompleteness Rule NextUniqueness Rules

Last updated 2 months ago

Was this helpful?