ADF node: panel

Node

Description

A container that highlights content as additional information, a warning, or the result of an action.

Example

Java

1
2
Panel.info(p("Hello world"));

ADF

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
{
  "type": "panel",
  "attrs": {
    "panelType": "info"
  },
  "content": [
    {
      "type": "paragraph",
      "content": [
        {
          "type": "text",
          "text": "Hello world"
        }
      ]
    }
  ]
}

Compatibility

Products

Usage

• DocContent
• LayoutColumnContent
• NestedExpandContent
• NonNestableBlockContent
• TableCellContent

Marks

❌ N/A

Structure

• type - panel
• attrs
  • panelColor? - string1
  • panelIcon? - string2
  • panelIconId? - string3
  • panelIconText? - string4
  • panelType - info | note | tip | warning | error | success | custom
  • localId? - string5
• content - array(PanelContent…)

---

1. The various overrides for the panel icon properties and the panel’s color are mainly intended for the custom field type, but the schema does not enforce that restriction. The behaviour when combining these properties with other panel types is undefined and may change in the future.↩︎
2. The various overrides for the panel icon properties and the panel’s color are mainly intended for the custom field type, but the schema does not enforce that restriction. The behaviour when combining these properties with other panel types is undefined and may change in the future.↩︎
3. The various overrides for the panel icon properties and the panel’s color are mainly intended for the custom field type, but the schema does not enforce that restriction. The behaviour when combining these properties with other panel types is undefined and may change in the future.↩︎
4. The various overrides for the panel icon properties and the panel’s color are mainly intended for the custom field type, but the schema does not enforce that restriction. The behaviour when combining these properties with other panel types is undefined and may change in the future.↩︎
5. The localId, when present, will typically be a random UUID. This is not enforced by the schema.↩︎