WorkingIndicator (FIX tag 636)

BooleanFIX 4.4

WorkingIndicator (tag 636) is a Boolean field defined in FIX 4.4. It appears in 3 message types, always optionally. It is an enumerated field with 2 defined values.

At a glance

Tag: 636
Name: WorkingIndicator
Datatype: Boolean (char)
Dialects: FIX 4.4
Messages: 3
Valid values: 2

What the specification says

Indicates if the order is currently being worked. Applicable only for OrdStatus = "New". For open outcry markets this indicates that the order is being worked in the crowd. For electronic markets it indicates that the order has transitioned from a contingent order to a market order.

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 636

ExecutionReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	139
35	MsgType	8	Execution Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
37	OrderID	ORD-10042
17	ExecID	EXEC-88117
150	ExecType	0	New
39	OrdStatus	0	New
636	WorkingIndicator	N	Order has been accepted but not yet in a working state
54	Side	1	Buy
151	LeavesQty	0
14	CumQty	1000000
6	AvgPx	1.09215
10	CheckSum	074

Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

Value	Meaning	Symbolic name
Y	Order is currently being worked	YES
N	Order has been accepted but not yet in a working state	NO

Where tag 636 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

Message	MsgType	Requiredness	Where in the message
ExecutionReport	8	Optional	directly on the message body
ListStatus	N	Optional	inside the OrdListStatGrp component
OrderCancelReject	9	Optional	directly on the message body

Wire format

Y or N. Not 1/0, and not true/false. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.

Read tag 636 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const workingIndicator = message.fields[636]?.raw;// e.g. "Y" — Order is currently being worked// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(636)  ?.enumValues?.find((e) => e.value === workingIndicator)  ?.description;

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix44

Try the decoder Source on GitHub