Phone Field
Overview
The Phone Field in Salesforce is a specialized field used to store phone numbers in various formats. It supports international formats, allowing users to enter country codes, area codes, and extensions.
Attributes of Phone Field
Basic:
Attribute Name | Description |
---|---|
Component Size |
For example, |
Label | A Label is the name shown to users and can come from various sources. Reference: Label Source Type |
Place holder | This is a hint or example text displayed in an input field before the user enters their own data. |
Type | Here you can choose different field types. Reference: Field Type. |
Layout | Field Layout allows you to arrange fields on the form. |
Default Country Code | In "Default Country," users can select a country code from the list to set as the default. |
Allow Extension | An extension in a phone field refers to an additional number that directs a call to a specific internal line within an organization or department. |
Dest Types | This attribute specifies whether the user wants to store a value in a variable or a model. Model: Here, the user can select the model and specify the field where the value will be stored. |
Dest Var | Here you can choose the variable option from variable list. |
Dest Model | Here you can choose the model from list. or it provide option for new model creation. |
Base UI:
Attribute Name | Description |
---|---|
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 |
|
Hide Space | After marking this checkbox as true, it will crop the extra corners of the fields. |
UI State:
Conditional Visibility:
Attribute Name | Description |
---|---|
Visibility Type | It determines whether a component is visible on the layout. It offers the following visibility types:
|
Read Only:
Attribute Name | Description |
---|---|
Read Only Type | It specifies whether a component can be edited by users. It offers the following options:
|
Conditional Disability:
Attribute Name | Description |
---|---|
Disability Type | It determines whether a component is disable on the layout. It offers the following visibility types:
|
Validation:
Attribute Name | Description |
---|---|
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. |
UI:
Attribute Name | Description |
---|---|
Layout | Field Layout allows you to arrange fields on the form. |
Is Copy Enabled | 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. |
Layout:
Attributes | Description |
---|---|
None | In the None layout, only the input/output field is visible, with no label displayed. |
Stacked | In a stacked layout, the input/output field is placed below the field label, with a small margin around the label. |
Horizontal | In a horizontal arrangement, the input/output field is placed before the field label, with a small margin around the label. |
Single Column | In a Single Column layout, the input/output field is larger than the field label, and displayed in single column grid. |
No Label | In the No Label layout, only the input/output field is visible, without the label. Layout: |
Label Source Type:
Attribute | Description |
---|---|
Model | From this source, users can select a Model 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. |
Events:
Events are essentially the automation of invoking the component's actions.
Here, we have onload event, click, double click actions are available for this components.
Icon Events | Description |
---|---|
onload | This event action is triggered when the Field component is loaded. |
change | This event action is triggered when the field is changed.. |
blur | This event action is triggered when the field is unfocused. |
Below here is the onload event workflow action.
on Load Event:
In the image below, you can select the created workflows.
For more information about Workflow check this out.
onload Events:
We have an onload event that runs when the component is loaded
Input Mapping
Input Mapping: "Whenever an event is triggered and you want to pass data to destinations such as models, variables, or components, you can use input mapping to achieve that.