Manage window actions, server actions, QWeb views, menu hierarchies, and paper formats

Views is the registry of every screen's XML. The form itself carries the warning that matters: edits to a standard view are overwritten during future module updates — extend through an inherited view instead. Inheritance has rules of its own (an extension-mode view must name its parent; a parent cannot be deleted while children inherit; groups go inside an inherited view's XML, not on its record), the architecture editor validates as you type and refuses genuinely broken XML with messages like "You cannot create recursive inherited views.", and the developer toolbar's Reset View Architecture can restore the previous saved version (soft), re-read the module's file from disk (hard), or diff against another view. Customized Views is quieter than its name: the per-user store of personally rearranged list layouts — on this database a handful of users' sale-order, picking, task, and invoice lists — delete a row and that user's personal layout resets.

Menu Items lists the whole menu tree, including what the app switcher hides. Two behaviours matter: a menu with no groups is not public — visibility falls back to read access on the action's model; and deleting a parent menu does not delete its children — they are promoted to top level, so tidy the subtree before removing its folder.

User-defined Filters stores every saved search. On this version a filter is shared with a set of users (Shared with) — and an empty set means it is shared with everyone, which is how a personal experiment ends up on the whole company's screens. Nothing enforces uniqueness: two favorites can carry the same name, and several can be flagged as default for the same screen — this list is the only place to spot and tidy that. Onboardings and Tours list the first-run banners and guided tours that have database state — the Tours list only shows tours that have been consumed or recorded, so it understates what the client actually ships.

Every PDF in the system is shaped by a Paper Format: page size (A-and-B series, Letter, Legal, or custom with explicit width and height), orientation, the four margins, Header spacing (the gap reserved for the repeating header — independent of the top margin, and only equal to it when a format wants the header flush), a header rule line, output DPI, and smart-shrinking control. Thirteen formats live on this database: the stock A4 and US Letter, and eleven WindoorERP-specific ones — label sheets, the ID badge, the CV, the survey reports, the landscape glass list — where margins and header spacing are deliberately tuned per document.

The Reports screen (the same screen under both Actions and Reporting) is where a printed document is wired up: its QWeb Template Name, its type (PDF, HTML, or text), its Paper Format (shown for PDF only; empty means the company default), a Printed Report Name expression that builds the download filename from the record, Add to the 'Print' menu, an optional domain restricting which records offer it, and Reload from Attachment to reprint the stored copy instead of regenerating. The Qweb Views button is a name search, not a stored link — an empty result there does not mean the template is missing.

The Technical menu is missing entirely — Developer Mode is off; no access right substitutes for it.

The Python code box is missing on a server action — the code field requires the Administrator right on top of Developer Mode.

"Server action … has one or more warnings, address them first." — the action saved with its yellow banner unresolved; fix what the banner names, then run again.

A view refuses to save — the message quotes the offending rule verbatim (recursive inheritance, a missing name on a field tag, a page outside a notebook, a QWeb view without a key); fix the XML it points at, and prefer an inherited view over editing the original at all.

A saved search appears for every user — its "Shared with" list was left empty, which means shared with everyone; add the intended users to the list, or delete the row.

A hand-edited standard screen reverted overnight — a module update re-shipped the view, as the form's own warning promises; rebuild the change as an inherited view.

Looking for "Automated Actions" — that module is not installed on this build; the Automation menu holds Scheduled Actions only.