- 4 minutes to read

3. Order Confirmation Delivered to Customer

This demonstration shows how Nodinite Log Events track order confirmations in a flat-file (CSV) format as they return from ERP processing to the customer-facing Portal. This step shows how cross-domain message flows keep correlation across Systems and message formats.

Step 3 occurs when the Portal has generated an order confirmation and delivered it to the customer. The customer receives acknowledgment that the order was accepted and is being processed.

Confirmation Sent step of order ORD-10005 in BPM Log Search: Show Details on its event, then Context Values with the file name, order number, customer, amount, and Repository Binding, animated walkthrough (7.12)
Animated walkthrough: in BPM Log Search, open Show Details on the Order Confirmation Delivered to Customer event of order ORD-10005 (Tailspin Toys), then the Context Values tab with the step's business data. The walkthrough shows ORD-10005; the examples below use order 1.

Understanding Step 3

graph LR ERP["fa:fa-server ERP System"] Portal["fa:fa-window-restore Portal System"] Customer["fa:fa-user Customer"] LogAPI["fa:fa-database Nodinite Log API"] ERP -->|"CSV Confirmation
O2C.Order.Confirmation/1.0"| Portal Portal -->|"Send Confirmation"| Customer Portal -->|"Log Event
Sales Domain"| LogAPI style Portal fill:#2678BD style Customer fill:#93d16d style LogAPI fill:#FFD525

Order confirmation flow: the ERP generates the CSV message, the Portal (blue) delivers it to the customer (green), and the Log API (yellow) captures the Log Event in the Sales domain with cross-domain correlation.

Message Details

  • Message Type: O2C.Order.Confirmation/1.0 (Message Types)
  • Domain: Sales (Domains)
  • System: Portal (Systems)
  • Service: INT1337-SND-Confirm-Outgoing (Services)
  • Direction: Send (outgoing to the customer)
  • Format: Flat File (CSV)
  • Log Status: 0 (Success); -1337 on the Send event when the order stops at this step
  • Timing: In the generated data, 30-300 seconds after Step 2

Log Events in This Step

Step 3 logs two Log Events with the same Body. Only the business event appears in the BPM.

SequenceNo (sent) Service Direction EndPointName Message Type LogText In BPM
5 INT1337-RCV-Confirm-Incoming Receive Portal-Confirmation-Receive O2C.Forwarding/1.0 Confirmation Received ❌ No
6 INT1337-SND-Confirm-Outgoing Send Portal-Confirmation-Send O2C.Order.Confirmation/1.0 Order Confirmation Delivered to Customer ✅ Yes

The demo sends SequenceNo 1 to 14 per order. Nodinite keeps that value as the event's ServiceInstanceSequenceNo and gives the event its own SequenceNo, a running number in the Log Database.

Business Data (Happy Path)

The data of the order from Step 1, here order 1. Other orders carry their own customer, product, quantity, and total, the same in every step (see Generate O2C Demo Data):

  • Order ID: ORD-10001 (same as source order)
  • Customer ID: CUST-001
  • Product SKU: SKU-DEMO-001
  • Quantity: 1
  • Order Total: USD 99.95

Sample CSV Message

This is the raw message payload that the Log Event carries base64-encoded in its Body field. This simplified CSV format contains the essential order confirmation data.

OrderConfirmationHeader
ConfirmationId,ConfirmationDate,CorrelationId,OrderId,OrderDate,CustomerID,CustomerName,CustomerEmail,ConfirmationStatus
CONF-2025-10001,2025-10-14T09:22:15Z,{PREFIX}-{DATEPART}-{HHMM}-{SEQUENCE},ORD-10001,2025-10-14T09:15:00Z,CUST-001,Contoso Corporation,orders@Contoso.example.com,CONFIRMED

OrderConfirmationDetails
LineNumber,SKU,Description,QuantityOrdered,UnitPrice,LineTotal
1,SKU-DEMO-001,Demo Widget,1,99.95,99.95

OrderConfirmationFooter
OrderTotal,Currency,EstimatedShipDate,TrackingEnabled
99.95,USD,2025-10-21,true

Nodinite Log Event (JSON formatted)

This step creates a Log Event that the demo sends to the Nodinite Log API. See Log Event Reference for the O2C Log Event structure, and JSON formatted Log Event for every field.

Context Properties (Business Data)

The Context Options carry the business data and the Repository Binding:

{
  "FileName": "ORD-10001-order-confirmation-delivered-to-customer.csv",
  "OrderNumber": "ORD-10001",
  "CustomerId": "CUST-001",
  "CustomerName": "Contoso Corporation",
  "OrderAmount": "99.95",
  "ExtendedProperties/1.0#RepositoryBinding": "..."
}

The confirmation id (CONF-2025-10001) and the estimated ship date stay in the message body, not in the Context.

View the Message in Nodinite

With the demo Stylesheet installed, users read this CSV message as an order confirmation. In the BPM Viewer, or a Log View, open Action on the Order Confirmation Delivered to Customer event and choose View message formatted as 'O2C - View Order Confirmation'.

Order Confirmation CONF-2025-10005 rendered by the O2C - View Order Confirmation Stylesheet (7.12)
The message rendered by the Liquid Stylesheet: confirmation number, customer with e-mail, the confirmed lines, the total, and the estimated ship date.

Key Points for Step 3

  • CSV Format: Demonstrates flat-file format support (vs JSON and XML in earlier steps)
  • Sales Domain Transition Back: Returns to the Sales domain (Index 0, Step 2) after ERP processing
  • Send Direction: Data flows outward to the customer (EndPointDirection: 1)
  • Correlation from Step 2: Uses the same Correlation ID to link back to prior steps
  • Cross-Domain Flow: Shows the order returning to the Portal after ERP processing completes
  • CSV Structure: A multi-section format (Header, Details, Footer) demonstrates flat-file complexity

Next Steps