How does BPM correlate events across different systems?

Nodinite uses Search Fields to correlate events across all systems. This page explains:

• Architecture showing cross-system correlation flow
• Comparison matrix of correlation methods and use cases
• How payload extraction works with different formats (XML, JSON, CSV)
• Real-world multi-system scenario with detailed examples
• ⚠️ What happens without proper correlation configuration

Extract business identifiers (Order ID, Invoice Number, Customer ID) from message payloads—BPM correlates transactions across CRM, ERP, payment gateways, warehouses, and shipping systems regardless of technology differences.

Quick Answer

Nodinite extracts business identifiers from message payloads using Search Field Expressions. When each system logs an event, these expressions extract the same business identifier (Order ID, Invoice Number, Customer ID) from different payload formats. BPM uses these extracted values to group and track related events across all systems—showing complete cross-system transaction flows.

Cross-System Correlation Architecture

Each system uses different formats—Search Fields extract the same business identifiers for correlation.

Each system uses different formats—Search Fields extract the same business identifiers for correlation.

Correlation Methods Comparison

How Payload Extraction Works

XML Message Example

CRM System logs Order Created:

<Order>
    <OrderID>12345</OrderID>
    <CustomerID>CUST-789</CustomerID>
    <InvoiceNumber>INV-2025-001</InvoiceNumber>
</Order>

Search Field Expressions:

• Order ID: XPath: //OrderID/text() → Extracts 12345
• Customer ID: XPath: //CustomerID/text() → Extracts CUST-789
• Invoice Number: XPath: //InvoiceNumber/text() → Extracts INV-2025-001

JSON Message Example

Payment Gateway logs Payment Processed:

{
    "transaction": {
        "orderId": "12345",
        "customerId": "CUST-789",
        "amount": 549.99,
        "status": "approved"
    }
}

Search Field Expressions:

• Order ID: JSONPath: $.transaction.orderId → Extracts 12345
• Customer ID: JSONPath: $.transaction.customerId → Extracts CUST-789

CSV File Example

Shipping System drops fulfillment file:

CustomerID,OrderID,TrackingNumber,Status
CUST-789,12345,1Z999AA10123456784,Shipped

Search Field Expressions:

• Order ID: CSV Column 2 → Extracts 12345
• Customer ID: CSV Column 1 → Extracts CUST-789
• Tracking Number: CSV Column 3 → Extracts 1Z999AA10123456784

Real-World Multi-System Scenario

E-Commerce Order-to-Cash Process

Business Context: Customer places order → payment processed → ERP invoice → warehouse fulfillment → shipping notification.

Systems involved: 5 different platforms, 3 different message formats.

Step-by-Step Correlation

1. Salesforce CRM - Order Created

• Message Format: REST API JSON
• Search Field Extraction: $.order.id → Order ID: 12345, $.customer.id → Customer ID: CUST-789
• BPM Step: "Order Entry" domain "Sales"

2. Stripe Payment Gateway - Payment Approved

• Message Format: Webhook JSON
• Search Field Extraction: $.data.object.metadata.order_id → Order ID: 12345
• BPM Step: "Payment Processing" domain "Finance"
• Correlation: Matches Order ID 12345 from CRM → Shows as same transaction

3. SAP ERP - Invoice Generated

• Message Format: SOAP XML
• Search Field Extraction: XPath //Order/OrderNumber → Order ID: 12345, XPath //Invoice/InvoiceNumber → Invoice: INV-2025-001
• BPM Step: "Invoicing" domain "Finance"
• Correlation: Matches Order ID 12345 → Adds Invoice ID INV-2025-001 to transaction

4. WMS (Warehouse) - Pick List Created

• Message Format: MSMQ XML
• Search Field Extraction: XPath //OrderRef → Order ID: 12345
• BPM Step: "Picking" domain "Warehouse"
• Correlation: Matches Order ID 12345 → Shows warehouse received order

5. FedEx Shipping - Shipment Dispatched

• Message Format: CSV File
• Search Field Extraction: CSV Column 2 → Order ID: 12345, CSV Column 3 → Tracking: 1Z999AA10123456784
• BPM Step: "Shipping" domain "Warehouse"
• Correlation: Matches Order ID 12345 → Adds tracking number, completes transaction

BPM Visualization Result

Single correlated view shows:

Click any Search Field Link (Order ID 12345) → See ALL 5 events across all systems instantly.

Time saved: Traditional approach requires logging into 5 different systems and manually correlating timestamps. With Nodinite BPM: instant cross-system visibility.

What Happens Without Proper Correlation

Symptom: BPM shows fragmented, incomplete transactions—each event appears as separate unrelated instance.

Root causes:

Configuration Steps

To enable cross-system correlation:

1. Define Message Types - Teach Nodinite to recognize each message format (CRM order XML, payment gateway JSON, etc.)
2. Create Search Fields - Define business identifiers (Order ID, Customer ID, Invoice Number)
3. Add Search Field Expressions - Configure XPath/JSONPath/Regex to extract IDs from each Message Type
4. Test extraction - Send sample messages, verify Search Fields populate correctly
5. Configure BPM - Use Search Fields for correlation in BPM definition
6. Validate - Trigger real transaction, verify all systems appear in single BPM instance

Next Step

Ready to configure cross-system correlation? Learn how to Add or manage BPM with Search Field correlation, or explore Search Field Expressions for advanced extraction logic.

Related Topics

• Business Process Model (BPM) - Main BPM overview
• Search Fields - Business data extraction for correlation
• Search Field Expressions - Configure extraction logic (XPath, JSONPath, Regex)
• Message Types - Define transaction message formats
• Search Field Links - Enable rapid cross-system troubleshooting
• Troubleshoot-in-Minutes Scenario - See correlation in action
• All FAQs - See all BPM FAQs