Overview

A Time Field is a UI component designed to capture and display specific times of the day. Unlike date fields, which capture full date and time information, a Time Field focuses solely on the time component, allowing users to input or select hours and minutes, and sometimes seconds.

Attributes of Time Field

Basic:

Attribute Name	Description
Component Size	This allows users to modify the size of a specific component according to the grid size of layout. For example, If the layout grid size is 3 then layout is divided into 3 sections then you can changes the components size between 1 to 3.
Display as	Display As allows you to select data type options to define how the field will be display. For example, if you have a text field and choose to display it as a picklist, the data will be stored as text but displayed as a picklist.
Label	Here user can set the label name for time. It can be 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.
Dest Types	This attribute specifies whether the user wants to store a value in a variable or a model. Variable: If you choose the variable option, you can select the variable where you want to save the field's value. You can bind this variable's value to the component by creating the appropriate variable. 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. Note: This appears when you select "Variable" in the Dest Type.
Dest Model	Here you can choose the model from list. or it provide option for new model creation. Note: This appears when you select "Model" in the Dest Type. Reference: How to Create a Record Type Model

Config:

Attribute Name	Description
Time Format	Here, you can set different types of time formats as HH:MM, HH:MM:SS
Hours format	Here, users can set the hour format to either 12-hour or 24-hour.
Value Destination Types	This attribute specifies whether the user wants to store a value in a variable or a model. Variable: If you choose the variable option, you can select the variable where you want to save the field's value. You can bind this variable's value to the component by creating the appropriate variable. 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	From the value destination model, you can select the specific model where you want to save the field's value. By using a model, you can bind a value to the component, with the value coming from the object used during 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	It is used to apply custom styles to section, such as color, font, size, and more. It allows you to define the appearance of a component by specifying CSS properties directly within the attribute.
Classes	It is used to apply SLDS classes to section, if needed.
Hide Space	After marking this checkbox as true, it will crop the extra corners of the fields.

UI State:

Visibility Type:

Attribute Name

Description

Visibility Type

It determines whether a component is visible on the layout. It offers the following visibility types:

Always: The component will always be visible.
Conditional: The component's visibility is determined based on specific criteria, which can make it either visible or hidden as needed.
You can explore more about Visibility Type here.

Reference: Conditional Visibility

Read Only:

Attribute Name

Description

Read Only Type

It specifies whether a component can be edited by users. It offers the following options:

Never: The component will always be editable at any time.
Always: The component will never be editable.
Conditional: The component's editability is determined based on specific criteria, which can make it either editable or read only as needed.
You can explore more about Read Only Type here.

Reference: Read Only

Conditional Disability:

Attribute Name

Description

Disability Type

It determines whether a component is disable on the layout. It offers the following visibility types:

Never: There is no disable option for this component
Always: The component will always be visible.
Conditional: The component's visibility is determined based on specific criteria, which can make it either visible or hidden as needed.
You can explore more about Disability Type here

Reference: Conditional Disability

Validation:

Attribute Name	Description
Required Type	Here, users can apply validation based on filter conditions. Never: This field is never required. Always: This field is always required.. Conditional: The required field is determined based on specific criteria of And, OR condition
Required Error Message	Enter the error message you want to display for required fields.
Minimum Date	Here, users can set the minimum date that can be selected for validation.
Maximum Date	Here, users can set the Maximum date that can be selected foe validation.

UI:

Attribute Name	Description
Layout
Help Text

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.

Conditional Visibility Type:

Attributes Name	Description
Destination Type	Users can select the destination type where the visibility criteria must be applied. Reference: Destination Type
Operator	Here, users can select different operators to add filters. Reference: Filter Operator.
Source Type	Here, you can select the source type from various sources.
Value	Here user can select the value from different Source Type. Reference: Merge Text

Destination Type

Destination Type	Description
Model	From this source, users can select a Model field to be displayed as the destination type.
Variable	Here, users can select the destination type from variables such as Record ID, Is Disabled, Is Read only, or Is Visible.
User	Here, you can choose the label from user fields such as First Name, Last Name, Email, Name, Phone, or Session ID.
Record	It enables to choose record fields as destination type.
Device	It enables user to decide whether the action will be visible on the specific device type or not. Devices supported: Mobile Desktop Tablet

Conditional Disability Type:

Attributes Name	Description
Destination Type	Users can select the destination type from various sources. Reference: Destination Type
Operator	Here, users can select different operators to add filters. Reference: Filter Operator.
Source Type	Here, you can select the source type from various sources. Reference: Available Sources.
Value	Here user can select the value from different Source Type. Reference: Merge Text

Conditional Read Only:

Attribute Name

Description

Read Only Type

It specifies whether a component can be edited by users. It offers the following options:

Never: The component will always be editable at any time.
Always: The component will never be editable.
Conditional: The component's editability is determined based on specific criteria, which can make it either editable or read only as needed.

Add Condition & Group Condition

Condition	Description
Add Condition	The Add Condition feature allows users to define multiple criteria that must be met for a validation rule to trigger. This feature is used to create complex logic by combining different conditions that Salesforce evaluates before allowing a record to be saved.
Add Group Condition	The Add Group Condition feature allows users to group multiple conditions together, creating complex logic that involves different sets of criteria. This feature is particularly useful when combining conditions that should be evaluated as a unit (logical OR within a group) or when nesting conditions for more advanced logic.

Filter Operator:

Note: Before using the filter criteria, it's important to understand which filter operators are supported for each field type

Filters Attributes:

Filter Operators

Operator	Supported Field Types	Description
Equal	Number, Currency, Date, Text, Boolean, Picklist	The equal operator is used to compare two values or expressions. It is used to compare numbers, strings, Boolean values, variables, objects, etc. The result is TRUE if the expressions are equal otherwise it’s FALSE
Contains	Text, Picklist	The contains operator returns TRUE if the value on the left contains the value on the right, and otherwise FALSE
Starts With	Text, Picklist	It returns TRUE if a string or number starts with the specified character otherwise it returns FALSE.
Ends With	Text, Picklist	It returns TRUE if a string or number ends with the specified character otherwise it returns FALSE
In	Text, Picklist	IN operator allows you to easily test if the expression matches any value in the list of values. Determines whether the value of an expression is equal to any of several values in a specified list.

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.

Note: Similarly you can create event action for change event and blur.

on Load Event:

In the image below, you can select the created workflows.

Note: You need to create a workflow for selecting from this list.

For more information about Workflow check this out.

Reference: Workflow

onload Events:

We have an onload event that runs when the component is loaded

For example, when a form is loaded, you can choose fields to be prepopulated by mapping field values using input mapping at the time the form 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.