> 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/process-node-parts/get-parts-definitions-beta.md).

# Get Parts Definitions (BETA)

## Description

The *get\_parts\_definitions* part is an advanced part you can use to retrieve a container of all the elements of a node. It is used with a specialized logic construction called a "decorator" that can add UI and logic in front of or at the end of a section of logic.

The system stores the result in the specified data object as a collection, and you should use an index to access the desired part (1-based).

**NOTE**: This part is currently in Beta mode. It is located in the *App Dev* parts submenu in the Designer Part Editor.

**Used With:** This part requires the params structure provided through the decorator construction. Talk to your LogicNets Representative for more information about this feature.

## Editor Fields

| Field Name                         | Description/Use                                                                                                                                                                                                                                          | Type/Options | Optional/Mandatory |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ |
| Part(s) Data-object                | <p>The retrieved parts definitions will be stored in the provided variable name (allowing interpolation of the name).<br>If the system cannot retrieve the parts definitions, this object is set to nil.</p>                                             | Data Object  | Mandatory          |
| Apply part default/overrides       | After getting the parts definitions, apply all (specific) part defaults and (specific) part overrides.                                                                                                                                                   | On \| off    | Optional           |
| Apply options conditions/rules     | Apply configured rules at the option level                                                                                                                                                                                                               | On \| off    | Optional           |
| Add reference to node in all parts | <p>When checked, each part structure will also get a field '*' that will contain the following structure:<br><code>* = { node\_id = node\_id, net\_id = net\_id, db = called\_db,</code><br><code>node = \*reference to the node properties }</code></p> | On \| off    | Optional           |


---

# 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/process-node-parts/get-parts-definitions-beta.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.