Problem
SDUI pages need to compose real object-backed slices of the application, not static cards or hand-written Cloud-specific widgets. Today ObjectUI has an object-view renderer and a lower-level list-view, but neither is a clean fit for a compact home-page widget.
For ObjectStack Cloud, the home page should show a customer journey: My environments, create environment, templates, members, and usage. The "My environments" section should reuse the existing sys_environment.my_environments view in a compact card/section, not duplicate list config or expose the full object-management surface.
Current Observations
object-view exists and can be rendered from schema, but it behaves like a full object management interface.
list-view can be embedded directly, but authors must duplicate object/view fields, filters, empty state, permissions, row actions, and view semantics.
- Pages need a way to reference an existing object view by
objectName + viewName and render it as a page section.
Proposed Direction
Enhance the existing object-view renderer, or add a generic object-view-embed wrapper, with compact page-embedding semantics.
Suggested schema shape:
{
type: 'object-view',
objectName: 'sys_environment',
viewName: 'my_environments',
variant: 'compact',
maxRows: 5,
showToolbar: false,
showViewSwitcher: false,
showCreate: false,
emptyState: { ... },
actions: [...]
}
The component should resolve the named view from metadata and preserve its filters, fields, empty state, permissions, row actions, and navigation behavior.
Acceptance Criteria
- A page schema can embed an object-backed section by referencing
objectName and viewName.
- Compact mode suppresses full object-management chrome while keeping useful row rendering and row actions.
- Authors do not need to duplicate columns/filters from the named object view.
- Empty states and loading states are suitable for a home page section.
- Embedded lists can cap rows with
maxRows and optionally expose a "View all" navigation affordance.
- Works with field permissions, row actions, and view-specific filters.
- Add tests covering view resolution, compact rendering, empty state, and maxRows behavior.
Related
Problem
SDUI pages need to compose real object-backed slices of the application, not static cards or hand-written Cloud-specific widgets. Today ObjectUI has an
object-viewrenderer and a lower-levellist-view, but neither is a clean fit for a compact home-page widget.For ObjectStack Cloud, the home page should show a customer journey: My environments, create environment, templates, members, and usage. The "My environments" section should reuse the existing
sys_environment.my_environmentsview in a compact card/section, not duplicate list config or expose the full object-management surface.Current Observations
object-viewexists and can be rendered from schema, but it behaves like a full object management interface.list-viewcan be embedded directly, but authors must duplicate object/view fields, filters, empty state, permissions, row actions, and view semantics.objectName + viewNameand render it as a page section.Proposed Direction
Enhance the existing
object-viewrenderer, or add a genericobject-view-embedwrapper, with compact page-embedding semantics.Suggested schema shape:
The component should resolve the named view from metadata and preserve its filters, fields, empty state, permissions, row actions, and navigation behavior.
Acceptance Criteria
objectNameandviewName.maxRowsand optionally expose a "View all" navigation affordance.Related
sys_environment.my_environmentson the Cloud home page.