Quick summary
- Maintain categories centrally so estimate builders do not invent inconsistent naming patterns.
Detailed guide
Catalog Category Form
The category form for defining reusable catalog categories that keep items organized and consistent.
Use this form to create a clean record the first time or safely update an existing one without guessing which field drives downstream behavior.
Put it into practice
-
Start by checking whether an existing category already covers the intended use. Add a new category only when classification meaning is genuinely different.
InteractionsService Catalog > Categories: review names and existing category scope before creating. -
Open the category form and define category identity with clear naming for fast selection.
InteractionsCategories tab: click New Category or edit existing category row. -
Set scope or type fields so category placement and filtering behavior match intended usage.
InteractionsCatalog Category Form: complete scope/type controls and supporting notes. -
Save and validate that target records can be classified with this category in their respective forms.
InteractionsAfter save, open a related form or list and confirm category appears in selector controls. -
If category updates were made for active pricing work, verify impact in estimate setup.
InteractionsProject Estimate workflow: validate category-linked selection behavior where relevant.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.
Category identity
Category names should help users choose correctly without opening every record.
Scope or type fields
These fields decide which records the category is meant to organize.
Display notes
Use notes to make intended usage explicit when names alone are not enough.
Guardrails
- Category data should validate before it becomes reusable workspace structure.
- Category editing is a shared-catalog permission.
If it starts drifting
- If a category does not appear where expected, verify you created the right category type for the target tab.