User Interface Block
A user interface block represents the screen, form, portal, workflow step, notification, or API surface where users and systems interact with the generated application.
When To Use It
Use a User Interface block when you want generated screens, forms, portals, dashboards, API endpoints, or task surfaces to reflect the model. Interfaces connect actors to commands and queries.
Required Data
- Name: task-oriented surface, such as Claim Review Screen.
- Audience: actors who use it.
- Commands available: actions users can take from the surface.
- Queries used: read models displayed or searched.
- Input fields: data captured before commands are submitted.
Recommended Data
- Workflow position: where this screen sits in the user journey.
- Validation feedback: messages for missing fields or rejected commands.
- Empty and loading states: what users see while waiting or when no records exist.
- Role-specific variations: fields or actions hidden for some actors.
- Navigation outcome: where the user goes after success or failure.
Examples
- Order Checkout: issues Place Order and displays Cart Summary.
- Claims Work Queue: queries Claims Awaiting Review and opens Claim Review Screen.
- Subscription Admin: issues Change Plan, Add Seat, and Cancel Subscription.
- Driver Mobile Stop View: issues Mark Arrived, Capture Proof Of Delivery, and Report Exception.
Generation Notes
Code Genie uses interface blocks to generate routes, forms, buttons, API entry points, validation messages, and page-to-command wiring. Model interfaces around tasks, not generic database tables, unless the system is intentionally CRUD.