Prove Compliance: Show the Logged Trail of a Transaction
When an auditor or your finance team asks "what happened to this order?", the answer is spread over several systems' logs. A Nodinite BPM puts that audit trail on one page: the steps the order went through, when each one was logged, its status, and the message itself, shown only to the people whose Role allows it.
- ✅ One search from the BPM shows every logged step of one order, with timestamps and status
- ✅ Open the logged payload and context of each step, subject to role permissions
- ✅ Decide who sees bodies and context, and record who opened what with Log Audits
- ✅ Add a new search value later and re-index the events you still retain
The Business Context
In the Order-to-Cash demo, an order passes seven steps across Sales, Planning, Logistics, and Finance, handled by a Portal, an ERP, a WMS, and ERP-Finance. The questions are business questions: did order 10010 get a confirmation, when was it invoiced, and what did we actually send?
The Problem
Without a common log, each question means asking the owners of the Portal, the ERP, and the WMS to search their own logs, match timestamps by hand, and send screenshots. It is slow and hard to repeat.
The Solution
Every step logs a Log Event to Nodinite with its timestamp, Log Status Code, and optionally the payload and context. With BPM Log Search New 7.11, you type the Order Number and the order's trail is plotted on the BPM:
The trail of one order: Order Received and Order Entry succeeded, Confirmation Sent failed at 11:38:47, and the later steps were never logged. Three events over 5 minutes 8 seconds.
From each row you open the logged message in the Log View. What a user may see is decided per Log View and Role, and access is recorded:
- Permission Set for Log Views controls per Role whether users can see the message body, the context values, or a transformed view. Stylesheets can show a business-friendly view without sensitive parts.
- Log Audits record user access to log events and message data; DaysToKeepLogAudits sets how long those records are kept.
- Search Fields decide what you can search on. If the auditor asks for a value you never indexed, an administrator adds a Search Field Expression and re-indexes the events still in the Log Databases. See Late binding and retroactive modeling.
The Results
- One search from the BPM instead of separate requests to the Portal, ERP, and WMS teams, with the same answer every time.
- Access to message content follows your Role setup, so an auditor can get read access without seeing more than you decide.
The logged trail helps you answer auditor questions; it doesn't make a process compliant on its own. How long events, payloads, and context are kept is governed by retention settings such as DaysToKeepMessageEventsDefault and DaysToKeepMessageDataDefault, so align them with your own retention policy.
How This Scenario Uses Nodinite Features
- BPM Log Search - Find one order and see its steps
- Permission Set for Log Views - Decide who sees body, context, and transformed views
- Search Fields - Make Order Number searchable, and re-index for new values
- Custom Metadata Support - Record compliance notes and the process owner on the BPM itself