Versions Compared

Version Old Version 23 New Version Current
Changes made by

Content Writers

Content Writers

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

The Section component serves functions as a container that groups contentfor grouping other components, such as Forms, Tables, and Badges, and other components. It provides a structured way method to organize and display information within your the application.

...

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

...

Attribute

...

control their behavior. It includes various sections explained below.

Basic:

...

Attribute

Description

Component Size

  • This allows users to modify the size of a specific component according to the grid size of layout.

Panel
panelIconId1f5e8
panelIcon:speech_left:
panelIconText🗨️
bgColor#F4F5F7

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 Type

It is used to set the layout type in two ways as:

  1. Grid: The Grid type divides a component into a specified number of columns. The grid size determines the number of available columns.

  2. Flow: The Flow Layout Type is used for positioning and formatting components within a layout. This layout type allows components to be positioned in relation to each other.

Note: By default, this attribute is set to a value of Grid Layout Type.

Grid Size

It defines how many columns you want to divide the component into.

Panel
panelIconId1f5e8
panelIcon:speech_left:
panelIconText🗨️
bgColor#F4F5F7

For example, if you set the grid size to 3 for a component, you can arrange the content inside it across three columns.

Header

This field allows users to add a title or heading to the section, providing context or description for the content within the section. You can also assigned Header using merge text.

Info

Reference: Merge Text

No Header

This checkbox enables users to remove hide the section's header.

Is Collapsible

This checkbox allows users to make sections of the application interface collapsible.

Actions

This allows users to add multiple actions to a section, each represented as a button. It enables users to quickly perform specific actions or invoke workflows directly from the section header.

Info

Reference: Actions

Overflow After

It is used to control the display of actions If the number of actions exceeds the provided limit, the additional actions will be displayed in a dropdown format within a section header.

Note: By default, this attribute is set to a value of 3, meaning that up to three actions will be directly visible in the section header.

Panel
panelIconId1f5e8
panelIcon:speech_left:
panelIconText🗨️
bgColor#F4F5F7

For example, if you have 3 actions, all will be displayed in the section header. If you add a added the 4th action, it will appear in the drop-down list, along with any subsequent actions.

Show Border

It is used to simply add border surrounding the section.

Note: Currently, we support noKodr supports only black borders.

UI

...

State:

...

Attribute

Description

Visibility Type

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

  1. Always: The component will always be visible.

  2. 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 conditional visibility

Note: By default, Visibility Type is set as Always.

Info

Reference: Conditional Visibility.

Read Only Type

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

  1. Never: The component will always be editable at any time.

  2. Always: The component will never be editable.

  3. 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 conditional visibility

Info

Reference: Read Only.

Component Label

It simply shows the name of the component.

Base UI:

...

Include Page
UI Attributes
UI Attributes

Include Page
Merge Text Config
Merge Text Config

Source Type:

Label Source Type Attribute

Description

Static

It includes only records from the manually input value.

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

By using the Cookie Key, the result is fetched by the value that has been added under the Cookie Key. But, have to make sure that the value that we are adding is from the Cookie Key value.

Local Storage Key

By using the Local Storage Key, the result is fetched by the value that has been added under the Local Storage Key. But, have to make sure that the value that we are adding is from the Local storage value.

User

Here, you can choose the label from user fields such as First Name, Last Name, Email, Name, Phone, or Session ID.

...

Include Page
Visibility and Disability
Visibility and Disability

Events:

Include Page

In noKodr, Events define the triggers for automation created by workflows. They determine when a specific workflow should be executed based on user interactions or changes in the application.

...

onload Events:

  • This triggers the assigned workflow every time the component is loaded.

...

Events (Common)
Events (Common)

Custom Action Event:

This event changes as you create new actions for the component. For example, in the image below, I have created a custom action called “New Candidate.” The event associated with this action is visible, which means that whenever you click on this action, the assigned workflow will be triggered.

...