Repeater
- Content Writers
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.
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:
Attribute Name | Description |
|---|---|
Component Size |
For example, |
Model | Creating a New Model: You can either select an existing model from the list or create a new model by clicking on the 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. |
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. |
Base UI
Base State:
Attribute Name | Description |
Visibility Type | It determines whether a component is visible on the layout. It offers the following visibility types:
|
Header and Footer Actions
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.
|
Visibility Type | It determines whether a component is visible on the layout. It offers the following visibility types:
|
Disability Type | It determines whether a component is disable on the layout. It offers the following visibility types:
|
Label Source Type:
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. |
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. |
Events