- 7 minutes to read

End-to-End Process Tracking

See exactly where every transaction sits across your entire process—from any system, in real time

End-to-End Process Tracking is Nodinite BPM's unique capability to correlate log events across ALL systems in a business process—on-premise, cloud, custom integrations—and present them in a unified, milestone-based view. No manual log correlation. No switching between Azure Portal, BizTalk Admin, database logs, and file systems.

One business transaction. One unified view. Complete visibility.

The Problem: Fragmented Logging Across Systems

Modern business processes span dozens of systems:

  • On-Premise: SAP ERP, BizTalk Server, Oracle databases, file systems
  • Cloud: Azure Logic Apps, Salesforce, AWS Lambda, Microsoft 365
  • Custom: Web services, APIs, microservices, event streams

When troubleshooting or auditing transactions, teams face a nightmare:

❌ Manual log correlation - Search Azure Portal for Logic App logs, then BizTalk Admin for adapter logs, then SQL for database logs
❌ Hours wasted - MTTR measured in hours, not minutes
❌ Missing context - Each system logs technical details but lacks business context (Order ID, Customer ID)
❌ Compliance gaps - Reconstructing audit trails requires manual correlation across fragmented logs
❌ Knowledge silos - Only experts know where to look for specific transaction types

The Solution: Milestone-Based Logging

Nodinite BPM tracks transactions across ALL systems using milestone-based logging:

✅ Single unified view - All log events for a business transaction in one grouped Log View
✅ Business context at every step - Order ID, Invoice Number, Customer ID extracted and correlated automatically
✅ Cross-system correlation - Track transactions from on-premise ERP → cloud CRM → payment gateway → fulfillment
✅ Visual process state - See which milestone is currently executing, which completed, which failed
✅ Instant troubleshooting - Click any business identifier to see ALL related events across ALL systems
✅ Complete audit trails - Reconstruct transaction history retroactively for compliance

How It Works

1. Systems Log Events with Business Context

All integrated systems log events via Logging Agents or Log API:

{
  "timestamp": "2026-02-06T14:23:45Z",
  "messageName": "Order_Received",
  "logStatusCode": "Success",
  "orderNumber": "ORD-2026-12345",
  "customerID": "CUST-98765",
  "totalAmount": 1234.56,
  "payload": "<?xml version=\"1.0\"?>..."
}

2. Message Types Extract Business Identifiers

Message Types define transaction types and Search Field Expressions extract business data:

Message Type: Order.Received
Search Field Expression: //Order/@OrderNumber → extracts ORD-2026-12345

3. BPM Correlates Events Across Systems

When viewing a BPM in a grouped Log View:

  1. BPM defines the process - Domains, steps, services, sub-processes
  2. Log events matched to BPM steps - Based on service assignments
  3. Events grouped by business transaction - Using Search Fields (Order ID, etc.)
  4. Visual process state displayed - Color-coded by Log Status Code

Search Field Links enable instant cross-system navigation:

  1. Click Order ID ORD-2026-12345 in a failed payment step
  2. See ALL related events across:
    • CRM (order entry)
    • Credit check service
    • Payment gateway
    • Inventory allocation
    • Shipping confirmation
  3. Identify root cause in seconds instead of hours

BPM - Grouped Log View Example
BPM in a grouped Log View with milestone-based logging, showing process state and business transaction correlation

Key Capabilities

Visual Process Health with Log Status Code Colors

BPM steps automatically inherit colors from Log Status Codes:

  • 🟢 Success (Green) - Step completed successfully without errors
  • 🟡 Warning (Yellow) - Step completed but encountered warnings
  • 🔴 Error (Red) - Step failed, requires immediate attention
  • 🔵 Information (Blue) - Informational events, step in progress
  • ⚪ None (Gray) - No events logged yet for this step

Benefits

  • Business users assess process health without technical knowledge
  • Operations teams prioritize troubleshooting based on visual indicators
  • Executives gain real-time process visibility for decision-making
  • No configuration - colors update automatically as events are logged

Rapid Troubleshooting Workflow

From problem identification to root cause in seconds:

  1. Identify the problem - Red or yellow step in BPM indicates issue
  2. Click to view events - Open the Log View for that step
  3. Examine the error - Review failed event details and payload
  4. Follow Search Field Links - Click Order ID to see related events across ALL systems
  5. Trace end-to-end - Understand complete transaction flow
  6. Take action - Resolve issue with full business and technical context

Real-world results: MTTR reduced from 2 hours to 90 seconds in customer implementations.

Progressive Drill-Down with Hierarchical BPMs

New 7.3 With Hierarchical BPMs, grouped Log Views match entries from any BPM in the hierarchy:

  1. Start with master process - see all log events across sub-processes (247 events)
  2. Click sub-process cell - filter to specific sub-process events (58 events)
  3. Click nested sub-process - drill deeper for precise troubleshooting (12 events)
  4. Navigate via breadcrumbs - return to parent levels as needed

This eliminates manual correlation across fragmented process views.

Prerequisites for Correlation

Important

BPM tracking requires proper configuration:

  1. Message Types - Define business transaction types for all logging points
  2. Search Field Expressions - Configure extraction of business identifiers from message payloads
  3. Search Fields - Create Search Fields with Links enabled for cross-system navigation
  4. Log Status Codes - Set appropriate status codes (Success, Warning, Error) in logging

Without proper Message Types and Search Fields, BPM cannot correlate business transactions. Ensure logged events have:

  • Correct Message Types assigned
  • Proper Search Field Expressions configured
  • Consistent business identifiers across all steps (Order ID, Customer ID, Invoice Number, etc.)

Example: Order-to-Cash End-to-End Tracking

Business Process: Order received in CRM → Credit check → Payment authorization → Inventory allocation → Shipment dispatch

Systems Involved

  • Salesforce CRM (cloud)
  • SAP ERP (on-premise)
  • Stripe Payment Gateway (SaaS)
  • Custom Warehouse Management System (WMS)
  • UPS Shipping API (external)

Milestone-Based Logging

Milestone System Message Type Search Fields Status
Order Entry Salesforce CRM Order.Received OrderID, CustomerID 🟢 Success
Credit Check SAP ERP CreditCheck.Completed OrderID, CustomerID, CreditScore 🟢 Success
Payment Auth Stripe Payment.Authorized OrderID, TransactionID, Amount 🔴 Error
Inventory WMS Inventory.Allocated OrderID, SKU, Quantity ⚪ Pending
Shipping UPS API Shipment.Dispatched OrderID, TrackingNumber ⚪ Pending

Troubleshooting Workflow

  1. BPM shows red "Payment Auth" step - process stuck
  2. Click step - view log events for payment authorization
  3. See error: "Insufficient funds - card declined"
  4. Click OrderID ORD-2026-12345 - Search Field Link shows:
    • CRM: Order total $1,234.56
    • SAP: Credit limit $5,000 (approved)
    • Stripe: Payment attempt $1,234.56 (declined)
  5. Click CustomerID CUST-98765 - Search Field Link shows:
    • Previous orders: 12 successful payments
    • Card on file: expires 01/2026
  6. Root cause: Card expired, customer needs to update payment method

Resolution time: 90 seconds from problem identification to root cause

Best Practices

Log at Business Milestones

✅ Do log at meaningful business events:

  • Order received
  • Credit check completed
  • Payment authorized
  • Inventory allocated
  • Shipment dispatched

❌ Don't log low-level technical events:

  • Database connection opened
  • File copied to temp directory
  • HTTP request sent (unless failure)

Use Consistent Business Identifiers

Ensure all systems use the same business identifiers for correlation:

✅ Consistent: All systems log OrderID: ORD-2026-12345
❌ Inconsistent: CRM logs OrderNumber: 12345, SAP logs SalesOrder: ORD-12345

Set Meaningful Log Status Codes

Use Log Status Codes to reflect business outcome:

  • Success: Normal operation, expected result
  • Warning: Completed but with unexpected conditions (e.g., credit check borderline, retry succeeded)
  • Error: Failed, requires intervention (payment declined, inventory unavailable)

Enable Search Field Links for rapid troubleshooting:

  1. Create Search Fields for business identifiers (Order ID, Customer ID, Invoice Number)
  2. Enable "Links" checkbox on Search Fields
  3. Users can click any business identifier to see all related events across systems

Next Steps

Search Field Links – Enable instant cross-system navigation from business identifiers
Message Types – Define business transaction types for logging
Search Field Expressions – Extract business data from message payloads
What is the BPM Designer – Create visual process models

Business Process Model (BPM) – Complete BPM overview
Log Views – View and filter events for BPM steps
Log Status Codes – Status codes determine BPM step colors
Hierarchical BPMs – Progressive drill-down in nested processes
Integrated Monitoring – Monitor service health in real-time