> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/multinode.md).
# Multinode
## Description
A multinode allows the user to display user advice or descriptive text.
## Use
A multinode allows the user to display a diagnostic conclusion or a recommendation for a specific order or next step. Note: This node is available only for applications using the Visual Guidelines Framework.
## Editor Fields
| Tab | Field Name | Description/Use | Type/Options | Optional/Mandatory |
| ------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------ | ------------------ |
| Details | Label | This is the text the system will display as the header. | Text | Mandatory |
| Details | Path | This field holds text that can be used to look up additional information. | Text | Optional |
| Details | Call logicnet | This is the id of the logicnet to be called. Note: If you set this field the system will display a circle with an arrow on the UI. When you click this the system will open the called logicnet. | Text | Optional |
| Details | Description | This is the descriptive text or advice the system will display when the pathway is complete. | Text | Mandatory |
| Details | Operator | Operator text like 'AND' or 'OR' to be shown between two nodes.
Note: If you add a second node this field is mandatory.
| Text | Optional |
| Details | Separator | If this is checked the system adds a line separator between two nodes. | Checkbox | Optional |
| Details | Add output | No: No output call node required.
Yes: Add an output call node. If you select yes, fill in the call id and output label.
| Yes \| No | Mandatory |
| Details | Call id | This is the id output call node logicnet. | Text | Optional |
| Details | Output Label | This field holds text to be shown on the output call node. | Text | Optional |
| Details | Call next id | This is the id of the logicnet to be called on the next level. | Text | Optional |
| Details | Output path | This field holds text that can be used to look up additional information. | Text | Optional |
## Other Notes
When using side-by-side text view you can style the multinode using the CSS hooks defined in the node template *system\_settings.multinode\_advice\_template* shown below. As with all standard LogicNets node template functionality, this can be overridden with a custom template definition. See the Nodes and Part Templates article for more information on this topic.
## Examples
The following are different examples of multinode.
1\. Multinode Using Operator
2\. Multinode with Output: 
3\. Multinode with Call:
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/multinode.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.