Overview
Tabs refer to a navigation element that allows are a group of tab component used to navigate and allow users to switch between different views or sections within the same layout. Each tab represents a different distinct section or category, and clicking on selecting a tab displays the content associated with that tab its associated content while hiding the content of other tabs.
Tabs are often used to help organize content into manageable chunks, making it easier for sections, enabling users to navigate and find access information efficiently without having to load loading new pages or screens.
...
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 Name
...
control their behavior. It includes various sections explained below.
Basic:
...
Attribute Name | Description | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Component Size |
| |||||||||||
Layout Type | It is used to set the layout type in two ways as:
Note: By default, this attribute is set to a value of Grid Layout Type. | |||||||||||
Default Tab | If you have multiple tabs, select the number to set the default tab. | |||||||||||
Overflow Limit | This feature lets you control the number of tab. Setting the limit to 1 will show only one tab, with other appearing in a dropdown menu. |
Base UI
...
:
...
Attribute Name | Description | ||
|---|---|---|---|
Component Size |
| ||
"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 |
| ||
Classes |
| ||
Layout Type | It is used to set the layout type in two ways as:
| ||
Visibility Type | It determines whether a component is visible on the layout. It offers the following visibility types:
| ||
Component Label | It simply shows the name of the component. |
Visibility and Components Attributes:
...
UI State:
...
Attribute Group | Attribute Name | Description | |||||
Visibility | Visibility Type | It determines whether a component is visible on the layout. It offers the following visibility types:
| Component | Component Label | It simply shows the name of the component
|
| Include Page | ||||
|---|---|---|---|---|
|
...
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.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
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
...
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.
| Info |
|---|
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.
| Info |
|---|
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. |
...
Note: After clicking inside the tab section on the layout, you will see the tab configuration.
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.
...
| Info |
|---|
Note: "You need to create a workflow for selecting from this list. |
For more information about Workflow check this out.
| Info |
|---|
Reference: Workflow |
onload Events:
We have an onload event that runs when the component is loaded
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
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.
...
| Include Page | ||||
|---|---|---|---|---|
|