> 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/validation-messages-in-the-starterapp-framework.md).

# Validation Messages in the StarterApp Framework

## Description

Form nodes in the StarterApp Framework simplify displaying validation messages to users. With updates to LogicNets in version 7.4 and higher, you are able to quickly add and display validation messages. For versions prior to v7.4, you have to model a combination of nodes and rules to show users when they have forgotten to enter required data or they have entered incompatible data.

**Node Type:** Form Node

**Used With:** This is for use in the StarterApp Framework.

## Example

In the Form node example attached to this topic, you can see that you can make a field mandatory in a form-part node, create the validation message a user will see, and then easily add a Form node that displays the message.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-aeb262f1c261a9568c05a52e32caa288f0d14fba%2Ff80ce158-944e-4e77-8bdb-f10c7410563d.png?alt=media)

## Using the Node

1. Make the field mandatory and set the validation message on the Validation tab of a form-part node.
2. Add a Form node after that form-part node.
3. Add a link back to the form-part node and default link to the next node.
4. Test your project to see the validation message.

## Attachments

* [StarterApp Form Node Example.zip](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/q51bmg-StarterApp-Form-Node-Example.zip)


---

# 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/validation-messages-in-the-starterapp-framework.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.