Overview
Vertical Tabs arranges tabs in a vertical layout, typically on the left side of the canva. This layout allows users to switch between different sections or components vertically, rather than using the traditional horizontal tab format.
With Vertical Tabs, users can add multiple tabs, each representing a different section or category. Clicking on a tab reveals the content associated with that tab while hiding the content of other tabs.
Reference: Tabs
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:
Basic Attribute Name | Description |
---|---|
Component Size |
For example, |
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 to show. For example, |
Show tabs on right checkbox | If this checkbox is selected, the tab location will change from the left side to the right side. |
Base 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 |
|
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. |
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:
Reference: Conditional Visibility |
Component | Component Label | It simply shows the name of the component. |
Conditional Visibility Type:
Attributes Name | Description |
---|---|
Destination Type | Users can select the destination type where the visibility criteria must be applied. Reference: Destination Type |
Operator | Here, users can select different operators to add filters. Reference: Filter Operator. |
Source Type | Here, you can select the source type from various sources. |
Value | Here user can select the value from different Source Type. Reference: Merge Text |
Destination Type
Destination Type | Description |
---|---|
Model | From this source, users can select a Model 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:
|
Conditional Disability Type:
Attributes Name | Description |
---|---|
Destination Type | Users can select the destination type from various sources. Reference: Destination Type |
Operator | Here, users can select different operators to add filters. Reference: Filter Operator. |
Source Type | Here, you can select the source type from various sources. |
Value | Here user can select the value from different Source Type. Reference: Merge Text |
Conditional Read Only:
Attribute Name | Description |
Read Only Type | It specifies whether a component can be edited by users. It offers the following options:
|
Add Condition & Group Condition
Condition | Description |
---|---|
Add Condition |
|
Add Group Condition |
|
Filter Operator:
Note: Before using the filter criteria, it's important to understand which filter operators are supported for each field type
Filters Attributes:
Filter Operators
Operator | Supported Field Types | Description |
---|---|---|
Equal | Number, Currency, Date, Text, Boolean, Picklist | The equal operator is used to compare two values or expressions. It is used to compare numbers, strings, Boolean values, variables, objects, etc. The result is TRUE if the expressions are equal otherwise it’s FALSE |
Contains | Text, Picklist | The contains operator returns TRUE if the value on the left contains the value on the right, and otherwise FALSE |
Starts With | Text, Picklist | It returns TRUE if a string or number starts with the specified character otherwise it returns FALSE. |
Ends With | Text, Picklist | It returns TRUE if a string or number ends with the specified character otherwise it returns FALSE |
In | Text, Picklist | IN operator allows you to easily test if the expression matches any value in the list of values. Determines whether the value of an expression is equal to any of several values in a specified list. |
Events
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.
Add Comment