Skip to main content
Administration → Form studio is where you arrange the form for every kind of record and add the questions your organisation tracks that the product does not — a production line, a permit number, a batch. The middle of the screen is the record’s form drawn as it will be drawn, so you arrange it directly. Form studio showing the work order form, with the palette of field types on the left Form studio showing the work order form, with the palette of field types on the left

Who can use this screen

Adding and arranging fields takes Configure custom fields — System Administrator and Maintenance Administrator by default. Without it the screen says Forms are arranged by an administrator, because a field’s type decides where its answers are stored. See roles.

The header and toolbar

The canvas is the form

The greyed fields are the product’s own: what they ask cannot change, but where they are asked can. Your fields are drawn as the record will draw them. Fields live in sections. The product’s sections come first, then yours, then In no section, drawn under everything else.

Back to the standard layout

Back to the standard layout asks first, in Go back to the standard layout?, and says what will move:
  • the record’s own fields go back where the product draws them;
  • the photographs and files the product added go back to the section they started in, which is made again if somebody removed it;
  • fields you added move to In no section;
  • sections you added are removed once nothing is left in them.
Nothing is deleted. Every answer stays, and so does what you set on each field: whether it must be answered, whether it is withdrawn, who may see it and when it is asked. Put it back goes ahead. The button is offered on every form, including one that holds only your own fields, such as a meter reading.

Adding a field

Add a question lists every type — Drag one into the form, or choose it and then choose where it goes. Placing one opens A new [type] field, here: Some forms take no questions of your own, because an answer to one could not be shown on any list. On those the palette says so in place of the types — on a form such as the capex proposal, that new questions cannot be added but its own fields are still yours to move, stop asking or insist on; on a form that already holds questions of yours, that the ones you have are still yours to move or stop asking. The type is fixed once anything answers this field, so it is worth getting right now. For a choice field, you add the choices once it exists. Add creates the field; Cancel discards it.

The types

The two signatures are different on purpose. A drawn signature is strokes captured on screen and is the only kind that can print on a generated document. A signature as an image is filed as evidence — retained, captured offline and counted against a job’s requirements.

A field’s settings

The pencil on a field opens its settings. The header shows the field’s label, its key, its type, required if it must be answered and how many answers it holds. The tabs are What it asks, Choices (choice fields only, with the number of choices), Where and when and Who sees it. The settings of a text field on the What it asks tab The settings of a text field on the What it asks tab

What it asks

For A controlled document field, What it files a new document as sets the Category, Owner and Review every (months) given to a document uploaded through the field. Leave it empty and this field only points at documents the library already has.

What a field accepts

Anything of the right type means no rule is set. A rule is refused at the moment somebody answers, in the words you give it.

Choices

The Choices tab of a One of a list field The Choices tab of a One of a list field What it offers lists each choice with its code, its wording and how often it has been chosen. Turn off stops offering a choice and keeps it on records that used it; Turn on offers it again; Remove deletes a choice nothing has used. Shown as plus Add adds a new choice. A published list cannot change under the answers given against it, so changes wait until you Publish. A choice field with nothing to choose cannot be published.

Where and when

The Where and when tab, with an Ask it only when condition and an Insist on it when condition The Where and when tab, with an Ask it only when condition and an Insist on it when condition Where it applies decides which records carry the field at all. With nothing named, it is on every record of this kind, so the first thing you add narrows it. When it is asked decides whether a record that carries the field is asked it right now. Conditions read the record’s own answers and fields, so the form follows what somebody fills in. A field hidden by a condition is never required — nobody can be blocked by a question they cannot see. Each condition uses the same builder as rules, and has its own Save. A few forms are filled in on a screen of their own that cannot keep a field frozen or ask it only on a condition — the capex proposal, an asset transfer and a disposal among them. On those, the conditions and Show it, but not for anyone to type are not offered, and a sentence says why in their place.

Who sees it

The Who sees it tab with the see and answer grant list and the Hidden from list The Who sees it tab with the see and answer grant list and the Hidden from list

The product’s own fields

The settings of a product field, the work order title The settings of a product field, the work order title A product field’s settings have What it asks and Who sees it. Its label and type belong to the product and are the same for every organisation; rename it on Localization.

Sections

Add a section opens A new section with a name (example: Commissioning). Name it after a section the record already has and its fields are drawn inside that one rather than in a panel below. A section’s settings offer:

No longer asked

Fields you stopped asking are listed under No longer asked. Nothing there has been deleted: every answer is still on its record, readable by a report and writable by an import. Ask it again returns a field to the section it came from, at the place it held.

List view

Below the form, List view sets how each list of this kind of record is drawn, for everybody in your organisation. It changes how the list looks and nothing in it. It is offered for the main registers — work orders, work requests, assets, maintenance plans, inspections, bookings, tools, sites, visitors, parts, requisitions, requests for quotation, purchase orders, vendors and contracts — and for the capex and FF&E plan lists. Each change is saved as you make it. For the two colours, tick the box and pick one of eight pale colours, or choose Another colour. A colour too dark to read the list on is refused with Too dark for the list to be read on. Choose a lighter colour. On the dark theme each colour is drawn as a faint tint of itself.

On the list and beyond the form

A few kinds of record carry two more panels below List view. On the list lists the warnings a list draws above its rows. Untick one to stop drawing it. That changes what is shown and nothing else: every check behind it still runs and still refuses. The capex plan list, for example, offers Plans that will be refused when they are sent. Beyond the form lists parts of the record that are not on its form. Each is off until it is ticked here, and ticking one turns it on for everybody in your organisation. The capex proposal offers two: The consolidated planning and capitalization plan forms offer a Send for approval of their own in the same way, and the capitalization plan also offers Capitalization Date is the 1st of the month. The site form offers Site code can be changed. Off, a site’s code is set when the site is added and cannot be changed. On, the code can be changed on the site’s form, including a code the site was numbered with, and every location at the site takes the new code at the start of its path. Labels already printed still show the old code, so print them again — scanning one printed from the product still finds what it was printed for — and numbers already given out keep the code they were given.

Required

Tick Must be answered and the field must be answered before the record can be saved — and, on a work order, before the job can be closed. A required field appears in the field app under “before you can close this”, with a count.
Every required field is something somebody must type at the machine, possibly in the rain. Prefer Insist on it when a particular status is reached over making a field required everywhere.
A record’s own number is set on Numbering. A status change can ask for fields in a dialog — set that on the move on statuses and transitions. Bring fields and values in bulk with Import.