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.

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
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,

UI Attributes:

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.
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 component, if needed.
Flow Type	It specifies the arrangement of content within the section, allowing users to choose between different layout flows as ‘Fit to content’ or ‘Equally distributed’.
Show Border	It is used to simply add border surrounding the section. Note: Currently, noKodr supports only black borders.

Visibility and Component Attribute:

Attribute Group

Attribute Name

Description

Visibility

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 attribute

Component

Component Label

It simply shows the name of the component.

Events:

Events are essentially the automation of invoking the component's actions.
Here, only onload event actions are available for this components.

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 Event:

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.

Layout