Tiles and cards
Tabs of type TilesGrid and CardList pull their content from the Grid linked in the tab via gridUri. Every row of that Grid becomes a tile or a card.
Tile view TilesGrid
A grid of tiles — the typical home screen with quick access to forms and links.
| Field Key | Field type | Required | Description |
|---|---|---|---|
title | Text | yes | Label of the tile |
icon | Files (SVG) | yes | Icon of the tile, single-color SVG |
uri | Weblink | yes | Target of the tile, e.g. a form link |
actionType | Text / Single Select | yes | How the target is opened — see below |
Card view CardList
A list of cards with image, headline, and action button — for news, announcements, or tasks.
| Field Key | Field type | Required | Description |
|---|---|---|---|
headline | Text | yes | Headline of the card |
supportingText | Text | no | Description text under the headline |
image | Files (Image) | no | Image on the card |
actionUri | Weblink | yes | Target of the action button |
actionType | Text / Single Select | yes | How the target is opened — see below |
actionLabel | Text | no | Label of the action button |
createdAt | Date and time | yes | Shown on the card, e.g. as "Today" or "Yesterday" |
Have createdAt fill in automatically
Set the field up as the Created at column type. It's then set automatically for every new entry — including entries created through a form or a Flow. → Column types
Action types
The value in actionType determines how the target is opened.
| Value | Behavior | Tiles | Cards |
|---|---|---|---|
formLink | Opens an ApptiveGrid form in the app, in an embedded web view | ✓ | ✓ |
internalFormLink | Opens an ApptiveGrid form natively in the app, with the app's own input fields | ✓ | ✓ |
internalLink | Opens the page inside the app | ✓ | ✓ |
externalLink | Opens the page in the device's browser | ✓ | ✓ |
triggerFlow | Opens the target in an in-app browser | – | ✓ |
internalLink passes along who's signed in
For ApptiveGrid links, internalLink also passes along the signed-in person. A form filled out through it then carries the correct person in the Created by field, instead of "Form link."
If you need to trace who submitted a report, that's the crucial difference from externalLink.
triggerFlow only exists for cards. It lets you kick off an ApptiveGrid Flow directly from a card. → Trigger a Flow via webhook
internalFormLink instead of formLink
internalFormLink shows the form with the app's native input fields: date picker, camera, location and attachments feel like the rest of the app, and completed forms wait on the device when there is no connection. formLink deliberately keeps the web view so existing tiles keep their behaviour; you decide per row.
Older app versions do not know internalFormLink and drop such tiles and cards. Switch only once your staff has the current app.
Rows with gaps are skipped
As with tabs: if a required field is missing, the tile or card doesn't appear — without any message. If a tile is unexpectedly missing, check the required fields first, then the spelling of the field Keys.
Control order via a sorted View
Tiles and cards appear in the order of the linked Grid. Link a View instead of the Grid, and you control order and visibility through its sorting and filters — for news, for example, sorted descending by date.