Wizard: View / Query / Security (partial)
Wizard walkthrough · Core Studio 3.0 · Verified 2026-09-01
When to use it: you want the boilerplate of a view (over a query), a query (data sources + ranges), or a security privilege/duty pair scaffolded — then you finish in the editor/designer.
Size: XL · Automatable: PARTIAL — this page says exactly what that means. Partial is a fact, not an apology.
What the wizard generates today vs. what stays manual
| Artifact | Generates today | Manual follow-up |
|---|---|---|
| Query | Valid minimal scaffold: root data source, joined sources (relation-aware where the index allows), coarse fields/ranges | Deep join trees, computed columns, complex ranges |
| View | Scaffold over a picked query + view basics | Field selections, aggregations |
| Security privilege / duty | Privilege basics + entry points (menu-item picks from index), optional duty wrapper | Fine-grained permission matrices, record-level security |
The summary screen explicitly lists what was intentionally left out — you never discover it by accident.
Prerequisites
- For a view: the query exists (or scaffold it first, same wizard).
- For security entry points: the menu items exist (see the Menu wizard).
Steps
- Query: 1. Basics → 2. Root data source (table picker) → 3. Joined sources (relation-aware suggestions where the index allows) → 4. Fields / ranges (coarse) → 5. Summary.
- View: query picker → view basics → summary.
- Security: privilege basics → entry points (menu-item picks from the index) → optional duty wrapper → summary.
Output anatomy
AxQuery/,AxView/,AxSecurityPrivilege/+AxSecurityDuty/artifacts under<root>/<Model>/<Module>/— raw writers, re-indexed, opened in the editor for completion (that handoff is the design, not a gap).
Verify it worked
- Generated artifacts re-read losslessly and compile on-VM.
- The summary’s left-out list matches the items the editor still marks as to-do.
If it goes wrong
- You expected a complete artifact — re-read the table above: this wizard deliberately scopes to minimal-valid output. Chasing designer-grade completeness here was an explicit non-goal.
Next: the Query/View work in the editor, or the fully-automatable wizards (Table, Form).