Embedded Widgets
A widget that belongs to a place in the product rather than to a board. Name a slot at the call site, author the thing once, and everybody who opens that screen sees it computed against their own records.
A figure that lives on the billing screen
1 definition, every workspace- Defaulta poll every 60 seconds
- Marked liveevery 5 seconds
- Tab in the backgroundpaused entirely
- Hover refreshskips the cache and reseeds it
- calculation
- modules
- dateFilter
- filters
- groupBy
- tableColumns
- rowLimit
- gaugeTarget
- cacheTtlSec
- isRealtime
- name
- tooltip
- iconKey
- chartVisual
- visualConfig
- themeSetId
- additionalCalculations
- pivotConfig
- crossFilterEmits
- drillThroughTargetDashboardId
The default renderer for its shape, in default colours. A series tile plots its first measure alone and a table tile can never become a grid, because the extra measures and the pivot settings are not read either. No click emission, no hop to another board.
Product figures from the platform’s own defaults - not customer averages
How it works.
The slot is the whole contract
Lowercase letters and digits joined by dots or underscores, two to sixty-four characters, unique platform-wide. The screen asks for a slot by name. Whichever widget carries that name answers, and swapping which widget answers is a rename rather than a code change.
Nothing is copied into the workspace
The definition stays on the platform side and is executed against the connection of whoever asked. One authored definition serves every workspace, and none of them holds a copy that can drift from it.
Deliberately thin authorisation
Any signed-in member may render any slot. There is no board permission to check, because the definition is the operator's and the records are already fenced by whose session is asking. That is the trade being made and it is worth knowing before a sensitive figure is published to one.
How it stays current
A poll every minute, or every five seconds when the definition is marked live, paused entirely while the tab is in the background. A hover button forces a pass that skips the cache and reseeds it.
One moment in every number.
Every number passes through the same seven. Embedded Widgets is the lit one, and everything either side of it is a different page in this category.
- 01Query
what is asked, and of what
- 02Shape
the measure and the dimension
- 03Draw
the visual chosen for that shape
- 04Arrange
where it sits on a dashboard
- 05Filter
narrowing it after the fact
- 06Drill
going from the number to the rows
- 07Share
who else gets to see it
The specifics.
8 facts- Slot
- Two to sixty-four lowercase characters with dots or underscores between segments
- Uniqueness
- One definition per slot, across the whole platform
- Where it renders
- Inside the signed-in product, as a component against a session-scoped endpoint. It is not an iframe, a script tag or anything a third-party site can host
- Presentation
- The chosen renderer, the palette and the presentation settings travel with the definition, so a slot draws the tile as it was authored
- Shape limits
- Extra measures and pivot settings travel too, so a series tile plots all of its measures and a table tile can be a grid
- Interaction
- No click emission and no hop to another board
- Caching
- The widget's own window, keyed by workspace and by a version counter every record write bumps. A window of zero disables it
- Not the same as
- Dashboard Sharing, which hands over a whole board to people who already have accounts
What this is assembled from.
A number on a dashboard was built somewhere before it was drawn. These are the parts it is made of.
More in Reporting & Analytics
12 capabilitiesSeven data shapes, twenty-two visuals, shareable without the portal.
Columns, funnels, treemaps, radar, scatter, gauges and pivots - offered only where the data shape supports them, so no chart can misread its own data.
Build as many as the floor needs, arrange them on a grid, and give each team the one that answers their question rather than everybody's question.
Click a bar and the rest of the dashboard follows it, so the next question is asked by pointing at the answer instead of rebuilding the filter.
Wire a chart's clicks to a second dashboard. The value travels on the URL and is read by the board that was named before it paints for the first time.
Cross one dimension against another with row, column and grand totals - the shape a finance team asks for when a chart will not settle the argument.
Colour a number by the rule that matters - under target, over threshold, inside a band - so a dashboard reads correctly from across the room.
Draw the target on the chart itself, so performance is read against the number that was promised rather than against the shape of the bars.
Put a window against the one before it, or against the same window a week, month, quarter or year back, on a card as a difference or a chart as a series.
Seventeen operators in a nested and-or tree, so the report that needs two exceptions and a date range stays one widget instead of becoming three.
Group by day through year, by equal-width bands, or by breakpoints you set, each band carrying a sort key so the axis reads in bucket order.
Six palettes including a print set, pinned per widget, each carrying eight series colours plus the axis, grid, card and tooltip colours drawn around them.
Total calls, answered rate, average duration and missed calls, split by direction and outcome, over the call records rather than a sampled export.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Reporting & Analytics
See embedded widgets on your own floor.
Thirty minutes, your numbers and your data. We will set embedded widgets up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included