> 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/form-node.md). # Form Node You use a form to present a form on screen in your application and then wait for the application user to input data or perform an action, such as entering information in a particular field or reading information. ## Use This part has two variants, which are used in the LogicNets "no-framework" installations and StarterApp Frameworks respectively. It is not required in Assessment Framework or other frameworks and is not visible on the toolbar of projects associated with other frameworks. During your application's runtime, when the LogicNets engine processes this node, the system displays all user-facing nodes up to that point on screen and pauses the application until the user provides the next input. This can include submitting text or clicking a button, for example. ### Form Node in Starter App Framework Projects Starter Apps can use a wide variety of form part nodes, which display in orange in the Designer. You indicate when the system should present all preceding inputs on screen by placing this form node at the end of a line of form part nodes and any other logic. ### Form Node in No Framework projects When modeling in the standalone or "no framework" project, this node contains all of the user inputs you want to display on the screen at one time. For example, you could create a form where your users can enter their first and last names. ## Editor Options There are no editor options with the form part when you use it with Starter App frameworks. When you're modeling a project without a framework the part menu provides you access to the different types of available user input. ## Advanced Note The form node performs the same basic function in both the Starter App and "no framework" models, but there are some differences in the underlying configurations. If you convert a Starter App to a standalone application (or vice versa) you may experience some runtime defects, until you apply the correct form node for the project type. --- # 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/form-node.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.