feat(app-showcase): Account 360 record page + Delivery Operations dashboard - #2059
Merged
Merged
Conversation
…hboard
Two flagship composed enterprise surfaces — moving the showcase beyond
atomic "one-of-everything" fixtures toward realistic, multi-capability
pages a developer would actually build.
Account 360 (showcase_account_detail, the account object's first record
page) — exercises the related-data + collaboration blocks nothing in the
showcase used before:
• record:related_list — Projects and Invoices as live child lists
• record:history — the audit-trail tab
• the synthesized discussion slot — activity + comment feed (@mentions)
• record:highlights + record:details (Company / Billing sections)
Highlights and details deliberately use *disjoint* fields: record:details
dedupes highlight fields and hide-empties the rest, so reusing the same
fields (as a first draft did) collapses every section to empty. Account
seed enriched with tax_id + billing_email so the Billing section renders.
Delivery Operations (showcase_ops_dashboard) — a believable ops landing
page vs the one-of-every-chart Chart Gallery:
• KPI hero row of metric tiles, each scoped by a per-widget filter
(active projects / at-risk / awaiting-review) — one dataset sliced
different ways
• health column + status bar + priority donut + throughput line + spend
table
• global dateRange (created_at) + global status filter
showcase_project_metrics gains status + health dimensions to power it.
Both wired into nav (Analytics → Delivery Operations) and registered in
objectstack.config. Verified in the browser (:5181): KPI filters resolve,
charts render, the Account tabs (Details / Projects / Invoices) and
discussion feed all populate. typecheck + 20 showcase tests pass.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
os-zhuang
added a commit
that referenced
this pull request
Jun 20, 2026
… wizard (#2060) Three more composed enterprise surfaces (part 2 of the set begun in #2059), each exercising SDUI capabilities the showcase hadn't surfaced as real pages. My Work (showcase_my_work, type:home) — a role-aware workspace that composes LIVE data rather than one-component-per-type: • KPI hero row of live `object-metric` tiles (Open Tasks / In Review / At-Risk Projects) — async aggregates with per-tile filters; • a personal work queue: `object-grid` filtered to the signed-in user via the `{current_user_id}` token (records I own); • a role-gated card (`properties.visible` CEL) only the admin sees — demonstrating per-user differentiated rendering. Approvals (showcase_review_queue, type:list) — the human side of the ~20 approval/review flows: an interface page over tasks `in_review` (the work awaiting a decision), the source object's action surfaced as a toolbar button ("Mark done" = approve & complete), drawer to inspect before deciding. New Project Wizard (showcase_new_project_wizard) — `object-form` with `formType:'wizard'` + step indicator: Basics → Status & Health → Budget, the first page to actually walk a stepped create flow. All three wired into nav + objectstack.config. Browser-verified (:5181): My Work KPIs resolve (8 / 2 / 1) and the owner-filtered queue + role card render; Approvals shows the 2 in-review tasks with the approve button; the wizard navigates Basics → Status (Step 2 of 3). typecheck + 20 tests pass. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jun 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The showcase is a thorough atomic fixture (one-of-every field / chart / flow), but thin on composed, realistic enterprise surfaces a developer would actually build. This adds the first two flagship surfaces.
What
Account 360 —
showcase_account_detailThe account object's first record page, and the first to exercise the related-data + collaboration blocks nothing else used:
record:related_list→ Projects and Invoices as live child listsrecord:history→ audit-trail tabrecord:highlights+record:details(Company / Billing sections)Delivery Operations —
showcase_ops_dashboardA believable ops landing page (vs the one-of-every-chart Chart Gallery):
metrictiles, each scoped by a per-widget filter (active / at-risk / awaiting-review) — one dataset sliced different waysdateRange+ global status filtershowcase_project_metricsgainsstatus+healthdimensions to power it.Verification
Browser-verified on
:5181: KPI per-widget filters resolve (Active 2 / At-Risk 1 / Awaiting Review 2 / Budget $1.09M), all charts render, the Account tabs (Details / Projects(2) / Invoices) and the discussion feed populate.typecheck+ 20 showcase tests pass.Wired into nav (Analytics → Delivery Operations) and
objectstack.config.Part 1 of the enterprise-surfaces set; My Work home / Approvals inbox / wizard / settings to follow.
🤖 Generated with Claude Code