/
Repeater

Repeater

Overview

The Repeater component is used to dynamically display and manage multiple instances of a data set or list of items. It repeats a specific set of components for each item in a collection, creating a list or grid of repeated elements.

Here’s how a Repeater typically functions in noKodr:

  • Data Binding: The Repeater is bound to a data source, such as a list of records from a Salesforce object or an external data source.

  • Template Layout: You define a template layout, which could include components like text fields, images, or buttons. This template is repeated for each item in the data set.

  • Dynamic Rendering: The Repeater dynamically renders the repeated items for each record in the data collection, allowing users to see and interact with multiple records simultaneously.

  • Customizable: You can customize the appearance and behavior of the repeated items, adding actions, styles, or conditional logic as needed.

The Repeater is particularly useful for displaying lists of records, product catalogs, or any other scenario where you need to present multiple items in a consistent, repeated format within the noKodr application.

repeater.png
Repeater Configurations

Attributes

The Repeater component is used to dynamically display and manage multiple instances of a data set or list of items. It repeats a specific set of components for each item in a collection, creating a list or grid of repeated elements.

Basic:

image-20250320-112759.png
Basic

Attribute Name

Description

Attribute Name

Description

Component Size

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

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.

Model

Creating a New Model: You can either select an existing model from the list or create a new model by clicking on the Create New Model option for your Repeater.

Note: The Repeater requires multiple records, so select multi-record model.

Header Actions

You can include multiple header actions.

Reference: Header Action

Header Overflow

This feature allows you to control the number of actions displayed. Setting the limit to 1 will show only one action, with additional actions appearing in a drop-down menu.

Footer Actions

You can include multiple Footer actions.

Reference: Footer Action

Footer Overflow

This feature allows you to control the number of actions displayed. Setting the limit to 1 will show only one action, with additional actions appearing in a drop-down menu.

UI State:

image-20240925-132444.png
UI State

Attribute Name

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 Visibility Type here

Base UI

image-20250320-113718.png
Base UI

Attribute Name

Description

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.

Header and Footer Actions

image-20250320-114018.png
Header Action

Attributes

Description

Attributes

Description

Label

A Label is the name shown to users and can come from various sources.

Name

Enter a unique the 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.

  1. Neutral

  2. Brand

  3. Outline Brand

  4. Success

  5. Destructive

Visibility Criteria

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

  1. Show: The action will always be visible.

  2. Hide: The action will never be visible.

  3. Conditional: The action 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.

Disability Criteria

It determines whether an action is disabled on the layout. It offers the following visibility types:

  1. Show: The action will always be visible.

  2. Hide: The action will never be visible.

  3. 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 Disability Type here.

Label Source Type:

image-20240813-133213.png

 

Attribute

Description

Attribute

Description

Model

From this source, users can select a Model 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.

Reference: Variable

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

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

Merge Field Expression

Merge Field Expression displays the value selected from the chosen value source.

Message Body

Inside the message body, user also can add the values manually.

Note: After adding fields to the form, you can configure specific fields. The table below shows all available attributes.

Conditional Visibility Type:

image-20240814-092607.png
Visibility Criteria

Attributes Name

Description

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

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:

  1. Mobile

  2. Desktop

  3. Tablet

  4. All of the Above

Add Condition & Group Condition

image (21)-20240822-182312.png
Add Condition & Group Conditions

Condition

Description

Condition

Description

Add Condition

  • The Add Condition feature allows users to define multiple criteria that must be met for a validation rule to trigger.

  • This feature is used to create complex logic by combining different conditions that Salesforce evaluates before allowing a record to be saved.

Add Group Condition

  • The Add Group Condition feature allows users to group multiple conditions together, creating complex logic that involves different sets of criteria.

  • This feature is particularly useful when combining conditions that should be evaluated as a unit (logical OR within a group) or when nesting conditions for more advanced logic.

Filter Operator:

Note: Before using the filter criteria, it's important to understand which filter operators are supported for each field type

Filters Attributes:

image-20240822-134925.png

Filter Operators

Operator

Supported Field Types

Description

Operator

Supported Field Types

Description

Operator

Supported Field Types

Description

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.

Note: When adding different components inside the Repeater, it will display the configuration options for those components.

Events

 

Related content