Documentation Service Catalog Catalog Group Form
Detailed guide

Catalog Group Form

The group form for organizing reusable catalog records into a structure estimate builders can navigate quickly.

Use this form to create a clean record the first time or safely update an existing one without guessing which field drives downstream behavior.

Open demo page Back to overview
Quick summary Step by step Guardrails Troubleshooting Related workflows

Quick summary

  • Clean up catalog navigation here instead of working around bad structure in every estimate.

Put it into practice

  1. Start by reviewing current group structure so the new or edited group solves a real discoverability problem.

    InteractionsService Catalog > Groups: scan existing groups and where offerings are currently clustered.

  2. Open Group form and define a clear grouping identity aligned to how estimate builders search for work types.

    InteractionsGroups tab: click New Group or edit existing group row.

  3. Set grouping rules and usage notes so future catalog updates remain consistent and easy to navigate.

    InteractionsCatalog Group Form: complete grouping rules and display or usage notes.

  4. Save and confirm offerings appear under the intended group in catalog browsing context.

    InteractionsAfter save, return to group and offering views to validate organization.

  5. Verify estimate builders can now find related offerings faster using the updated group structure.

    InteractionsProject Estimate offering selector: check grouped navigation and search results.
    Open workflow: Estimate Workflow

What to review

Page header and breadcrumb

Confirms whether you are creating or editing, gives you the back path, and is the quickest way to avoid updating the wrong record.

Primary form sections

The form is grouped so you can complete one block at a time instead of hunting for every field in a single long screen.

Required inputs and field labels

Every required label tells you what must exist before the record can be saved; blank or invalid values should be corrected before moving on.

Validation and inline errors

Use these messages as instructions, not warnings to dismiss. They tell you exactly which field blocks save and why.

Primary save action

Commits the record only after the form validates. Use it after reviewing every section because it is the action that changes workspace data.

Cancel or return action

Leaves the form and takes you back without finishing the workflow. Use it when you opened the wrong record or need to check related data first.

Group Name

Group Name (for example Core, Extended, Optional) is how estimate and quote lines are clustered for the client.

Sort Order

Sort Order controls where the group appears relative to other groups.

Default Group

Default Group marks this group as pre-selected when adding new estimate lines, so only one group should hold that role.

Guardrails

  • Group Name is required and should be unique so estimate builders can tell groups apart.
  • Only one group should be marked Default Group, since it becomes the pre-selected group for new lines.
  • Sort Order should be set intentionally so the group appears where builders expect it.
  • Only catalog maintainers should change grouping structure.

If it starts drifting

  • If items are still hard to find after save, confirm you changed the right group rather than the underlying offering.
  • If new estimate lines land in the wrong group, check which group is set as Default Group.
  • If two groups look interchangeable, rename one rather than leaving ambiguous labels.