Overview
Field component is used to represent individual data elements within a record, similar to columns in a relational database. It is designed to store and manage various types of data values required for different objects.
Fields can hold different types of data, such as numbers, phone numbers, email addresses, and text, depending on the data type configuration.
Fields can be bound to models and variables, enabling dynamic data handling and updates within your application.
The Field component is generic and can be configured to accept and display data in multiple formats and types.
If you need to present or capture data without linking it to a specific object, the Field component can be used independently.
Basic Attributes:
Attributes are the options available for each component, allowing you to customize its appearance and functionality. They help you tailor the look and behavior of your components to fit your needs.
Attribute Name | Description |
---|---|
Label | A Label is the name shown to users and can come from various sources. Reference: Source Type |
Place holder | This is a hint or example text displayed in an input field before the user enters their own data. |
Field Type | Here you can choose different field types. Reference: Field Type. |
Layout | Field Layout allows you to arrange fields on the form. |
Hide Space Checkbox | After marking this checkbox as true, it will crop the extra corners of the fields. |
Config and UI Attributes:
Attribute Group | Attribute Name | Description |
---|---|---|
Config | Debounce time in seconds | "Debounce time in seconds" refers to the delay period set to prevent a Event from being called. Example: If the debounce time is set to 2 seconds, the Event will only execute if there is a 2-second pause. |
Is Copy Enabled checkbox | After marking the checkbox as true, a copy icon will appear beside the name field. | |
Help Text | Provides additional guidance or information about a field or element to assist users in understanding how to complete it or what data is expected. | |
Value Destination Types | This attribute specifies whether the user wants to store a value in a variable or a model. Model: Here, you can select "Model" as the value destination. Note: Value Destination Model field appears when you select "Model" as the Value Destination Type. | |
Value Destination Variables | Here you can choose the variable option from this list. Note: This appears when you select "Variable" as the Value Destination Type. | |
Value Destination Model |
| |
UI | Component Size |
Note: Currently, we support Component Size |
Margin Location | "Margin Location" refers to the spacing around the outside edge of an element | |
Margin Size | "Margin Size" refers to the amount of space around the outside edges of an element, | |
Style |
| |
Classes |
| |
Validation | Required Type | Here, users can apply validation based on filter conditions.
|
Required Error Message | Enter the error message you want to display for required fields. | |
Minimum Length | Set the minimum number of characters required for the input field. | |
Min Length Error Message | Enter the error message to display if the input does not meet the required minimum length. | |
Maximum Length | Set the maximum number of characters allowed for the input field. | |
Max Length Error Message | Enter the error message to display if the input exceeds the maximum allowed length. | |
Pattern | A regex pattern or regular expression pattern, is a sequence of characters that defines a search pattern. It's used for pattern matching within strings, such as validating input, searching for specific text, or replacing text. | |
Pattern Error Message | A "Pattern Error Message" typically refers to an error generated when input data does not match the expected format defined by a regular expression pattern. This message is usually displayed to inform users that their input is invalid or incorrectly formatted. | |
Visibility | Visibility Type | It determines whether a component is visible on the layout. It offers the following visibility types:
|
Disability | Disability Type | It determines whether a component is disable on the layout. It offers the following visibility types:
|
Read Only | Read Only Type | It specifies whether a component can be edited by users. It offers the following options:
|
Component | Component Label | It simply shows the name over the field. |
Label Source Type:
Attribute | Description |
---|---|
Model (Salesforce Object) | From this source, users can select a Model (Salesforce Object) field to be displayed as the label name. |
Variable | Here, users can select the label name from variables such as Record ID, Is Disabled, Is Read only, or Is Visible. |
Cookie Key | Choose the available cookie key whose value you want to include from your browser. |
Local Storage Key | Select the available Local Storage Key whose value you want to include from your browser. |
User | Here, you can choose the label from user fields such as First Name, Last Name, Email, Name, Phone, or Session ID. |
Merge Field Expression | Merge Field Expression displays the value selected from the chosen value source. |
Message Body | Inside the message body, user also can add the values manually. |
Field Types:
Field Types | Description |
---|---|
text | |
textarea | |
rich textarea | |
checkbox | |
integer | |
double | |
currency | |
date | |
datetime | |
time | |
picklist | |
multipicklist | |
tag | |
array | |
object | |
criteria | |
password | |
phon | |
url | |
Jsons | |
Slider | |
Action | |
icon | |
model | |
fields | |
radio | |
image | |
images | |
lookup | |
color | |
record | |
Formulae | |
Merge Text | |
Field Selector | |
Visual Picker | |
Percentage | |
Address | |
Number | |
Boolean | |
html | |
css | |
javascript | |
Duration | |
Encrpyted | |
Filter | |
any | |
Model Selector | |
Categories Selector | |
Device |
Events
Events available for any component is of onload type.
Onload Events:
onload event occurs when the component has been loaded.
Here, only onload event actions are available for components.
Actions are basically workflow actions, which you can explore in Workflow here.
Add Comment