> 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/design-considerations-and-frameworks/frameworks/application-starter-framework/load-and-reload-sections.md).

# Load and Reload Sections

There are times while your application runs that you may want the system to reload data in a section or start a different logicnet in a section. For example, if a user clicks on a menu button in the topbar, the system can reload a different logicnet in the main section. To reload a section add “reload section” node in your logicnet.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-e7301c0a4053eba64211416a43f088d48bd8cb50%2F5f33cff9-a50a-44d5-9ac6-cdd5ac954227.png?alt=media)

Once you add the node you can configure the parameters in the *Parameters* tab of the node-details window. You can configure the following parameters.

| Field Name | Description/Use                                                                                                                                | Type/Options | Optional/Mandatory |                                                                                                                                                                                                                                                                                                                                                                                                                                                        |            |          |
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- |
| Sections   | <p>This is where you specify the sections to be reloaded. Each section consists of the following parameters:<br><strong>Section:</strong> main | side         | topbar             | footer<br><strong>Update only:</strong> Set this to "no" if you want to load a different logicnet in the section. If this is set to "yes" the system will refresh the logicnet in the session to reflect any data updates.<br><strong>UI net:</strong> This is the name of the UI logicnet the system should load in the section.<br><strong>Process net:</strong> This is the name of the process logicnet the system should load in the section.</p> | Collection | Optional |

In the *StarterAppUI* example project you can see that the *topbar\_process* UI net uses the reload section function to load either *main\_ui* or *main\_ui2* into the main section.


---

# 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/design-considerations-and-frameworks/frameworks/application-starter-framework/load-and-reload-sections.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.
