> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/components/component-library/modular-checkout-components/common-customisations-for-form-subcomponents.md).
# Common customisations for Form subcomponents
In this guide, you'll learn how to perform common customisations on subcomponents in your [Form component](https://docs.limio.com/components/component-library/modular-checkout-components/component-checkout-form). Please note you will need to be using the [new Page Builder v2](https://docs.limio.com/product/page-builder/page-builder-overview-of-key-features) to achieve these customisations.
Not all of these customisations are available on all Field types.
## How to change the label on a field
1. In your page, click the purple pencil icon of the Form component you want to customise.
2. Click Edit Subcomponents in the right panel.
3. Find the subcomponent you want to change the label for, and click the line to expand.
4. Change the *Label* field.
5. Press Confirm.
6. Press Confirm in the right panel.
7. Press Save to rebuild your page, and publish when you are ready.
## How to add a character limit to a field
1. In your page, click the purple pencil icon of the Form component you want to customise.
2. Click Edit Subcomponents in the right panel.
3. Find the subcomponent you want to add a character limit to, and click the line to expand.
4. Set a character limit using the *Minimum length* and *Maximum length* fields.
* For example, if you want a first name field to be between 2-30 characters, you would set the *Minimum length* field to 2, and the *Maximum length* field to 30.
* You can set one length field without setting the other.
5. Press Confirm.
6. Press Confirm in the right panel.
7. Press Save to rebuild your page, and publish when you are ready.
## How to add validation to a field
1. In your page, click the purple pencil icon of the Form component you want to customise.
2. Click Edit Subcomponents in the right panel.
3. Find the subcomponent you want to add validation to, and click the line to expand.
4. Add a [regular expression (regex)](https://en.wikipedia.org/wiki/Regular_expression) to the field called *Validation regular expression*.
5. Press Confirm.
6. Press Confirm in the right panel.
7. Press Save to rebuild your page, and publish when you are ready.
## How to add a tooltip to a field
1. In your page, click the purple pencil icon of the Form component you want to customise.
2. Click Edit Subcomponents in the right panel.
3. Find the subcomponent you want to add validation to, and click the line to expand.
4. Add text to the *Tooltip message* field.
* If left blank, there will be no tooltip.
* If populated with text, an icon will appear next to the field label in the Shop to customers. when a customer hovers over it, the tooltip text will be displayed.
5. Press Confirm.
6. Press Confirm in the right panel.
7. Press Save to rebuild your page, and publish when you are ready.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.limio.com/components/component-library/modular-checkout-components/common-customisations-for-form-subcomponents.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.