> 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/getting-started/interacting-with-nodes-in-the-designer-viewer/node-categories.md).

# Node Categories

## Node Categories

There are multiple nodes available in the LogicNets Designer, and these node types are grouped together into seven categories:

* *Form parts*
* *Report parts*
* *Process*
* *Routing*
* *Call parts*
* *Form*
* *Special*

## Framework-specific Nodes

Categories and associated nodes appear in your Designer based on the framework on which your project is based or if it is based on a framework at all. This makes it easier for you to find the nodes you need; for example, if your project uses the Assessment Framework, your nodes toolbox will look like this—there is no *form* option because Assessment Framework doesn't use forms.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-58fffb9757c2ba8251418d8d76d96103fbc70cea%2Faefe06bb-b596-4fe5-8c6e-99dd4c5f0fe7.png?alt=media)

## Node Choices

Node categories can have one or more node options; for example, the form parts category contains multiple options while the process node exists by itself. If a category has multiple options a collapsed arrow displays on the nodes toolbox and you can click that arrow to open the dropdown menu of your options. Note that the special category will contain options relevant for the framework you are working in.

Here is an example of the node options available in the Assessment Framework under form parts.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-2e7e3e8394ec41a400a7e1845974972a385323f4%2F7673a215-678d-4917-92d4-5d11f847f5a3.png?alt=media)

## Recently Used Nodes

When you are creating logicnets you frequently use the same node type over and over. To save you time in selecting nodes the system displays the most recently used node per category at the top of the list—the header of that node category. You can click or drag the header node to [add it to your logicnet](/release-9/getting-started/interacting-with-nodes-in-the-designer-viewer/add-a-node.md).

When you log in for the first time the system displays the default category headers, but as you use the system it updates the recently used information.

Note that if you switch between frameworks, e.g. work on a project without a framework and then create a different project with a framework, the system will display the first available node in that category for the framework you switch to.


---

# 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/getting-started/interacting-with-nodes-in-the-designer-viewer/node-categories.md?ask=<question>&goal=<user_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.