> 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/configurations/components-config-overview.md). # Components Config Overview ### Overview A **Component** is like a basic building block that you can attach to an application, or web. Once you attach a component, you can give it specific details to match your requirements. These details might be about what users need, its features, or rules for using it. A component can even have smaller parts within it. You can use a component multiple times in your space. The following Components are all configured under **Settings Entity**. The settings entity will redirect you to Admin module where configuration is done. {% hint style="warning" %} Please Note: Your access to this module within the Ezra360 platform depends on your access settings. For more information, see [Security Roles and Privileges](/security-and-roles/security-roles-and-privileges.md) and [User Roles](/security-and-roles/user-roles.md) {% endhint %} To navigate it, go to **Modules** > **Customization**\ **#1** navigate to list of **Modules**, and click **#2** **Customization** Entity, or you can instead Click on **#1**** Main Menu** then you will see **#2** **Customization** Card which will display all the Customization sub-modules .

The **Customization** direct link will take you to an Admin Module, that has a layout like this:

From the Admin Module Screen we will navigate to see the listed Entities. See the [Entities](/configurations/components/entities.md)configuration. *** ## Data Types The following table of data types acts as guide when configuring Ezra for your form fields.

Data Type	Description
Single Text	A field that allows entering a single line of text. It's commonly used for short pieces of information. This field can contain up to 4,000 text characters. You can set the maximum length to be less than this.
Multi-Line Text	This is a scrolling text box. The field that allows entering multiple lines of text. It's useful for capturing longer descriptions or comments. When you add this field to a form, you can specify the size of the field.
Whole Number	field that stores whole numbers (integers). It's suitable for counting items or quantities. You can set the minimum and maximum values too.
Decimal	A field that stores decimal numbers (floating-point numbers). It's used for storing fractional or precise numeric values.
Currency	A field that stores currency values with currency symbols. It's used for storing monetary amounts.
Lookup	A field that creates a relationship with another entity and displays a searchable list of records from that entity.
Generic Lookup	Similar to a lookup, but more flexible as it can reference multiple entity types. It's used for creating relationships with different types of records.
Partylist	A special type of field used to reference multiple party records (like Contacts, Accounts) involved in an activity. It's often used for scheduling and tracking interactions.
Select Option	A field that provides a list of predefined options for selection. Users choose from the provided values.
DateTime	A field that stores both date and time information. It's used to capture specific points in time.
Date	A field that stores only date information. It's used for capturing dates without time details.
Boolean	A field that stores true/false values. It's used for capturing binary choices. Example: Is Active - True, Accept Terms - False.
Rich Text	It allows formatting text with styles, links, and images. It's used for creating well-structured content.
Web Resource	A field that can display web content within the form. It's used for embedding external resources.
Hyperlink	A field that stores a URL and displays as a clickable link. It's used for linking to external resources.

## Common Form Records Fields Below is the common records fields, when configuring Ezra, you will most likely to come across this fields, here is an overview of each records. Refer to this Table if you don't understand some text fields. {% hint style="info" %} Please note that Record fields may differ according to the component and the Business Process. {% endhint %}

Field Record	Description
Display Name	it represents the display name of your field. The name that is displayed to the user on the interface. For example, "Sales Order".
Schema Name	It must be unique. It is used to create the logical name. This name should be in Pascal case. The schema name is used to create the class for the entity. For example, "SalesOrder".
Plural name	refers to the name used to represent multiple instances of a data record entity. For example, "Sales Orders"
Entity Type	Data Record: refers to the structured data components that represent various business objects or concepts within the system. Each entity is associated with a set of fields that capture relevant information. Document Library: refers to a centralized repository where you can store and manage various types of documents, files, and attachments associated with records within the Ezra environment.
Owner Type	Defines the scope and nature of ownership for records within a specific entity. User: refers to individual users within the system that can be assigned as the owners of records that will have control over those records and can perform actions. Everyone: It signifies that records are owned by the system itself or are considered to be shared across the organization.
Boolean Data Types
☑ Business Process	it indicates that whether the associated entity or record type uses a business process flow to streamline and standardize workflows.
☑ Social Timeline	Indicates whether the entity or record supports the social timeline feature. The social timeline allows users to see social activities and interactions related to a record, such as posts and mentions from social media platforms.
☑ Enable Audit	Specifies whether auditing is enabled for the entity or record. Auditing tracks changes to records and provides a history of data modifications.
☑ Duplicate Detection	Determines whether duplicate detection rules are applied to the entity or record. Duplicate detection helps prevent the creation of duplicate records in the system.
☑ Attachments	Indicates whether the entity or record can have file attachments associated with it. If set to true, users can attach documents and files to the record.
☑ Customizable	It is set to default on Ezra. Specifies whether the entity or its forms, views, and fields can be customized. If set to true, users with appropriate permissions can customize the entity's structure and behavior.
☑ Searchable	It refers that the field value is searchable by the user in a case of categorized search or relevance search.
☑ Publish Create Event	Determines whether the entity is searchable. If set to true, records of this entity can be included in search results.
☑ Visible	Specifies whether the entity or field is visible to users. If set to false, the entity or field may be hidden from users, but it can still be used in the system.
☑ Read-Only	Specifies whether the entity or field is read-only. If set to true, users can view the data but cannot edit it.
☑ Required	Indicates whether a field is required for the creation or update of a record. If set to true, users must provide a value for this field when creating or modifying a record.
☑ Publish Create Event	Indicates whether an update event is published when a record of this entity type is created. It can be used to trigger external processes or integrations when records are created.
☑ Publish Update Event	Indicates whether an update event is published when a record of this entity type is updated. It can be used to trigger external processes or integrations when records are updated.

--- # 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/configurations/components-config-overview.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.