Skip to documentation
Screebits Docs
Flow Editor
Open Screebits
  • Screebits
  • Flow Editor documentation
  • Blueprints
  • Your first steps in Screebits
  • Workspace, strategies and account
  • Get started with the Flow Editor
  • Build an RSI Momentum Alert
  • Flow Editor concepts
  • How a strategy starts and continues
  • Control and data connections
  • Nodes, parameters, outcomes, and ports
  • Plans and feature availability
  • Saves, versions, and checkpoints
  • Tactical and Portfolio strategies
  • Validation and readiness
  • Flow Editor mode guides
  • Build Portfolio strategies
  • Build Tactical strategies
  • Flow Editor guides
  • Add a Quant Hub metric
  • Configure a node
  • Configure Settings and visual preferences
  • Connect nodes
  • Create a strategy
  • Create checkpoints and restore versions
  • Reset a Flow safely
  • Debug and replay a Backtest
  • Fix validation issues
  • Use keyboard shortcuts
  • Manage variables
  • Run a Backtest
  • Save and resolve conflicts
  • Work on tablet and mobile
  • Use Quick add
  • Use the Inspector
  • Add, move, duplicate, and remove nodes
  • Flow Editor examples
  • Portfolio rebalance with risk limits
  • Tactical order and position monitoring
  • Use Backtest Center
  • Read a Backtest result
  • Compare and export Backtests
  • Explore Quant Hub
  • Metric parameters, charts and overlays
  • Flow Editor node reference
  • Order Ticket Field
  • Flow Editor troubleshooting
  • Troubleshoot activation and validation
  • Troubleshoot Backtests and replay
  • Troubleshoot compact layouts
  • Troubleshoot connections and data types
  • Troubleshoot plans and locked features
  • Troubleshoot Quant Hub in the Flow Editor
  • Troubleshoot save, offline, and conflicts
  • Backtests and responsible use
  • Flow Editor glossary
  1. Screebits
  2. /Flow Editor documentation
  3. /Flow Editor node reference
  4. /Order Ticket Field
IntermediateLast verified Sep 30, 2026

Order Ticket Field

Extracts one field from an Order Ticket.

On this page
  1. When to use
  2. Example
  3. Identify the submitted order
  4. Common problems
  5. Next steps

Extracts one field from an Order Ticket.

When to use

Use it when order lifecycle logic needs a scalar value from the ticket produced by Order.

Example

Extract the client order identifier before waiting for or canceling an order.

Try it here

Explore Order Ticket Field

Extracts one field from an Order Ticket.

Exercise steps
  1. Choose a different field in Inspector.
  2. Observe how the active output and its type change; the connected input keeps its structured value.
Event TriggerOrderOrder Ticket Field
Graph preview — a diagram of the example

Identify the submitted order

Connect Order: Order Ticket to the ticket input and select Client Order ID to obtain a string identifier for a later targeted Cancel Orders request. Alternatively, select Quantity to inspect the amount submitted or Submitted At to inspect its time. These are fields of the submission ticket, not evidence of a fill. If Await Order Event later reports rejection or timeout, the ticket can still identify the attempted order while Fill Price may be absent. Keep the ticket on the same Order branch rather than borrowing an identifier from another activation.

Common problems

Connect an Order Ticket, not an Order Result. Select the field needed by the downstream node.

Next steps

Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.

Node facts

These facts come from the current Flow Editor node catalog.

Node type
Order Ticket Field
Activation role
No activation role
Category
Field
Availability
Tactical only
Modes
Tactical
Required plan
None
Behavior
Transforms a value
Control inputs
0
Output data types
Text, Number, price, datetime

Parameters

NameInput typeRequirementDefaultOptions and constraints
Order ticket fieldSelection listRequiredclientOrderIdOptions: Client order id, Instrument, Side, Order type, Quantity, Limit price, Stop price, Time in force, Submitted at

Primary parameters

  • Order ticket field

Outcomes

None

Data inputs

  • Order Ticketorder Ticket · Required

Data outputs

  • Client Order IdTextShown when Order ticket field is clientOrderId
  • Instrument IdTextShown when Order ticket field is instrumentId
  • SideTextShown when Order ticket field is side
  • Order TypeTextShown when Order ticket field is orderType
  • QuantityNumberShown when Order ticket field is quantity
  • Limit PricepriceShown when Order ticket field is limitPrice
  • Stop PricepriceShown when Order ticket field is stopPrice
  • Time In ForceTextShown when Order ticket field is timeInForce
  • Submitted AtdatetimeShown when Order ticket field is submittedAt

Related documentation

  • OrderSubmits a configured Tactical order and produces a ticket for lifecycle tracking.
  • Await Order EventWaits for lifecycle events associated with a submitted Order Ticket.
  • Cancel OrdersRequests cancellation for one pending order or for open strategy orders.

On this page

1 / 5
  1. When to use
  2. Example
  3. Identify the submitted order
  4. Common problems
  5. Next steps

Practical guidance for strategies, historical simulations and metric research in Screebits.

Responsible useGlossary