Release notes

---

What's new

• We have added the ability to send a client's account group name in the Account field (tag 1) of orders forwarded to a liquidity provider. LPs that expect a string identifier now receive it directly, with a single configuration parameter and no duplicate tag

---

What's new

• We have introduced support for string-based trading account identifiers. Order flow now carries an alphanumeric account, order id, and group end-to-end (from the client FIX session all the way to the liquidity provider), instead of being limited to numeric logins.

---

What's new

• We have added automatic recovery for market-data subscriptions in the Liquidity Manager: when a liquidity provider rejects a symbol subscription, the LM now resubscribes automatically using a configurable exponential backoff, instead
  of leaving that symbol without quotes until the next full session reconnect.
• We have added a new FXPrimus market-data (quotes) connector to the Liquidity Manager.

Bug fixes

• We have fixed a Liquidity Manager bug where a Trade session would refuse to connect if the ApiData_<N>_NewOrderSingleTag (or sibling GroupTag / HeaderTag / TimeInForce) parameter exceeded 1024 characters — for example on configurations with many trading groups. The session now loads parameters of any length.

Misc

• Minor logging changes

---

What's new

• We have extended outbound FIX tag obfuscation to cover integer-valued tags, so identifying values sent as integers (e.g. Account, PartyID) are no longer transmitted in clear text.

---

Misc

• Log files have daily rotation

---

Misc

• We have improved how the LiquidityManager recovers from corrupt persistent delivery files.

---

Misc

• We have improved diagnostics for components that persist data to Postgres

---

Misc

• We have improved diagnostics for components that persist data to Postgres

---

Bug fixes

•  We have fixed precious metal margin calculator 

---

Bug fixes

• we have fixed an issue when SEND_ORIGINAL_REQUEST_PRICE was set and markup for a symbol on Liquidity Manager was set, incorrect price would be sent to Liquidity Provider

---

Misc

• We are now treating suspended status as new (applicable for Exante connector)