Data, dashboards, and live updates
Map database fields, build readable collections and dashboards, and choose how published Pages refresh their data.
Choose the right display #
| Display | Useful for |
|---|---|
| Table | Comparing records in labeled columns. |
| List | A compact collection. |
| Repeater | Repeating a card or other child layout for every record. |
| Dashboard presentations | KPIs, charts, timelines, and status views using mapped fields. |
| Tracking | Looking up one public-safe status using a full reference. |
A Grid arranges child widgets; it does not itself repeat database records. Put a Repeater inside the layout when you need one card per record.
Connect database records #
- Prepare a table in Chatigram Databases with suitable sample records.
- Select a collection widget in Studio. Open Data → Database content and choose the database and table.
- Choose the columns visitors may see and assign display roles, such as Main text. Use visitor-friendly headings for Table columns.
- Choose Use these fields. Review the displayed content and empty state, then save your draft.
- Publish the reviewed mapping and check the published result with non-sensitive sample data.
Connecting a display does not edit the source table. The published revision controls the layout and field mapping; current values come from the connected data. A record update does not require republishing the layout. Changes to the mapping do require saving and publishing.
Treat every mapped field in a public collection as information you are willing to disclose. Search or a visitor-selected filter is a navigation aid, not an access restriction. Collection search and category controls operate on the loaded records; do not assume they search the entire table.
Choose an update mode #
The Update mode setting controls how an open Page reads fresh data. Availability depends on the binding type.
| Mode | Use it for |
|---|---|
| Static | A normal data load without ongoing refresh. |
| Manual refresh | Letting the visitor request an update. |
| Periodic refresh | Reading on a configured interval. |
| On data change | Refreshing an eligible unfiltered collection when changes are detected. |
| Live Push | Updating eligible collections or feeds while the Page is open, with reconnection and fallback checks. |
| On Page refresh action | Refreshing a named collection through a configured Page action. |
Tracking and filtered database sources use the supported manual or periodic options rather than general collection change notifications. Refreshes depend on connectivity, browser visibility, and service availability; avoid promises of instantaneous delivery. Show a useful updated time when freshness matters.
Build a live dashboard #
Use a Table’s Content → Visualization options or an appropriate Library block to present connected values as a KPI, chart, timeline, or status view. Map the label, value, time, and status fields required by that presentation.
For a time series, store observations as separate timestamped records. For a comparison KPI, supply the previous value explicitly. Choose readable units and labels, and provide a useful empty state instead of treating missing data as zero.
Workflow Live Feeds can hold a latest value or recent events. Configure a feed and its declared fields, connect a widget to it, and use the Update Live Feed workflow node to write values. For example, a scheduled workflow can prepare a summary, update a feed, and let a Page display it. A feed update does not start another workflow.
To configure one in Studio:
- Select a compatible collection or dashboard widget and open Data → Workflow Live Feed.
- Choose an existing Live Feed, or open Create a Live Feed. Enter a Feed name and comma-separated Field names.
- Under Store, choose Latest value for one current reading or Recent events for a short activity history. Set the available expiry and event-retention settings for your use case.
- Enable Allow publication on public Pages only if every declared field is safe for public visitors. Otherwise, use a private Page.
- Select the feed, choose its Feed update method, and apply Use this feed. Map its declared fields to the presentation, then save and publish.
In the workflow, select the feed and map values by their declared field names. Test an empty feed and an expired value as well as a normal update. These settings describe the feed's retention and refresh behavior, not additional subscription allowances.
Feeds begin private. Public publication requires intentionally public-safe feed content; private feeds belong on private Pages. Browser updates are not background notifications and do not provide sound alerts. Check the actual availability of these newer controls in your organization before relying on them.
Offer a public-safe tracking lookup #
Use Tracking or the Tracking & Status starter. In Data, choose the table and map distinct reference and status fields. Add only safe details, such as a general progress label and last updated time.
Give each request a securely generated random UUIDv4 reference, and share it through your own appropriate process. The lookup compares the complete reference and returns at most one matching record. Missing, duplicate, or expired references produce no result. It does not write to the source table.
A reference is reusable and may be shared. This feature is suitable for explicitly public-safe status information, not confidential customer details, payment information, or medical records. It is not customer authentication. A conditional “found” panel changes presentation only; hidden content remains public.
Prefill a Page from a link #
Under Page appearance and opening actions → URL inputs, declare the inputs a link may initialize. Configure types, bounds, defaults, and allowed values. A declared input can prefill a form or filter an already publishable collection.
Query parameters do not establish identity, grant permission, or run workflow actions. Keep secrets and personal information out of link parameters. Use a separate authorization process where confidential information is involved.