- 3 minutes to read

O2C Demo Stylesheets

Transform raw Order-to-Cash messages into formatted, business-friendly reports that operators can understand instantly. Nodinite Stylesheets render complex payloads as readable tables—no external tools required.

On this page, you will:

  • ✅ Understand what Stylesheets do and why they matter
  • ✅ Access pre-built stylesheets for all 7 O2C steps
  • ✅ Learn the critical configuration needed to display data correctly

What Are Stylesheets?

A Stylesheet is a template that transforms raw message data into readable, formatted views. Instead of showing base64-encoded JSON or raw XML, Stylesheets present business data—customer names, order IDs, amounts, statuses—in clean, organized tables.

graph LR A[Raw Message Data] --> B{Stylesheet
Template} B --> C[Formatted Display] style A fill:#2678BD style B fill:#FFD525 style C fill:#93d16d

Diagram: Stylesheet transformation flow showing how raw message data is processed through a Liquid template to produce a business-friendly formatted display.

Why use Stylesheets?

  • Data Security: Mask sensitive information while displaying business context
  • User-Friendly Displays: Turn technical formats into readable, actionable reports
  • Consistency: Apply the same formatting across all related messages
  • Compliance: Protect sensitive data while maintaining auditability

Available Stylesheets

The O2C demo includes pre-built stylesheets for each of the 7 order lifecycle steps:

Step Format Stylesheet Purpose
1 JSON Order Received Customer name, Order ID, Amount
2 XML In Development ERP Reference, Entry time, Status
3 CSV In Development Confirmation number, Customer email
4 JSON In Development Schedule date, Production line, SKU
5 XML In Development Tracking number, Warehouse location
6 PSV In Development Delivery date, Carrier, Proof of delivery
7 JSON In Development Invoice number, Total amount, Due date

Each stylesheet extracts business data from its message format and displays it in a consistent, readable table layout.

⚠️ Critical: "Message Body is Json" Configuration

When using JSON stylesheets, you MUST configure the "Message Body is Json" setting on the Stylesheet (not on the Log View). This checkbox controls how data is accessed:

☑️ CHECKED — Nodinite parses JSON and injects properties as direct variables. Use simple syntax: {{ orderId }}, {{ customer.name }}

☐ UNCHECKED — Raw message body available as string. Requires JavaScript parsing.

Important

All JSON stylesheets in this demo require "Message Body is Json" to be CHECKED. XML/CSV/PSV messages require it UNCHECKED. Without the correct setting, stylesheets will show placeholder values instead of actual data.

How to Use

  1. Add a Stylesheet and paste the template for the message step
  2. Configure the Stylesheet:
    • JSON messages → ✅ CHECK "Message Body is Json"
    • XML/CSV/PSV messages → ☐ UNCHECK "Message Body is Json"
  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

For complete guidance on creating and managing stylesheets, see Stylesheets Overview in the main Customize section.

Next Steps