Platform · Module
Generative UI
Role- and intent-specific screens generated from certified components
Generative UI creates screens such as "collections view for today" from a declarative spec, using only certified components and design tokens. Generated views respect permissions and never bypass the Action Bus.
Screens on request
Planned for Wave 4, Generative UI lets a user ask Copilot for a screen, for example "collections view for today", and get one built for their role and intent.
Built from safe parts
Screens are described in a declarative UISpec with layout, components and bindings to objects, queries and Actions. The only building blocks are the certified One3 component library and design tokens. That keeps generated screens consistent, accessible and maintainable.
Permission-aware
Rendering respects permissions: fields the user cannot see are masked and Actions they cannot run are hidden. Every button calls a normal Action through the Action Bus. Accessibility checks against WCAG 2.2 AA run before a view can be saved.
Share and maintain
Users preview a generated screen and save it as a View. Role views can be shared to roles or workspaces with admin approval. Views have versions, diffs and rollback, with compatibility checks when an app is upgraded. Brand theming through tokens is white-label aware. Usage analytics that suggest improvements are planned for Wave 5.
How it fits
Generative UI does not replace each app's standard screens. It adds personal and role views on top of them, using the same objects and Actions. Because views are declarative specs rather than code, they survive app upgrades with compatibility checks, and admins can review what a shared view shows before approving it. The approach also replaces the need for a separate low-code screen builder: customers get custom screens without custom code.
Features
What Generative UI includes
UISpec schema
Layout, components and bindings to objects, queries and Actions. W4.
Certified components only
The One3 component library and design tokens. W4.
Generate from intent
Ask Copilot, preview and save as a View. W4.
Permission-aware rendering
Masked fields and hidden Actions where not permitted. W4.
Accessibility validation
WCAG 2.2 AA checks before save. W4.
Shared role views
Shared to roles or workspaces with admin approval. W4.
Versioning and rollback
Diffs, rollback and upgrade compatibility checks. W4.
White-label theming
Brand tokens per tenant or partner. W4.
Workflow
Generate a collections view
- 1
Finance user asks Copilot for today's collections view.
- 2
A UISpec is generated from certified components.
- 3
Accessibility checks run.
- 4
User previews, saves it and requests to share it with the finance role.
- 5
An admin approves the shared view.
AI
AI skills and Digital Employees
Intent to UISpec
Generates validated screens with checked bindings and accessibility.
View improvement suggestions
Uses view analytics to suggest changes. W5.
Digital Employees that use this module
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
Can a generated screen expose data I should not see?
No. Rendering is permission-aware, and every button calls a normal Action through the Action Bus.
Are generated screens accessible?
WCAG 2.2 AA checks run before a view can be saved.
When is it planned?
Wave 4 (Year 3).
See Generative UI in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.