The nodes in the "dendrogram" category have two modes available: Transform and Exposed Inputs.
Transform Nodes
Transform mode is the default for Dendrogram nodes. A T connector is included on the node, and a matching Transform node connects to it.
In Transform mode, the node has no connectors for individual settings. To drive one setting from your flow, override it with a Write Property node between the Transform node and the T connector, or switch the node to Exposed Inputs.
Why use the Transform?
A Transform node creates a set of inputs in the Properties Palette for anyone using the flow to fill out. It converts those inputs into a plain JSON object and sends it to the paired node through the T connector. Transform nodes publish all of a node's settings to the Properties Palette in one step.
For instance, the Site Fill transform node automatically adds these 3 properties to the properties palette:
Transform nodes often also include UI widgets like sliders or list managers to make it easier to edit the flow results. For instance, the along point transform:
Editing Default Values
You can also edit the defaults so every time the flow is re-used, it starts with the same assumptions. In the Flow Canvas, click "Edit Defaults" on the Transform Node.
A preview of the properties appears on the left-hand side as an overlay.
Create a custom header for the node properties in the properties palette.
By default, the header will say the name of the node the transform pairs with, for example "Site Fill."
You can change this to be any custom value to make it easier for end users to know what the settings are for.
This can be especially useful in nested flows that re-use the same nodes for different sections or controls.
Publish the properties with a toggle
If the toggle is on, the transform properties will display in the properties palette
If the toggle is off, the properties will be hidden and always use the defaults set in the "edit defaults" canvas
The Transform Default values
Edit the default values for the flow.
Any new instances of the flow will automatically inherit these defaults.
Any changes in the properties palette will override the transform defaults.
What the Transform node sends
Every Transform node sends a plain object with a type naming the paired node and the settings inside parameters. For example, the Site Fill Transform node sends this object with its built-in defaults:
{
"type": "siteFill",
"parameters": {
"width": 16,
"space": 4
}
}The transform settings in the Properties Palette show lengths, areas, and volumes in your project units. The JSON always stores them in meters, square meters, and cubic meters, so a value you write into it with Write Property must use those units too.
If nothing is connected to T, most nodes run on built-in default settings that can't be changed. Site Plan, Wrap, and Subdivide Site produce no output without their Transform node.
Expose Inputs Mode
Swap between Transform Mode and Expose Inputs with the right-click menu. Right-click on a selected dendrogram node, and select "Expose Inputs."
Why Use Exposed Inputs?
With Inputs exposed, each property or input value that was previously handled with the Transform is now embedded into the node. This makes the dendrogram nodes behave more similarly to other (simpler) nodes in the Flow Builder node library.
In Exposed Inputs mode, you can:
Type values directly into text boxes/number spinners on the node to "hard code" the settings.
Add Input parameters to expose certain properties to the property palette UI, while leaving others hidden.
Give the Input parameters custom names to clarify detailed flow logic in the properties palette UI.
Control input values with outputs from other nodes without using write property as a go-between in the transform node.
Swap Between Modes
You can quickly swap between modes using the right-click menu.
However, the Transforms & Input Parameters do not convert between modes.
It is best to select the mode you want to use and stick with it as part of your flow design.
Comparing Transform vs Exposed Inputs Modes
There is no right or wrong method for your flows. Most will simply use the default Transform mode as it is the fastest and most consistent way to control the node inputs. The Exposed Inputs mode is available for advanced editors and flow masters who need more control.
| Transform | Exposed Inputs |
Prebaked Properties UI? | ✔️ | ✖️ |
Specialty widgets and controls in properties palette | ✔️ | ✖️ |
Selectively publish only some inputs? | ✖️ | ✔️ |
Use the same values for multiple nested versions of the node | Connect the same transform to multiple nodes' T input connectors | Connect the input parameters or output results to multiple nodes' input connectors |
|
|
|
All of the Nodes with "Expose Inputs" available:
Node name | Default/Transform Mode | Exposed Inputs Mode |
|  | |
|  | |
|  | |
|  | |
|  | |
|  | |
|  | |
Road |  |  |
|  | |
|  | |
 |  | |
|  |