feat: full workspace creation with route, menu, and default screen#42
Merged
Conversation
- Auto-create sys_ux_page_registry with slugified path and app shell - Auto-link workspace to Workspaces menu via sys_ux_registry_m2m_category - Auto-create Home screen type and Default Home screen - Lookup default references by name (Workspace App Shell, Unified Navigation, Workspace category) - Return workspace URL in output Closes #34
The Next Experience router requires sys_ux_app_route records to map URL segments like /home to screen types. Without routes, the workspace URL returns 404. - Add sys_ux_app_route creation with route_type=home - Link route to Home screen type and Workspace App Shell - Use consistent 'Home' naming for screen types Closes #34
The Next Experience framework requires sys_ux_page_property records to render a workspace. Without them, the URL returns a redirect to login (the framework recognizes the route but can't render it). - Add chrome_header, chrome_footer, chrome_toolbar, chrome_tab - Set unique_name with scope prefix pattern - Auto-detect scope prefix from sys_ux_app_config sys_scope Closes #34
The screen needs a custom macroponent extending Page Template in the same scope, not a reference to a global component. Without it, UI Builder shows 'The variant record lacks a page definition'. - Create custom sys_ux_macroponent extending Page Template - Use custom macroponent on Home screen instead of Dashboards - Add sysId prop to macroponent and config Closes #34
The custom macroponent had an empty composition, causing 'no content available'. Embed a Heading component with a welcome message so the page renders actual content. - Look up Heading component by name - Include it in composition and layout - Personalize label with workspace name Closes #34
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
1 participant
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.
Closes #34
Changes
workspace createnow bootstraps a fully functional, navigable workspace:sys_ux_app_config— workspace configurationsys_ux_page_registry— URL route with slugified path, app shell, and parent appsys_ux_registry_m2m_category— registers workspace in the Workspaces menusys_ux_screen_type— Home screen collectionsys_ux_screen— Default Home screensys_ux_app_route— maps/hometo the Home screensys_ux_page_property(×4) — chrome_header, chrome_footer, chrome_toolbar, chrome_tabsys_ux_macroponentextending Page Template with a Heading component/now/<path>/home) in outputUsage
After creation, the workspace appears in the Workspaces menu in the Unified Navigator and renders a welcome heading on the home page.