Blotters and order actions

Use Blotter In to inspect messages received from the initiator and the session's orders. Use Blotter Out to inspect messages sent by the simulator. Both feeds update live.

Inspect traffic

Each blotter reports message type, message name, UTC time, and sender. Open a row to decode the raw FIX fields. The filter bar narrows the displayed messages by message type, UTC date range, or text in the raw FIX message or message name. The applied-filter row lets you remove one filter or clear all filters.

Use Show to choose 25, 50, 100, or 200 displayed messages. The count below the table distinguishes the displayed messages from all messages matching the current filter.

Work with orders

Blotter In separates working orders from completed orders. Expand a working order to inspect its executions. Right-click a working-order row, or use the keyboard context-menu key, to open its available actions.

The menu enables actions only when the current state permits them. Depending on the order and workspace, it can offer Cancel order, Amend, Force fill, Bust fill, Correct fill, Mark Done-for-Day, Reject, Expire, or Reactivate order. FX orders use the FX dealing ticket for quoting, execution, and allocation. A disabled entry's tooltip states the state or feature restriction.

Reactivate order applies only to a terminal order that was not filled, and only when Allow order reactivation is on in Global Settings. Completed orders are read-only in Blotter In, so the entry appears in a working order's menu and is disabled there.

Use Cancel all or Cancel by symbol only after confirming the affected working orders. Delete all orders clears the blotter without sending messages to the counterparty.

Bulk actions and decisions

Select working orders to apply a shared bulk action. The available bulk actions are limited to the actions enabled for every selected order. Cancel, Reject, Expire, and Mark Done-for-Day are the bulk actions (Reactivate is also listed but never enabled for a working order, as described above); Amend, Force fill, Bust fill, and Correct fill remain per-order because they require order-specific values.

The Decisions panel records the deterministic decision trail for inbound orders. Open a decision to inspect why a rule, override, or baseline behaviour produced the result. Where an order has routing information, its context menu also links to the pending route or shows the routing decision.

After a lifecycle action, verify the new order state, the execution list, and the outgoing report. See Simulation recipes for controlled scenarios.

Updated 2026-09-25 · Edit on GitHub