Overview

Layout component not only helps in structuring the user interface but also allows you to embed one layout within another. This feature, known as a layout within a layout, facilitates more complex and organized designs by enabling the nesting of layouts.

For example, in a application for a customer relationship management (CRM) system, you might have a main layout for displaying customer profiles. Within this main layout, you can embed additional layouts for sections like contact details, activity history, and related opportunities. By using nested layouts, you ensure that each section is well-organized and that data is dynamically passed between layouts, providing a cohesive user experience.

Layout Configurations

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.

Basic:

Basic

Attribute Name	Description

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.
Layout	Here, users have the option to add a previously created layout. This feature allows you to select from layouts that have already been designed and saved,

Base UI :

Base UI

Attribute Name	Description

Attribute Name	Description
Padding Location	`Padding Location` typically refers to the configuration of spacing around elements.
Padding Size	`Padding Size` refers to the amount of space added inside an element, between the element's content and its border or edge.
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.

UI State:

UI State

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

Conditional Visibility Type:

Visibility Criteria

Attributes Name	Description

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

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 All of the Above

Add Condition & Group Condition

Add Condition & Group Conditions

Condition	Description

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

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.

noKodr - For Salesforce

Layout