> 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/validation-text.md).
# Validation Text
## Description
The *Validation text* part allows application users to add validation text using a process node rather than a form or form node part.
**Node Type:** This part is located in process nodes under the *Misc* menu.
**Used With:** This part can be used with all frameworks or in applications created without frameworks. For information on using Validation text with the StarterApp Framework, see [Validation Messages in the StarterApp Framework](/release-9/design-considerations-and-frameworks/frameworks/application-starter-framework/validation-messages-in-the-starterapp-framework.md).
## Use
The Validation text part can be used to create a custom validation message. To use this part, do the following:
1. Create a logicnet.
2. Add a process node to your logicnet.
3. Click the *Misc* menu and select
4. Select Validation message from the dropdown menu.
5. Fill out the required editor fields and click ***save***.
## Tips and Tricks
This part can be used to force changes in the underlying state of Assessment Framework or FHIR Questionnaire Step-by-Step tabs:
* set level = "Warning" if all questions (form parts) are ruled out, and you want to continue to show the TAB progress icon for validation errors (orange !)
* set level = "Error" if all questions (form parts) are ruled out, and you want to continue to show the TAB progress icon for errors (red X)
## Editor Fields
| Field Name | Description/Use | Type/Options | Optional/Mandatory |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------- | ------------------ |
| HTML enabled | When enabled, this checkbox tells the system the the question caption can be formatted using HTML. | Yes \| No | Optional |
| Text | This field contains the validation comment you want the system to display. This text can also include interpolated text, such as *$(my\_text\_object).* | Text | Mandatory |
| Level
(Rel 8.3+)
| Set the type of error based on the underlying impact desired:
- Warning:
- validation errors = 1
- errors = 0
- shows ASF tab with validation error icon
- Error (default setting):
- validation errors = 0
- errors = 1
- shows ASF tab with error icon
| Warning \| Error (default) | Mandatory |
---
# 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/validation-text.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.