> 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/auto-scroll-section.md).

# Auto-Scroll Section

## Description

The Auto-Scroll Section part allows application end-users to keep a screen's scroll position at the last focused-on position on that screen.

## Use

The Auto-Scroll Section part can be added in the code view of a process node. When it is added to a process node, the Auto-Scroll Section part maintains the scroll position on a page when an end-user selects a UI element. To use this part, each form part element to which the auto-scroll should apply must include the CSS class that is defined in the selector field of the Auto Scroll Section part.

Create the part by performing the following actions:

1. Open the logicnet in the LogicNets Designer where you want to use the Auto-Scroll Section part.
2. With your mouse in the logicnet Viewer screen (where you build your logicnets), right-click your mouse.
3. Select ***add node***.
4. Select ***process***.
5. Double-click on the newly added node to open the Editor pane. You may have to increase the size of the pane to see each of the tabs at the top.
6. Click the *code* tab at the top of the Editor pane.
7. Add the part identified as Example 1 below inside the node parts of the node you created. You may also copy-paste the following lines:

   **Note: The "selector" field should contain the name of the CSS class that will make specific class objects auto scrollable. In the example above, the CSS class name is "auto\_scroll\_class".**

   { \_name = "auto\_scroll\_section", selector = ".your\_class\_name" }
8. Click ***save***.
9. Double-click on the node. In the list of parts associated with this node you will see the part you added (Example 2 from Example Project - see link below).
10. Double-click on the Auto-Scroll Section part in the list of parts for that node and the system will display the Selector field (Example 3 from Example Project - see link below).
11. Enter the name of the CSS class in the Selector field. This replaces the default *your\_class\_name* you used to set up the part.

## Editor Fields

| Tab   | Field Name | Description/Use                                                                           | Type/Options       | Optional/Mandatory |
| ----- | ---------- | ----------------------------------------------------------------------------------------- | ------------------ | ------------------ |
| Basic | Selector   | This field should contain the name of the CSS class format you wish to apply to the part. | .your\_class\_name | Mandatory          |

## Example

The following [example](/release-9/example-gallery/example-projects-for-parts/auto-scroll-section-example-project.md) demonstrates how to use the Auto-Scroll Section part.


---

# 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/auto-scroll-section.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.