Skip to main content
CYPEX Documentation
Support
v2.0.0 Latest stable release View changelog ->
Basic Referencegenerated

Markdown Text

A Markdown text field with translations

Technical id
default_markdown_field
Default size
1 × 1 cells
Translation keys
text

A read-only rich typography layout block that parses and prints markdown shorthand tokens (like stars for text weight, dashes for lists, backticks for code) alongside alignment settings.

When to use

  • Presenting rich textual content containing custom typography formatting (bold, italic), blockquotes, code blocks, or structured bullet lists.
  • Rendering dynamic string content that blends hardcoded text with i18n localization keys via expressions.
  • Displaying stylized informational sections where standard text containers are too limited and advanced layout customization is required.

What you need

  • Rich text properties, stylized documentation strings, or computed string combinations processed dynamically via expression fields.

Examples

  • A rich text layout container generating a custom message by joining explicit strings with translated references (e.g., ‘Hi ’ + i18n.text).
  • Rendering software documentation blocks, formatting code blocks, or displaying organized bulleted policy updates.

Avoid

  • Using to display pure unformatted raw fields or numeric scores, use the simpler data_display component instead.
  • Enabling the ‘HTML Allowed’ flag when rendering raw, unsanitized user inputs, which can introduce cross-site scripting security risks.

Use instead

  • Data Display — You only need to show basic data values or counts with simple card layouts rather than rich prose rendering.

Editor properties

Configure these in the Application Designer property panel. Group headings mirror the editor where possible. Data Source is where the element gets its rows or field binding (a view/query, a connector operation, or a parent form field). References appear only for view-backed sources and map foreign-key ID columns to readable labels from another view.

Text
TextrequiredCustom expression
A rich text editor field that accepts standard formatting notation, such as double markers for bold, single markers for italics, backticks for code blocks, hyphens for lists, and text alignment coordinates (left, center, right).
Default: buildCustomExpressionValue("i18n.text")
OverflowoptionalOne of: hidden, auto, visible
An expression box defining dynamic data overrides. Defaults to ‘i18n.text’ to reference the formatted text block above. String values can be concatenated seamlessly.
Choices
  • hidden
  • auto
  • visible
Default: none
AlignoptionalOne of: left, center, right, justify
A boolean switch controlling whether the rendering framework parses and injects native HTML tags found within the source content.
Choices
  • left
  • center
  • right
  • justify
Default: none
HTML AllowedoptionalYes / no
A boolean switch controlling whether the rendering framework parses and injects native HTML tags found within the source content.
Default: false
GapoptionalNumber
Spacing between Markdown blocks in the rendered output.
Default: none

Sizing

  • Default size when dropped on a page: 1 × 1.

Accessibility

Renders as a semantic layout box preserving appropriate native element markers (headings, lists, emphasis tags) generated by the markdown parser engine.

Where you can place it

Drag this element into one of these containers:

1
2
3
4
5
{
  "config": {
    "text": "@@expression:'value'"
  }
}
1
2
3
4
5
6
7
8
9
{
  "config": {
    "text": "@@expression:'value'",
    "overflow": "hidden",
    "align": "left",
    "htmlAllowed": false,
    "gap": 0
  }
}

Ready-made setups

Configuring a markdown element to append an expressional dynamic string prefix directly to a pre-formatted localized text layout translation.

1
2
3
4
5
6
7
8
9
{
  "config": {
    "text_settings": {
      "formattedText": "Welcome to the custom **management platform** overview.",
      "textSourceExpression": "@@expression: 'Hi ' + i18n.text",
      "htmlAllowed": false
    }
  }
}