Tiles component attributes
warning
The content on this page is outdated and will not receive updates. For the most up-to-date functionality, refer to Setting up and managing flows.
You can customize tiles components by applying attributes.
Default legacy player runtime
You can apply the following attributes when running flows with the default legacy player.
| Key | Value | Description |
|---|---|---|
classesPage builder: Space delimited css classes | string | Apply CSS directly to the component. The string value can consist of multiple entries to build up a CSS class selector, separated by a space character. See CSS reference.For example, if a custom " .mw-bs .myChosenClassName" style is added to a player (either directly or through a linked stylesheet), this custom style can then be applied to the component using the value "myChosenClassName". |
noResults | string | This attribute allows you to display a custom message on the page if no results are found, such as if there are no tiles to display. |
pagination | boolean | By default pagination is disabled for tiles populated by a list. You can enable it by setting the pagination attribute to true.• true: Enables pagination for tiles populated by a list. Define the size using the paginationSize attribute.• false: Set by default, no pagination is enabled for tiles populated by a list. |
paginationSize | number | If pagination for tiles has been enabled, this attribute allows you to set the number of items displayed on each page (tile). The default value is for 10 tiles to be displayed per page. • Set the value to the number of tiles to display on each page. • Set the value to zero ('0') to display all items (if this is supported by the connector that the tiles component is loading data from). |
Metadata example
This metadata example uses the default legacy player runtime.
"attributes": {
"classes": "myclass1 myclass2",
"pagination": false,
"paginationSize": 10,
"noResults": null
}