Card Designer: Request Wide Card

A request shows up as a small card almost everywhere it's listed. In the queue split-view the card sits in a narrow left pane, so it stacks its information vertically. But Aeon also lists requests in places with much more horizontal room — the Requests tab on a user record, an activity's requests, a bundle, or an appointment. In those embedded lists Aeon uses a wide version of the request card that spreads its fields across the row instead of stacking them.

The Request Card (Wide) designer is where you control that wide layout. It's the same drag-and-drop tool as the standard Card Designer: Request Card — the difference is which layout it edits and where that layout shows up. Most of the time you set the wide card up once, alongside the queue card, so requests look consistent throughout the app.

When you'll use this

• You've customized the queue request card and want the embedded lists (user, activity, bundle, appointment) to match — those use the wide layout, configured here.
• A request looks cramped or sparse when it appears on a user record or activity, and you want to add or remove fields for that wider context.
• You want a different field on one queue's wide cards — for example, surfacing the requested format or a custom field on requests in a particular queue.

Wide card vs. queue card — two separate layouts

The queue request card (narrow) and the wide request card are stored and edited independently. Changing one does not change the other. If you want them to match, you'll set both up — this page covers the wide one. They share the same field palette and the same designer controls, so once you've used one, the other is familiar.

Where the wide card appears

The layout you build here renders wherever requests are listed in a wide container:

• The Requests tab on a user record.
• The requests list on an activity.
• Requests grouped into a bundle.
• Requests tied to an appointment.

The narrow queue list is not affected — that's the standard request card.

Opening the designer

1. Open Customization Manager from the main navigation.
2. In the left panel, expand Card Designer.
3. Click Request Card (Wide).

The designer opens with a Card Designer header and the subtitle "Customize how request cards appear in embedded lists (user, activity, bundle, appointment)." Use the Back button in the header to return to the Customization Manager; if you have unsaved changes, Aeon asks you to confirm with an Unsaved Changes dialog before leaving.

Permission required

The card designers live under the Designers configuration capability. Your role needs Designers access to open this page and save layouts. If your role doesn't have it, the Card Designer section won't be available to you in the Customization Manager.

The layout of the designer

The screen has three working areas, with two toolbars across the top:

• Top toolbar (templates): pick which template you're editing, create/duplicate/rename/delete templates, set the default, reset to the system default, and Save. A live status reads Saved, Unsaved, or Saving….
• Second toolbar (layout + history): choose which Layout you're editing (Default or a per-queue override), add or remove overrides, Reset to system default, and Undo/Redo.
• Fields (left): the palette of fields you can drag onto the card, grouped by category, with a Search fields… box.
• Card Preview (center): a live preview of the card. Drag fields here, click to select, reorder rows.
• Properties (right): settings for the field you've selected — "Select a field to edit its properties" until you pick one.

How the wide card is built

Every request card has a fixed first row that you can't edit. On the wide card it shows the selection checkbox, the lock and view icons, the transaction number (for example, #12345), any flags on the request, and the status badge. The preview labels this "Row 1 is fixed and cannot be customized."

Everything below that row is yours to design. Out of the box the wide card uses a single row that lays the title, author, requester, document type, call number, and scheduled date out side by side — taking advantage of the extra width. (The narrow queue card, by contrast, stacks title, author, and metadata on separate rows.) You can add up to five configurable rows in total.

How flags appear on the wide card

The wide card shows any flags on a request in the fixed top row automatically — there's room for them, so you don't have to place a field for it. The narrow queue card doesn't put flags in its fixed row; instead it carries a Flags field in its configurable rows. The Flags field is available in the palette (under Special) for both cards, so you can also place flags wherever you like in your own rows.

Adding a field

1. In the Fields palette, find the field you want. Type in Search fields… to filter by name.
2. Either drag it onto the card preview where you want it, or click it to drop it into the currently selected field's row (or the last row if nothing is selected).
3. The new field appears in the preview and is automatically selected so you can adjust it in Properties.

Arranging fields and rows

• Reorder within a row: drag a field left or right. With the keyboard, select a field and use the arrow keys (press Space to grab, arrows to move, Space to drop).
• Move a field to another row: drag it to a different row, or select it and press Ctrl/Cmd + ↑ / Ctrl/Cmd + ↓.
• Add a row: click Add Row (n/5) below the existing rows. The counter shows how many of the five allowed rows you've used.
• Remove a row: use the remove control on the row (available as long as at least one configurable row remains).
• Remove a field: select it and press Delete or Backspace, or click Remove Field at the bottom of the Properties panel.

Setting a field's appearance

Select any field on the card to open its settings in Properties:

• Custom Label — override the field's default label.
• Width — Auto, Fill, 1/3, 1/2, 2/3, or Full Width.
• Display Style — Plain Text, Icon + Text, Badge, or Template.
  • With Icon + Text, an Icon picker appears.
  • With Badge, a Badge Style selector appears (Default, Outline, Secondary, Destructive).
  • With Template, a Template String field appears — use {fieldName} syntax (for example, {itemTitle} by {itemAuthor}) to combine values.
• Text Size — Extra Small, Small, or Medium.
• Font Weight — Normal, Medium, Semibold, or Bold.
• Color — Default, Muted, Primary, or Accent.
• Hide if Empty — when on, the field disappears from a card when that request has no value for it (so cards don't show blank labels).

Per-queue layouts (overrides)

By default, every wide request card uses the Default layout. If you want a different wide layout for requests in a specific queue, add an override:

1. In the second toolbar, open the Layout selector. It reads Default until you've added overrides.
2. Click the + button (Add queue override).
3. In the Add Queue Override dialog, pick a queue and click Add Override. The new layout starts as a copy of the Default so you have a starting point.
4. Edit the override's rows and fields just like the default. Switch between Default and your overrides using the Layout selector at any time.

To remove an override, select it in the Layout selector and click the trash button (Remove this override); confirm in the Remove Override? dialog. That queue's wide cards return to the Default layout.

Overrides are a request-card feature

Per-queue overrides exist because requests live in queues. The user and activity card designers don't offer them — only the request cards (narrow and wide) do.

Saving and templates

Your edits aren't live until you save. The top toolbar shows Unsaved while you have pending changes.

• Save — click Save (or press Ctrl/Cmd + S) to write your changes to the current template. The status changes to Saved.
• Discard — the discard control (next to Save) reverts to the last saved version.

The dropdown next to the template selector manages templates:

Action	What it does
New Template	Create a fresh template (named in the New Template dialog), copied from the one you're currently viewing.
Duplicate	Copy the selected template under a new name.
Rename	Rename the selected template.
Set as Default	Make the selected template the one used by default.
Reset to System Default	Overwrite the template with Aeon's built-in wide layout.
Delete	Remove the template.

Resetting and deleting can't be undone

Reset to System Default overwrites every layout in the template — the default and all overrides — with the built-in wide layout, and cannot be undone. Delete removes the template and any role assignments that reference it. Both prompt for confirmation first; the Undo/Redo buttons only cover edits within your current session, not these template-level actions.

Assigning a template to a role

Templates let different roles see different wide cards. You don't assign them from here — you assign a Request Card (Wide) template to a role on the role's Layout Assignments, covered in Editing a Role: Layout Assignments. The default template is what everyone gets unless a role-specific template is assigned.

Editor review — remove this callout (and the HTML comment below it) before publishing

A few things only an SME should confirm on this page:

• Where the wide card renders: the page subtitle names "user, activity, bundle, appointment" embedded lists. Confirm that list is complete and accurate for what ships, and that the narrow queue card is genuinely the only place that does not use this layout.
• Flags in the fixed row: the wide card shows flags in its fixed top row automatically while the narrow card does not (coded via showFlags: isWideRequest); the Flags field is also available in the palette for both. Confirm this is the intended, documentable behavior.
• Screenshots needed: (1) the Request Card (Wide) designer with the three panels and the default single-row layout; (2) a real embedded request list (e.g., a user record's Requests tab) so admins can see where the wide card actually appears; (3) the Add Queue Override dialog.

The full generation metadata — sources, files read, and verifications, i.e. the detail a tool like Claude would need to regenerate this page — is in the HTML comment directly below this callout. When this page has been reviewed and approved, delete both this callout and that comment; a page with no Editor-review callout is one that's done.