Overview

The Section component serves as a container that groups content, such as Forms, Tables, Badges, and other components. It provides a structured way to organize and display information within your 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	Description
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 assign a dynamic Header using merge text. Reference: Merge Text
No Header	This checkbox enables users to remove the section's header, creating a streamlined layout without a title or heading.
Is Collapsible	This checkbox allows users to make sections of the application interface collapsible, enhancing the overall user experience.
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. Reference: Actions
Overflow After	It is used to manage the display of actions in a list 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. For Example: If you have three actions, all will be displayed in the section header. If you add a fourth 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 only black borders.

UI

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.

Visibilty, Read Only and Component

Attribute

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

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

Component Label

It simply shows the name of the component.

Merge Text

Merge text is a key feature of the noKodr application, allowing users to display field values on the UI. Depending on the data type, users can perform mathematical operations on these fields.

For example, if you want to display a calculated total price based on the quantity and unit price entered by the user on a sales order form, and you wish to dynamically showcase this on the UI without saving the record in the database, you can achieve this using the UI fields in noKodr.

After selecting merge text you can you can see several options such as:

Attribute Name	Description
Source Type	In this option, you can select various sources from which you want to display values.
Value	The available options will change depending on the selected source type. For example, if you choose "Static" as the source, you can provide a fixed static value.
Merge Field Expression	The selected field from the source will be displayed in a merge format. For instance, the first name field from the contact model will appear as: {model:contact.FirstName}.
Message Body	In this option, You can add multiple values to form your final UI merge text. For example, merge fields include {model:contact.FirstName},{model:contact.LastName} will eventually display the contact's first name and last name next to each other.

Available Sources

After clicking on the Gear Icon, you can select various sources to include fields or values, such as variables, other models, static values, etc.

Source Type	Description
Static	Use this option to provide a fixed static value.
Field	Select the field from the chosen object in the model whose value you want to include.
Model	Choose the field from other models whose value you want to include.
Variable	Select from the variables created in the layout whose value you want to use.
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	You can also select fields from the current logged-in user in your organization to include in the merge. Note: The User source refers to the currently logged-in user in your organization. This means that if you include the First Name field from the user, each time a different user logs in, they will see their own First Name displayed.

After selecting the source type, you need to choose the available options based on the selected type. For example, if you have selected "Model" as the source type, you will need to select one model from the available models.

Note: Only single record models are visible here and can be used in the merge text. Multi-record models are not supported here.

Once you select a model, the field options will become available. You can then choose the fields you want to include in your merge field expression and combine multiple fields to form your final expression in the message body.

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.

Actions:

Header Action Attributes	Description
Label	A Label is the name shown to users and can come from various sources. Reference: Source Type
Name	Enter a unique API name for your action.
Icon	This option lets you choose from various icons to add to the action button.
Variant	This feature allows users to change the appearance of the action button. You can explore more about variants here.
Visibility Type	It determines whether a component is visible on the layout. It offers the following visibility types: Never: There component will never be visible. 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 Conditional Visibility Type attribute here.
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 disabled. 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 Disability Type attribute here.

Variants:

Variant	Description
Neutral	Neutral is the default variant of the Action which is displayed in white color.
Brand	Brand variant is a blue color.
Outline-brand	Outline-brand is like the brand variant, but the color is used for the label and border only, not the whole Action color.
Destructive	Destructive variant is in a red color. Note: It is usually used to group buttons which depict actions which warn the user.
Success	Success variant is in a green color. Note: It is usually used to group buttons which depict successful action.

Conditional Visibility Type:

Destination Type	Description
Model	From this source, users can select a Model (Salesforce Object) 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:

Destination Type	Description
Model	From this source, users can select a Model (Salesforce Object) 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 disabled on the specific device type or not. Devices supported: Mobile Desktop Tablet

Events:

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.

Actions are basically workflow actions, which you can explore in Workflow here.

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.