Markdown with Caplin extensions

As of FX Professional 5.7.0 and FX Sales 3.16.0, some trade model message fields support Markdown formatting.

Overview

As of FX Professional 5.7.0 and FX Sales 3.16.0, the following message fields support Markdown content as a richer alternative to plain text:

  • WarningMessage

  • DetailedWarningMessage

Markdown flavor

Syntax support:

Caplin substitution tokens

You can use the following substitution tokens in Markdown or plain text content:

Theme tokens

The front end application replaces theme tokens with a colour from the active theme file.

Syntax: {{theme:identifier}}

Example: {{theme:foreground.semantic.warning_inverse}}

Setting a theme colour in an HTML span tag
<span style="color: {{theme:foreground.semantic.warning_inverse}}">Unfortunately we are unable to quote a rate for this amount at this time. Please contact your dealer during their normal business hours.</span>

i18n tokens

The front end application replaces i18n tokens with a value from the i18n properties file for the active locale.

Syntax: {{i18n:identifier}}

Example: {{i18n:fx-margin-ticket.warningcode.123}}

Parameters in i18n token values ([parameter]) are not interpolated. For example, given the following i18n token value …

caplin.fx.validation.invalid_decimals=Only [decimalPlaces] decimal places are allowed

… the string {{i18n:caplin.fx.validation.invalid_decimals}} is rendered without interpolating the parameter token [decimalPlaces]:

Only [decimalPlaces] decimal places are allowed