- 5 minutes to read

O2C Demo Stylesheets

Read every message of an order as a business document. The Order-to-Cash demo logs seven messages per order in four formats, and Nodinite Stylesheets render each of them as an order, a schedule, a packing slip, a delivery note, or an invoice, with no external tools.

BPM Log Search of the Order-to-Cash BPM: one order opened step by step, Order Received as an Order Report, Order Entry as an ERP document, and Order Delivered as a delivery note, animated walkthrough (7.12)
Animated walkthrough: one order in BPM Log Search, read through three Stylesheets: JSON (Step 1), XML (Step 2), and pipe-separated (Step 6). The walkthrough shows order ORD-10002; the step pages show ORD-10005.

On this page, you will:

  • ✅ Find the Stylesheet for each of the seven O2C steps
  • ✅ See which engine renders which format: Liquid for JSON, CSV, and PSV, XSLT for XML
  • ✅ Set Message Body is Json right for each format

What Are Stylesheets?

A Stylesheet is a template that transforms raw message data into a readable view. Instead of showing raw JSON, XML, or delimited text, a Stylesheet presents the business data (customer names, order IDs, amounts, statuses) as a document. Each Stylesheet is tied to one or more Message Types; Nodinite offers it in the Action menu of every Log Event with a matching Message Type.

graph LR A["fa:fa-file-code Raw message
JSON, XML, CSV, PSV"] --> B{"fa:fa-tags Message Type"} B --> C["fa:fa-palette Stylesheet
Liquid or XSLT"] C --> D["fa:fa-file-alt Business document"] style A fill:#2678BD style B fill:#9E59BB style C fill:#FFD525 style D fill:#93d16d

The raw message (blue) is matched to its Message Type (purple); the Liquid or XSLT Stylesheet (yellow) renders a business document (green).

Why Use Stylesheets

  • User-friendly displays: turn technical formats into readable documents that business users understand
  • Data protection: show the business context without the fields a user shouldn't see
  • Consistency: render every message of a Message Type the same way

Available Stylesheets

The demo has one Stylesheet per step. Each is bound only to the Message Type of its step's business event, the event the BPM shows. The step numbers are the ones the BPM shows (Step 1 to Step 7).

Step Format Engine Stylesheet Message Type Renders
1 JSON Liquid O2C - View Order O2C.Order.Received/1.0 Order Report: customer, ship-to, order lines, total
2 XML XSLT O2C - View Order Entry O2C.Order.Entry/1.0 ERP reference, dates, status, lines with reservation
3 CSV Liquid O2C - View Order Confirmation O2C.Order.Confirmation/1.0 Confirmation number, customer and e-mail, lines, ship date
4 JSON Liquid O2C - View Order Planned O2C.Order.Scheduled/1.0 Schedule, priority, production lines, materials
5 XML XSLT O2C - View Order Ready O2C.Order.Ready/1.0 Packing slip: warehouse, ship-to, carrier, tracking, items
6 PSV Liquid O2C - View Order Shipped O2C.Order.Delivered/1.0 Delivery note with proof of delivery
7 JSON Liquid O2C - View Order Invoice O2C.Order.Invoice/1.0 Invoice: bill-to, terms, lines with tax, totals

Every Stylesheet is active and has Render as HTML checked. The forwarding events of the steps log O2C.Forwarding/1.0; of the demo Stylesheets, only O2C - View Order is also bound to it, because the forwarding event of Step 1 (Order Forwarded to ERP) carries the same JSON. On the forwarding events of the other steps it renders an empty Order Report.

Choosing the Engine and Message Body is Json

Body Engine Message Body is Json How the template reads the body
JSON Liquid ✅ Checked Nodinite parses the JSON; every property is a Liquid variable ({{ orderId }}, {{ customer.name }})
XML XSLT Not shown XSLT reads the XML directly; the checkbox only appears for Liquid
CSV, PSV Liquid ☐ Unchecked (no effect) The whole body is one string in data; the template splits it with Liquid filters

Important

Check Message Body is Json for JSON bodies. With it unchecked, a JSON template still renders, but every field is empty. For XML, CSV, and PSV it has no effect; leave it unchecked.

Message Body is Json is a setting on the Stylesheet, not on the Log View. When it is unchecked, or the body isn't JSON, the raw body is in the Liquid variable data, and Liquid filters handle it: the CSV and PSV templates split data into lines and fields with newline_to_br, split, and strip. A quoted field that contains the separator is split too, since Liquid has no CSV parser.

The JSON parser normalizes dates and numbers before Liquid sees them (2025-10-16T14:30:00Z shows as 2025-10-16 14:30:00, 1245.0 as 1245). XML, CSV, and PSV values show exactly as the message holds them.

How to Use

  1. Add a Stylesheet and paste the template from the step's page.
  2. Set Type and Message Body is Json as in the table above, and check Render as HTML.
  3. Associate the Stylesheet with the step's Message Type.
  4. Open a matching event from a Log View or from BPM Log Search New 7.11, choose Action, and pick View message formatted as the Stylesheet. The dialog View message body formatted as '…' has the buttons Open in New Window, Print, and Close.

For complete guidance on creating and managing Stylesheets, see What is a Stylesheet? in the Customize section.

Next Steps