> For the complete documentation index, see [llms.txt](https://docs.ezra360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ezra360.com/overview/components-overview/forms.md).

# Forms

Forms are user interfaces that allows user to view, enter and update data related to a specific entity. They are used to interact with records and perform various action within Ezra360. We have  different forms namely, **Main** form, **Quick Create** form, and **Portal** form, **Mobile** Form.

**Main Form:**\
The main form is the comprehensive primary form for a specific entity, and it contains essential fields and information related to that entity. It is mainly used when users access the entity directly through direct links. They provide complete view of the entity, allowing users to perform **CRUD** operations (*Create, Read, Update, Delete*) depending on their security roles. Which has multiple buttons to choose from that makes action to the entity.\
On <mark style="color:orange;">**#1**</mark> of the image below shows an example of a main form.<br>

<figure><img src="/files/AvqtM7i4rn9ALpOdfCiZ" alt=""><figcaption><p><mark style="color:red;">Click image to view full screen</mark></p></figcaption></figure>

***

**Process Form**\
Process forms are designed to present fields and information in a logical sequence, helping users complete tasks, and perform actions in a structured manner. They are particularly useful for capturing data and interactions related to well-defined business processes.

The following image on <mark style="color:orange;">**#2**</mark> shows a process form, the form hold its own inter-related information about an entity.

<figure><img src="/files/Ut88azcN3yI3fdxZxM4c" alt=""><figcaption><p><mark style="color:red;">Click image to view full screen</mark></p></figcaption></figure>

***

**Quick Create Form:**\
Quick forms are more compact and focused forms designed to show specific key information about an entity. They are used in scenarios where you need to see critical details quickly without the need for a full view of the record. Quick Create forms are often embedded in dashboards, views, or other areas where space is limited, and users require concise information at a glance.\
\
To access quick forms in a sub-grid, use the <mark style="color:orange;">**#1**</mark> "**+**" button to open a quick form.

<figure><img src="/files/iQF0iAgOXlF24QNT9cuW" alt=""><figcaption><p><mark style="color:red;">Click image to view full screen</mark></p></figcaption></figure>

The quick create form will be opened as a pop up on the screen. <mark style="color:orange;">**#2**</mark> shows the opened quick form in the middle of the screen. When you click <mark style="color:orange;">**#3**</mark> it will maximize the quick form and then open it in a main form with detailed view.

<figure><img src="/files/3xRmkiHYEKejPRy2jf45" alt=""><figcaption><p><mark style="color:red;">Click image to view full screen</mark></p></figcaption></figure>

***

**Portal Form:**\
Portal forms are specifically designed to enable external users (such as customers, partners, or suppliers) to interact with the data through your web portal in Ezra. Portal forms can be customized to match the branding and requirements of the external-facing website, allowing seamless data interaction between Ezra360 and portal users.

<figure><img src="/files/Oq3BJ9ORVfFA2dNudYJP" alt=""><figcaption><p><mark style="color:red;">To be replaced!</mark></p></figcaption></figure>


---

# 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.ezra360.com/overview/components-overview/forms.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.
