Skip to main content
Version: 8.6.9.2

1800-client-config

#Message NameDescription
1805AccountConfig
1806AccountExchGroupConfig
1810AccountRouteConfig
1814AltHedgePolicyMap
1811AltHedgeTargetMap
1815AltSymbolMap
1830ClientAccntStrategyMap
1835ClientAccountConfig
1935ClientConfigChangeRequestOne request carries a SERIES of record-level operations (target message + pkey +

the changed fields + their propose-time values) that merge, reject, or return

as one unit. crClass discriminates the two review queues: Settings reviews

ClientConfig requests, Risk Controls reviews RiskControl requests.

Merged and Rejected are TERMINAL - no further transitions or withdraws; a new

request is required. Pending/Returned remain actionable. Note comments stay

accepted on terminal records - terminal seals the DECISION, not the conversation

(every publish is archived; the 24h retention window bounds the append period).

Merge is apply-FIRST and SERVER-SIDE: a decide to Merged runs the ops through the

target messages' own write pipelines under the CHECKER'S session (per-record ACL

re-checks as if the checker posted each write); ONLY on total success does the

state commit to Merged. On any failure the state stays as it was and the failure

is recorded as a durable mergeFail comment (failedCount).

RiskControl requests carry exactly ONE op (no baskets).
1850ClientFirmConfig
1910ClientPrivateSRSE
1817HedgePolicyAlgoConfig
1813HedgePolicyConfig
1816PositionHedgeTrigger
1922TraceAccntRoutes
1923TraceAccntRoutesResult
1915UserAuctionFilter
1916UserAuctionTickerFilter
1905UserAuthentication
1875UserConfig
1900UserMessage