Overview

The Icon component is a visual element used to represent actions, objects, or status indicators within the user interface. Icons in noKodr are integrated into various components, serving as symbols that enhance user understanding and navigation.

Here's how icons are typically used in noKodr:

Component Representation: Icons may be used to represent different UI components, making it easier for users to identify and select them when designing a layout.
Action Triggers: Icons can be linked to specific actions, such as saving a form, opening a modal (referred to as "screens" in noKodr), or deleting an entry. These icons are usually placed on buttons.
Status Indicators: Icons might indicate the status of a process or item, such as showing whether a workflow is active, pending, or completed.
Enhancing Visual Appeal: Icons add a visual layer to the interface, making it more engaging and user-friendly by providing quick, recognizable cues.

Attributes:

Attributes are the options available for each component, allowing you to customize its appearance and control their behavior. It includes various sections explained below.

Basic

Attribute Name

Description

Component Size

This allows users to modify the size of a specific component according to the grid size of layout.
This feature allows for flexible customization, enabling users to resize components to fit their specific needs within the defined grid structure.

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.

Icon

This field allows you to choose an icon from different categories like utility, action, custom, doctype, and standard
You can also select the icon size as XX-Small, X-Small, Small, Medium, or Large. Additionally.
A search bar option is available to search for icons by name

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.

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

Component Label

It simply shows the name of the component.

Note: This field displays the name of the component along with the count of its usage. For example, if you add the section for the third time in a layout, it will be labeled "Section 3."

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 component is loaded.

Reference: onload Event

click

This event action is triggered when the icon component is clicked.

double click

This event action is triggered when the icon component is double clicked.

Below here is the onload event workflow action.

note

Note: Similarly you can create event action for click and double click

on Load Event:

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

note

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.