Field Studio: forms and fields

Before you begin

• Catalogue capability; department or global permission.

Step by step

1. 01

   Choose Forms, Fields or Value lists; create reusable fields and stable technical keys.

2. 02

   Create/clone forms and sections, move fields by drag or arrows; configure required, defaults, visibility, readonly, conditions and limits.

3. 03

   Preview as requester/agent, save draft and publish separately; inspect the real catalogue.

4. 04

   Choose the appropriate type: short or long text with minimum/maximum length, decimal-capable number with bounds, yes/no, date, date and time, whole-minute duration, email, phone, HTTP/HTTPS URL, single or multiple choice, or informational text requiring no answer. No is distinct from an empty field. Choices keep stable keys when labels are translated.

5. 05

   Configure visibility and editability separately for requester and agent. A create-required field must be requester-visible and either editable or have a valid default; a hidden field cannot be required at that step.

6. 06

   Read-only values are applied by the server from the catalogue; the requester does not need to re-enter them. Test both preview and an actual request with the intended role before sharing the form.

7. 07

   Clone a form to create a variant, give it a new key and save. Setting Default replaces the earlier default in the same scope; publish separately and reopen to verify selection. Department managers see global definitions read-only: create an override in their authorised department.

The result to check

Users complete the published version, separate from the draft.

Limits and considerations

• Form name limit 120; key limit 64 lowercase/digits/hyphen/underscore.
• Types: short/long text, number, boolean, date/datetime, duration, email, phone, URL, information, single/multiple choice.
• Global and department overrides differ.

Continue with related guides