> For the complete documentation index, see [llms.txt](https://rpa-connect.gitbook.io/rpa-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rpa-connect.gitbook.io/rpa-connect/en-us/form-design/comprehensive-form-development.md).

# Comprehensive Form Development

In the previous section, we analyzed the various types of properties that allow you to customize form fields to give them both the appearance and functionality you desire. Many of these properties are common across multiple tools; however, each has its own particularities. In this final stage, you will be able to:

* Gain an in-depth understanding of the features and functions of the main input fields and tables.
* Apply the properties previously discussed to each specific field type to modify its characteristics.
* Analyze and choose the most suitable option type based on the data you aim to collect with your form.

To achieve this, we will work on the basic form design created in the first stage of this journey. Remember to save your progress using the ***Save*** button as you complete the proposed actions.


---

# 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://rpa-connect.gitbook.io/rpa-connect/en-us/form-design/comprehensive-form-development.md?ask=<question>&goal=<endgoal>
```

`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.