Troubleshoot a Failed Order from the BPM
A customer asks where their order is. With a Nodinite BPM, you answer from one page: search the order, see the step where it stopped, open the event that failed, and jump to the order in the business system.
- ✅ Search by the value you know, such as the Order Number, straight from the BPM
- ✅ The failed step is red on the drawing, so you know where to look before you read a single log line
- ✅ Open the failed event and read the logged message, as your role allows
- ✅ One click from the event to the order in your ERP or portal with a Search Field Link
The Business Context
In the Order-to-Cash demo, an order passes a Portal, an ERP, a warehouse system, and ERP-Finance in seven steps, each logging its own events in JSON, XML, or flat-file format.
The Problem
Without a common view, finding out what happened to one order means opening the Portal's log, then the ERP's, then the warehouse's, matching timestamps and IDs by hand, and often asking the one developer who knows which system comes next. Support waits, and so does the customer.
The Solution
Step 1: Search the Order from the BPM
From the BPM Overview, click Log Search on the Order-to-Cash BPM, keep the Order 2 Cash Log View, and type the Order Number. BPM Log Search New 7.11 finds the order's events, grouped by the Application interchange id they all carry, and plots them on the BPM.
Order PIC-20261009-1644-0010: three events in 5m 8s. Order Received and Order Entry succeeded, Confirmation Sent failed, and the later steps have no events yet.
If more than one order matches, the result says how many groups were found and you pick one.
Step 2: Open the Failed Event
The red row is the Confirmation Sent event. Open it to see what was logged: the payload and the context properties, if your Role may see them. A Stylesheet can render the payload in a business-friendly form, so a support agent reads an order confirmation rather than raw XML. Open Action on the event and choose the Stylesheet view, shown here for the Order Received event of another order:
Action offers View details, View message body, the Stylesheet view, Resend, and Download.
The logged message as a business document: order, customer, amount, and order lines.
Step 3: Jump to the Order in the Business System
The Order Number on the event is a Search Field value. When an administrator adds a Search Field Link to it, the value becomes a link: one click opens the order in the ERP or the Portal, with the Order Number filled in.
Expand the event, and the order number opens the order in the ERP.
Step 4: Check the System Behind the Step
If a system behind the step is down, the lightbulb on its Service shows it; see Monitor and act.
The Results
The investigation that used to cross several system logs becomes one search from the BPM, followed by a click on the red step and, when needed, a click into the ERP. Support staff can follow an order themselves instead of escalating every question to a developer.
It also works after the fact. If you later need to search on another value, such as a customer number, an administrator adds a Search Field and re-indexes the events you already logged; nothing has to be logged again.
from the BPM] --> B[fa:fa-circle-xmark Red step
Confirmation Sent] B --> C[fa:fa-file-lines Failed event
payload and context] C --> D[fa:fa-arrow-up-right-from-square Search Field Link
order in ERP or Portal] style A fill:#2678BD style B fill:#c33d34 style C fill:#E47528 style D fill:#93d16d
Blue: start from the BPM. Red: the failed step. Orange: the logged evidence. Green: the business record, one click away.
How This Scenario Uses Nodinite Features
- BPM Log Search New 7.11 - search one order and plot it on the BPM
- Search Fields and Search Field Expressions - make the Order Number searchable in every message format
- Log Views - group the order's events and control who sees which payloads
- Log Status Codes - color each step by its logged outcome
- Search Field Links - turn the Order Number into a link to the order in another system