Onepager

A Onepager is a saved View containing resource-list boxes on one A4 landscape canvas. Each box combines a resource selection, ordered property fields, a local filter, and an item limit. It is an interactive project overview, not a document editor or a PDF export tool.

The fictional Product Atlas fixture contains Products / Lumen devices with Aster Mini and Aster Pro, and Products / Orbit devices with Orbit Dock and Orbit Hub. Markets contains Northland, Westhaven, and Eastreach. Features contains Wireless sync, Compact chassis, Offline mode, and Extended battery. Products have Launch ready, List price, and a multi-reference Included features field anchored to the Features Class.

Access And Modes

Project Viewers can inspect permitted results. Project Analysts can create Views and change Views they created; Editors and higher can change other saved Project Views. Saving a View remains subject to server checks, even if controls are visible.

The Onepager temporarily disables layout changes and reference drops while project results are stale or refreshing. Wait for reconciliation before editing. This UI state is separate from the server's saved-View permission checks; selecting a linked resource in Details does not itself lock the whole Onepager.

Edit layout changes boxes, not project field values. Preview presents calculated rows and permits eligible reference drops. Reference data changes require Editor rights on the Project or an authorized active Layer; an Analyst's right to save a View is not a right to change its product references.

Layer-only access stays in the selected permitted Layer. It does not expose All data or grant unrestricted Project View administration. Linked and shared read-only intersections cannot be changed through a Onepager.

Create A Onepager

1. Open Product Atlas and show the View pane.
2. Choose Add view, enter Product release overview, and select Onepager.
3. Create the View and wait for it to appear in the View selector.
4. Choose Edit layout.
5. Choose Add box or Add first box on an empty canvas.
6. Select the box and choose Configure.
7. Enter Products as the Box title.
8. Select Lumen devices and Orbit devices under Resource roots, using Children for each.
9. Select Launch ready, List price, and Included features under Property fields.
10. Set Item limit to 10 and choose Apply.
11. Set the page as-of date to October 1, 2026, inside Scale. Choose Preview and inspect the rows.
12. Use the View pane's Save view action to persist the layout and source configuration.

Expected result: one box lists eligible product Values with those fields. Apply changes the current View draft; Preview changes the editing mode. Neither substitutes for Save view.

Creating another Onepager from an active Onepager uses its current draft as the starting configuration. Creating a Onepager while another View type is active starts a default Onepager. A saved View cannot be converted to a Table or Timeline later; create another View instead.

Configure A Resource List

Choosing Children under Products selects Lumen devices and Orbit devices, not the four product Values beneath them. Choose each device group / Children for the four product rows. A broader descendant scope includes deeper eligible resources as well as intermediate groups. Review the actual tree when choosing a scope.

Property families retain their identity when renamed centrally. A field missing on one resource does not become a new field automatically just because it is included in a box. The display preserves configured field slots and distinguishes Missing from Unset. Missing means there is no applicable value/field data for that slot; Unset means an existing visible value has no content.

Formatted-text output is visible plain text. A Onepager does not render a field's stored formatting as an embedded rich document.

Arrange The Canvas

The page is fixed at 297 x 210 mm with a 10 mm safe area. Layout dimensions are saved in millimetres, so zooming does not change the persisted page geometry.

1. Enter Edit layout and select one box.
2. Drag it to the intended location and use its resize handles to adjust its dimensions.
3. Align with the page safe-area guides, the 5 mm grid, or other boxes' edges.
4. Use Duplicate box to make another configured list.
5. Use Bring forward or Send backward when boxes overlap.
6. Use Delete box to remove the selected layout element.
7. Choose Preview and inspect content fit, then save the View.

Expected result: geometry remains inside the safe area. Deleting a box does not delete its listed resources, fields, or values. Duplicating a box creates a separately configurable source rather than another product record.

Use Fit page, Zoom in, and Zoom out to inspect layout. Zoom is workspace presentation state, not a saved page setting. The current editor supports one selected box, not multi-selection, rotation, arbitrary page sizes, or multiple pages.

A row limit is not a guarantee that all rows fit physically. Box content is clipped to its frame; enlarge the box, reduce selected fields or candidates, or split the overview. When the returned row set exceeds the item limit, a more count reports omitted rows; a physically clipped count or row is still possible in a box that is too small.

Page, Box, And Layer Context

The top-level View filter is the page filter. The filter in Configure is specific to that box. The active Layer comes from the project header and is not saved inside the Onepager.

The effective rule is:

active Layer AND page filter AND box filter

Positive Class selections can produce separately labelled rendered contexts. For example, a Markets filter for Northland OR Westhaven can render two contextual sections rather than pretending both market-specific prices are one unconditional price. Conditions are evaluated for each context on the server.

An AND requiring two contradictory Values from the same Class produces no compatible Class context. OR retains alternative contexts. Do not diagnose an empty box solely by counting stored resources; inspect the complete rule combination.

The As of date chooses applicable snapshot data. Selecting a different snapshot in Details does not update this date. See Snapshots for Active/Inactive and untagged priority.

Worked Product Atlas Overview

1. Set the page filter to Markets any Northland.
2. Configure a box using Lumen devices / Children and Orbit devices / Children, containing List price and Included features.
3. Configure a second box using Essentials / Children and Advanced / Children under Features. Leave its property fields empty if you only want feature labels; the fixture has no feature-owned Status field.
4. Inspect Aster Pro's existing Scale conditions: Northland launch price is 229 and its matching Launch campaign child is 219; the global default is 249.
5. Set the page as-of date to October 1, 2026, and enter Preview.

Expected result: the product box displays Northland-context data, including 219 for Aster Pro in the unchanged fixture. Its Included features contains Wireless sync, Extended battery, and the conditioned Offline mode. The feature box uses the same page context but its own candidate selection. Removing the page filter returns to All data calculation unless a Layer or box filter still supplies context.

Click a resource label or field to open its Details. A linked candidate is evaluated in its destination context while reading original data, and opens read-only linked Details. Opening the original is a separate action, subject to access.

Change A Reference By Dropping A Resource

Reference drops are a specific write interaction available in Preview, not a general inline editor.

1. Leave Edit layout by choosing Preview and wait for any pending project calculation.
2. Find Aster Pro's writable Included features field in the Products box.
3. Drag the canonical Compact chassis Value from Features / Essentials onto that exact reference field.
4. Wait for the pending write and recalculated result.
5. Inspect Aster Pro's corresponding snapshot and condition/default in Details to confirm where the change was stored.

Expected result: Included features appends Compact chassis. For a separately authored single-reference field, the same interaction replaces its prior selection with Compact chassis. Dropping a target already in the effective multi-reference set makes no additional change.

The target must be an active eligible resource below the field's anchor Class. The Class itself, an inactive target, or a resource from another anchor branch is rejected. Dropping on a scalar field, a read-only or linked row, or an obsolete intersection is rejected. The application rechecks the displayed frame, context, resource, field, and snapshot before writing.

Where The Drop Is Saved

A page with Northland selected is not an unconditional write surface merely because the Layer selector says All data. Page and box filters also determine where the reference edit belongs.

For a new contextual multi-reference condition, the app uses Change / Add. It preserves inherited dynamic selections instead of flattening them into a fixed replacement. If an exact contextual condition already exists, its Replace or Change mode is preserved and the stored condition is extended. A single-reference contextual drop uses replacement semantics.

Worked Contextual Drop

Aster Pro's default Included features contains Wireless sync and Extended battery. For an independent exercise, set the Onepager page filter to Eastreach, keep an as-of date in Scale, then drop Compact chassis on Aster Pro's Included features field in Preview.

Expected result: Eastreach contains Wireless sync, Extended battery, and Compact chassis through a contextual addition. The global default stays unchanged. Northland retains its existing Offline mode addition, and Westhaven retains its Extended battery subtraction. If an exact Eastreach condition previously used Replace with Offline mode in an additional exercise, the drop extends that replacement to Offline mode and Compact chassis instead. These drops modify the fixture; they are not part of its initial seeded state.

Layer Editors can make permitted contextual drops only within their authorized Layer. They cannot use this interaction to change the global default. See Conditions for reference cascading.

Troubleshooting And Limits

Current request limits include 24 data sources, 48 elements, 24 roots and 24 fields per source, and an item limit of 1-100 per source. Broader context/reference expansion can still exceed an evaluation budget before those maxima. Narrow the request rather than relying on a partial result.

Only configurable resource-list boxes are available. There is no built-in printing/PDF export, static-text block, chart, image block, multi-selection, rotation, or general in-place scalar editor. Reference drops are real data writes; saving the layout is not required to make a successful drop persist, and deleting the box does not undo the drop. The current Preview-drop workflow returns no Undo receipt and clears the global Undo entry on success. See Undo for receipt-supported operations.