Where a record is created, and what the control that opens the form should look like #26

New Issue

2026-09-21T07:18:09Z

cgalo5758 commented

2026-09-21 07:18:09 +00:00

The question

Creating a product, an entitlement set or a plan ladder starts in a panel on the list page that asks for identity only, and the rest of the record is filled in on the record's own page. The two sides now share one declared field list, so they cannot drift apart, but the split itself was never decided: whether creation should happen in one place, and whether a panel that opens in place is the pattern to standardize around rather than a drawer, a modal or a page of its own. The opener is part of the same question: it is drawn lighter than the record's main action although it is the page's main action, and while it is open it is drawn pressed, which reads as a toggle. Both together led to the opener being clicked in place of the commit.

What depends on the answer

Every create surface in the operator panel, and the sub-record forms that copied the pattern: adding a price, a tier or a rule, issuing a grant, extending one.

Options known so far

Record creation gets a page of its own, with the list page's opener as that page's one filled call to action; sub-record creation stays inline behind a light opener whose icon turns while it is open, and the rule that draws an open opener pressed is retired.
Every creation stays in place, in a panel or a drawer, with the weight rule corrected.

Published systems size the surface by the creation: inline for something quick and simple, a modal for a couple of fields, a side panel when the work needs the page behind it, a page of its own for a creation the service depends on; they show disclosure with a chevron and never with a pressed button.

Decided when

The design system says which creations get which surface and how the opener is drawn, and the create surfaces follow it.

Migrated from status/issues.md at b7a0e15

## The question Creating a product, an entitlement set or a plan ladder starts in a panel on the list page that asks for identity only, and the rest of the record is filled in on the record's own page. The two sides now share one declared field list, so they cannot drift apart, but the split itself was never decided: whether creation should happen in one place, and whether a panel that opens in place is the pattern to standardize around rather than a drawer, a modal or a page of its own. The opener is part of the same question: it is drawn lighter than the record's main action although it is the page's main action, and while it is open it is drawn pressed, which reads as a toggle. Both together led to the opener being clicked in place of the commit. ## What depends on the answer Every create surface in the operator panel, and the sub-record forms that copied the pattern: adding a price, a tier or a rule, issuing a grant, extending one. ## Options known so far - Record creation gets a page of its own, with the list page's opener as that page's one filled call to action; sub-record creation stays inline behind a light opener whose icon turns while it is open, and the rule that draws an open opener pressed is retired. - Every creation stays in place, in a panel or a drawer, with the weight rule corrected. Published systems size the surface by the creation: inline for something quick and simple, a modal for a couple of fields, a side panel when the work needs the page behind it, a page of its own for a creation the service depends on; they show disclosure with a chevron and never with a pressed button. ## Decided when The design system says which creations get which surface and how the opener is drawn, and the create surfaces follow it. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

design

area/operator-ui labels 2026-09-21 07:18:09 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#26