ComplexEvents
component blockFIX 5.0 SP2
ComplexEvents is a FIX component block defined in FIX 5.0 SP2 — a reusable group of fields that messages include by reference rather than repeating field by field. It has 1 member and is used by 72 message types.
FIX 4.2 has no component blocks
Component blocks were introduced after FIX 4.2, whose dictionary defines only the standard header and trailer and inlines everything else directly into each message. That is why almost every component page covers the later dialects only.
Members
- 1483NoComplexEventsrepeating groupOptional
- 1484ComplexEventTypeOptional
- 1485ComplexOptPayoutAmountOptional
- 1486ComplexEventPriceOptional
- 1487ComplexEventPriceBoundaryMethodOptional
- 1488ComplexEventPriceBoundaryPrecisionOptional
- 1489ComplexEventPriceTimeTypeOptional
- 1490ComplexEventConditionOptional
- —ComplexEventDatescomponentOptional
Messages that include ComplexEvents
- 6IOI
- 7Advertisement
- 8ExecutionReport
- AADerivativeSecurityList
- ABNewOrderMultileg
- ACMultilegOrderCancelReplace
- ADTradeCaptureReportRequest
- AETradeCaptureReport
- AFOrderMassStatusRequest
- AGQuoteRequestReject
- AHRFQRequest
- AIQuoteStatusReport
- AJQuoteResponse
- AKConfirmation
- ALPositionMaintenanceRequest
- AMPositionMaintenanceReport
- ANRequestForPositions
- AORequestForPositionsAck
- APPositionReport
- AQTradeCaptureReportRequestAck
- ARTradeCaptureReportAck
- ASAllocationReport
- AWAssignmentReport
- AXCollateralRequest
- AYCollateralAssignment
- AZCollateralResponse
- BNews
- BACollateralReport
- BBCollateralInquiry
- BGCollateralInquiryAck
- BKSecurityListUpdateReport
- BLAdjustedPositionReport
- BMAllocationInstructionAlert
- BNExecutionAcknowledgement
- BOContraryIntentionReport
- BPSecurityDefinitionUpdateReport
- BQSettlementObligationReport
- BRDerivativeSecurityListUpdateReport
- BZOrderMassActionReport
- CEmail
- CAOrderMassActionRequest
- CCStreamAssignmentRequest
- CDStreamAssignmentReport
- DNewOrderSingle
- ENewOrderList
- FOrderCancelRequest
- GOrderCancelReplaceRequest
- HOrderStatusRequest
- JAllocationInstruction
- QDontKnowTrade
- RQuoteRequest
- SQuote
- VMarketDataRequest
- WMarketDataSnapshotFullRefresh
- XMarketDataIncrementalRefresh
- ZQuoteCancel
- aQuoteStatusRequest
- bMassQuoteAcknowledgement
- cSecurityDefinitionRequest
- dSecurityDefinition
- eSecurityStatusRequest
- fSecurityStatus
- hTradingSessionStatus
- iMassQuote
- mListStrikePrice
- qOrderMassCancelRequest
- rOrderMassCancelReport
- sNewOrderCross
- tCrossOrderCancelReplaceRequest
- uCrossOrderCancelRequest
- xSecurityListRequest
- ySecurityList
Components that nest ComplexEvents
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