Timeliness and Conformity Rules

Timeliness & Conformity 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

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!

Recent Order Activity

Scenario: Monitor that orders are being processed within expected timeframes.

Business Rule Configuration:

Rule Name: Order_Processing_Timeliness
Description: Ensures orders are shipped within 7 days of order date
Data Quality Dimension: Timeliness
Schedule: Daily
Target: Sales.SalesOrderHeader

SQL Query:

SELECT 
    COUNT(*) AS total_count,
    SUM(CASE 
        WHEN Status = 5  -- Shipped
        AND DATEDIFF(day, OrderDate, ShipDate) <= 7
        THEN 1 
        WHEN Status < 5  -- Not yet shipped
        AND DATEDIFF(day, OrderDate, GETDATE()) <= 7
        THEN 1 
        ELSE 0 
    END) AS scopeCount,
    SUM(CASE 
        WHEN Status = 5 
        AND DATEDIFF(day, OrderDate, ShipDate) > 7
        THEN 1 
        WHEN Status < 5 
        AND DATEDIFF(day, OrderDate, GETDATE()) > 7
        THEN 1 
        ELSE 0 
    END) AS nonCompliant
FROM Sales.SalesOrderHeader
WHERE OrderDate >= DATEADD(month, -1, GETDATE())  -- Last month's orders

Incomplete Product Information

Scenario: Enforce standard phone number format across all records.

Business Rule Configuration:

Rule Name: Phone_Number_Format_Conformity
Description: Validates phone numbers follow standard format pattern
Data Quality Dimension: Conformity
Schedule: Weekly
Target: Person.PersonPhone

SQL Query:

SELECT 
    COUNT(*) AS total_count,
    SUM(CASE 
        WHEN PhoneNumber LIKE '[0-9][0-9][0-9]-[0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]'
        OR PhoneNumber LIKE '([0-9][0-9][0-9]) [0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]'
        THEN 1 ELSE 0 
    END) AS scopeCount,
    SUM(CASE 
        WHEN PhoneNumber NOT LIKE '[0-9][0-9][0-9]-[0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]'
        AND PhoneNumber NOT LIKE '([0-9][0-9][0-9]) [0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]'
        THEN 1 ELSE 0 
    END) AS nonCompliant
FROM Person.PersonPhone

PreviousValidity Rules NextRule Groups

Last updated 4 months ago

Was this helpful?

Good evening

hashtagTimeliness & Conformity Rules

hashtagAccessing your Catalog

hashtagRecent Order Activity

hashtagIncomplete Product Information

Timeliness & Conformity Rules

Accessing your Catalog

Recent Order Activity

Incomplete Product Information