DocumentaciónHelp

Design an item's form

Build the questions the requester answers when ordering an item, make some appear only when they apply and test it before publishing.

On this page

An item's form is the set of questions the desk needs to handle the request right the first time: which equipment, for whom, from when. You build it field by field and test it in the Preview exactly as the requester will see it.

Before you start

  • You need the Administer level in Service catalog to change and save the form. With the View level you can open it and test it, but not save it.

  • The item can be new or existing. See Create a service catalog item.

Add a field

  1. Go to Catalog, Items tab, and open the item (or press New item).

  2. In the Form part, choose the type in the list next to the Field button.

  3. Press Field. The field is added at the end, already open, with the type name as its label.

  4. Fill in its configuration (see the table below).

  5. Repeat for each question. A form allows up to 50 fields.

  6. Press Save at the top right.

Each field appears as a row with its label, its type and, if applicable, required. Press the label to open or close its configuration. With ↑ and ↓ you change the order in which they're asked, and with the trash icon you remove the field.

Field types

Type

What it asks the requester for

Its own settings

Short text

One line of text, like a serial number or a folder name

Help, Maximum length

Long text

Text over several lines, like a justification

Help, Maximum length

Number

A quantity, like the number of licenses

Help, Maximum value

Date

A calendar day, like the start date

Help

Email

A valid email address

Help

Dropdown list

Choose one option from a list

Options

Single choice

Choose one option, showing all of them

Options

Multiple choice

Check one or more options

Options

Checkbox

Check yes or no, like "I accept the terms of use"

—

Person

Indicate someone in the company, like who will receive the equipment

People

Attachments

Upload files, like a quote or a signed form

Maximum files

Settings for each field

All fields have:

  • Label: the question the requester reads, up to 120 characters. Required.

  • Id: the field's internal name. It's used in Show if and in workflows to read the answer. When you add the field it's created from the type name (for example, texto_corto) and it doesn't change when you edit the label: change it to something meaningful, like tipo, if you'll use it in conditions. Use lowercase, start with a letter and use only letters, numbers and _ (up to 40 characters), without repeating another field's id.

  • Type: you can change it later. The label, id and whether it's required are kept; between Dropdown list, Single choice and Multiple choice the options are kept too.

  • Required: the requester can't send the request without answering it. In the portal it's marked with an asterisk (*). On a required Checkbox, the requester must check it.

  • Show if (optional): a condition so the field appears only in some cases. See Show a field only when it applies.

And depending on the type:

  • Help: a short text under the field, up to 200 characters. Available in Short text, Long text, Number, Date and Email.

  • Maximum length: how many characters it accepts. If you leave it empty, the limit is 500 for Short text and 5,000 for Long text.

  • Maximum value: the highest number a Number accepts.

  • Options (one per line: value | text): each line is an option. To the left of the bar goes the value (what Elion ITSM stores and what you use in conditions) and to the right the text the requester sees. If you write only the text, the value is created on its own. Up to 100 options.

  • People: The whole company lets them choose any active person; Their department, only someone in the same department as the requester.

  • Maximum files: from 1 to 10 per field. It defaults to 3.

An example of Options for an "Equipment type" field:

notebook | Notebook
pc | Computador de escritorio
monitor | Monitor adicional

Choose short, stable values (notebook, pc) and change the text freely. If you change a value, the conditions and workflows that use it stop matching.

Show a field only when it applies

Show if (optional) makes a field appear only if a condition on the other answers is met. For example, asking "Do you need a docking station?" only when the equipment type is notebook.

The condition isn't code: it uses a closed set of operators and Elion ITSM checks it as you type:

To

Write

Read an answer

form. followed by the field's Id: form.tipo

Compare

== (equal), != (not equal), <, <=, >, >=

Check whether it's in a list

in: form.tipo in ['notebook', 'pc']

Check whether a multiple choice includes an option

contains: form.software contains 'office'

Combine

&& (and), `

Values

text in single quotes ('notebook'), numbers (500000), true, false and null (empty)

Examples:

form.tipo == 'notebook'
form.tipo in ['notebook', 'pc'] && form.reemplazo == true
form.cantidad > 5
form.fecha_ingreso >= '2026-11-01'

Rules for it to work:

  • In lists and options you compare against the value, not the text: form.tipo == 'notebook', not 'Notebook'.

  • A Number is compared with numbers without quotes (form.cantidad > 5); text, with quotes. A number in quotes isn't equal to a number.

  • A checked Checkbox is true: form.acepta == true.

  • Dates are compared as text in YYYY-MM-DD format.

  • It can only use other fields in this form (not the same field), in up to 500 characters.

  • If the condition isn't met, the field doesn't appear and its answer isn't requested, even if it's Required.

  • A hidden field counts as empty for the other fields' conditions. If "Equipment type" is hidden, whatever depended on it is hidden too.

If the condition has an error, you see it in red under the field, for example Unclosed text. or it uses form.modelo, which is not a field of this form.

If you change a field's Id, the conditions of other fields that used it end up with errors and you can't save until you fix them. Workflows that read that answer also stop finding it.

Test the form

The Preview part shows the form exactly as the requester will see it, with the Short description at the top. It updates as you edit and applies the Show if conditions: answer the questions and you'll see fields appear and disappear.

  1. Answer in the Preview as a requester would.

  2. Press Validate. Elion ITSM checks your answers and marks each field's errors in red, like Required., Invalid email. or Maximum 5. If everything is fine, you'll see The test answers are valid.

  3. If the item is already saved, press Test on the server. It's the same check that's done when someone sends the real request. If everything is fine, you'll see The server accepted the test answers.

Test on the server checks the answers against the saved form. If you changed fields, press Save before testing. On a new item the button doesn't appear until you save it.

In the preview, Person and Attachments are simulated: you type text instead of searching for the person or uploading a file. So when testing on the server, leave them empty (if they're required, the server will mark them with Required; that's expected). To really test them, order the item from the portal with a test user. See Request something from the catalog.

A Person field with Their department is tested with your own department, as if you were the requester.

What happens next

  • Each time you save a change to the form, the Form version you see under the item name goes up. Changes to the item's other details don't change the version.

  • New requests use the current version. Each request already created keeps the version it was answered with: on the ticket record, the Catalog request block shows the questions and answers of that version, even if you later changed the form.

  • On the ticket, the description contains each question with its answer (options with their text, checkboxes as Yes or No).

If something doesn't work

Under the form, a yellow box shows what prevents saving. While it's there, pressing Save shows Fix the form before saving. The most common warnings:

  • the label is missing.: enter the field's Label.

  • the id must be lowercase, start with a letter and use only letters, numbers and _. or the id "…" is repeated.: fix the Id.

  • add at least one option., some options have the same value. or each option needs a value and a text.: check the Options.

  • between 1 and 10 files. or the maximum must be positive.: fix Maximum files, Maximum length or Maximum value.

  • "Show if" of "…": followed by the problem: fix that field's condition.

When testing on the server, the message Unknown field under a field means that field isn't saved yet: press Save and test again.

Related

Search Elion ITSM

Type at least 2 characters to search Elion ITSM.

↑↓ to navigate · Enter to open · Esc to close