Skip to content

Commit baf708b

Browse files
authored
Merge pull request #11403 from gjulivan/development2
update tree node documentation
2 parents 2939c1b + 1df8d63 commit baf708b

2 files changed

Lines changed: 17 additions & 1 deletion

File tree

  • content/en/docs/marketplace/platform-supported-content/modules/data-widgets
  • static/attachments/appstore/platform-supported-content/modules/data-widgets/treenode

content/en/docs/marketplace/platform-supported-content/modules/data-widgets/tree-node.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,16 @@ Mendix recommends using multiple Tree Node widgets in a nested matter. In this w
1818
* Allows you to nest tree nodes to map out your entire domain model into a tree view
1919
* Delivers out-of-the-box performance and network optimizations through lazy loading and caching of tree nodes
2020
* Offers additional styling customizations through Atlas UI
21+
* Displays an infinite amount of tree nodes by using self-reference entity (available from data widgets version 3.11.0 and above)
22+
23+
### Child Detection Mode
24+
25+
Starting from data widgets version 3.11.0, Tree Node offers 2 ways of rendering child nodes:
26+
27+
* **Manual child rendering** – This is the current available configuration. The end-user needs to put tree node widget (child) inside another treenode widget (parent) and set data source accordingly.
28+
* **Infinite tree node** – This is a recursive mode whereas the children have self reference to the same entity as the parent. In this mode, the widget will render child automatically. Data with empty parents will be automatically used as root.
29+
30+
{{< figure src="/attachments/appstore/platform-supported-content/modules/data-widgets/treenode/infinite_treenode.png" alt="self reference entity for treenode" class="no-border" >}}
2131

2232
### Lazy Loading
2333

@@ -47,7 +57,8 @@ Drag the Tree Node widget onto the page and use the configuration properties des
4757

4858
* **Data source** – the data source of the widget, which can also be optionally used as the data source for the header and content of the widget
4959
* Required
50-
* **Header type** – defines the type of the header
60+
* **Parent association** – the association used to select a parent. If set, tree node will automatically use infinite tree node child detection modes.
61+
* **Header type** – defines the type of the header:
5162
* Default: **Text**
5263
* When set to **Text**, you can configure the **Header caption** property
5364
* When set to **Custom**, a new region becomes available where you can configure the header through other widgets
@@ -59,8 +70,13 @@ Drag the Tree Node widget onto the page and use the configuration properties des
5970
* **Has children** – indicates if the current level of tree nodes has children tree nodes
6071
* Default: **Yes**
6172
* When set to **Yes**, a new region becomes available at the bottom of the widget where you can add another widget as child nodes
73+
74+
{{% alert color="info" %}}The **Has children** configuration will be set automatically on infinite tree node child detection mode.{{% /alert %}}
6275
* **Start expanded** – determines whether the content of the current level of tree nodes starts expanded or collapsed
6376
* Configurable when **Has children** is set to **Yes**; default: **No**
77+
78+
{{% alert color="info" %}}On infinite tree node child detection modes, we recommend setting **Has children** to **No** for large data sets. Otherwise, the setting will force the tree node to expand directly, loading all data at once.{{% /alert %}}
79+
6480
* **Animate** – defines whether the content is animated when a tree node expands and collapses
6581
* Default: **Yes**
6682

8.36 KB
Loading

0 commit comments

Comments
 (0)