SimpliServDocs

Plan custom fields

Plan, create and place custom fields for contacts, tickets, orders and other areas on the detail page

→ Open custom fields in SimpliServ

Custom fields extend the standard data. Good fields answer a recurring question; bad fields duplicate existing data or collect unstructured text.

Planning

Target entity

Decide whether the field belongs to contact, ticket, order, proposal, invoice, product, vehicle, lead, contract or employee. A field on the wrong object makes search and workflow harder.

Type

Choose text, number, selection, date, checkbox or tri-state checklist to suit the evaluation. Don't use free text when only fixed values are allowed. Show fields that are only needed in certain cases via Conditional display instead of always displaying them.

Required and visibility

Only make a field required if every process reliably knows the value. Make the field name unique for employees and API/workflows. A field only appears on the detail page once it sits in a card.

Setup

Choose the target

Open Administration → Layout & fields → Fields & cards and choose the area. Don't rebuild existing standard fields.

Create the definition

Use Field to enter label, type and options and drag the field from the Field list into a card. Choose terms so users don't have to guess.

Open a test record

In Preview mode and on a safe example check: display, required logic, saving and editing.

Check automations

Check workflows, form mappings, imports and exports for the new field logic.

Don't change field names or options uncoordinated after productive use. Reports, workflows and external integrations may expect the old values.

How is this guide?

On this page