Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Overview

Repeater is a component used to dynamically display and manage multiple instances of a data set or list of items. It allows you to repeat a specific set of components for each item in a collection, effectively 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.

image-20240816-065153.png

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

image-20240820-073242.png

Attribute Name

Description

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 After

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 After

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

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

  • 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 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.

Visibility and Component

image-20240820-100818.png

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 attribute

Component Label

It simply shows the name of the component.

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

Events

Events available for any component are of onload type.

image-20240818-190902.png

onload

  • onload event occurs when the component has been loaded.

  • Here, only onload event actions are available for components.

  • Actions are basically workflow actions, which you can explore in Workflow here.

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.