Forms

The form designer is the single-column UI that lets users create and edit records of an entity. One form per entity (intentionally — see why one form).

Where to find it

PF Manage → Entities → [your entity] → Form tab.

What you can do in the designer

• Reorder fields by drag (vertical only).
• Group fields under section headings for visual chunking.
• Hide / show fields per role — a field can be visible only to admins, only to managers, etc.
• Conditional visibility — show a field only when another field has a specific value. Predicate is JSON-Logic; the designer has a visual builder for the common cases.
• Make a field read-only in this form (without changing the underlying schema).
• Override the field label for this form only (the schema label stays the same).
• Override the help text for this form only.
• Mark a field as auto-focus — the form opens with that field's cursor active.

What you CANNOT do

• Multi-column layouts. Single column only. Reasoning: accessibility (forms read top-to-bottom), mobile UX (no horizontal scroll), and form designer simplicity. If you need side-by-side fields, group them into a single "compound" field in the schema and render it custom.
• Have multiple forms per entity. One form is the canonical form. If you need a "quick add" with fewer fields and a "full edit" with all of them, use hidden fields with defaults for the quick add — or use the REST API directly to bypass the form.