Skip to main content
Forms collect structured information from employees and hand it to a workflow. Instead of a free-text ticket an agent has to chase down, a form asks the right questions, validates the answers, and starts the automation with a complete payload.
Laptop Request form in a Serval ticket, showing a Device section with a two-by-two grid of laptop cards, each with a photo, name, and description

A form opened in a ticket, with product images on the options

Where forms live

Forms live on a team, under Service Management → Forms.
Serval left sidebar with Service Management expanded and an arrow pointing at the Forms entry

Forms in the team sidebar

Why Serval forms

When to use a form

Need only a parameter or two before running an automation? Workflow inputs may be enough. Reach for a form when the request has sections, logic, live data, and a lifecycle worth versioning.

Lifecycle

1

Build

Describe the form to Catalyst, or edit its code directly.
2

Preview and publish

The preview is the real form, rendered by the real engine.
3

Employees fill it in

From the catalog, a link, or because the Help Desk Agent offered it in their ticket.
4

Submit starts the workflow

Every submission and its run appears under Run history.

Create a form

Build, preview, and publish your first version.

Fields and layout

Every field type, its validation, and how to lay out sections.

Logic and workflows

Conditional fields, live data, and the submit handler.

Share and fill

Catalog, tickets, Slack, and who can open a form.