CupixWorks 5.0 — this article is still being finished. Screenshots marked to be replaced show the right screens and will be retaken before launch. Taken in a support session, so the top of the screen shows a bar you will not see. Taken on an internal test system, so the address and team name are not the ones you will see.
One page, two subjects
Templates has two tabs and they are genuinely different things. Status Sets define the stages a note or an asset moves through. Forms define the fields someone fills in.
They share a shape: a searchable list on the left, a read-only view of the selected item, and a Configure button that turns the right-hand side editable. Nothing saves until you press Save, and Discard reverts the whole session.
Status Sets
A status set is a group of statuses arranged in three named columns: Initiation Stage, Execution Stage, Finalization Stage. Each column holds however many statuses you add, and the column is what gives a status its meaning in a workflow.
Each status chip has a menu — Edit, Duplicate, Delete.
A new status set starts from the + beside the list: Add Status Set asks for a name and an optional description and Create. The pencil beside a set's name opens Rename, with the same two fields.
Adding or editing one opens a panel with more than a name: Title, Description, Abbreviation, a Status Shape chosen from a row of shapes, and two colours — background and foreground.
The shape and the abbreviation are there because a status has to be legible when it is small. A full title does not fit on a marker in a viewer; an abbreviation and a shape do.
Both are marker fields, and SiteView is where you see them. The abbreviation is what appears on a SpatialNote marker when the full status name will not fit; the shape is the shape of that marker. So the two colours, the shape and the abbreviation are together the answer to “what does this status look like on a marker” — which is the only place most people will ever see it.
Forms
A form is a set of fields. Select one and you get a Preview that states its own limits: this preview is read-only. Click Configure to edit fields.
A form is created from the + beside the list. Add Form asks for a name and description, a two-letter abbreviation with a font colour and a background colour — the symbol the form shows in lists — and the Status Set it binds to. The pencil on a selected form opens Edit Form with the same fields.
In Configure the page splits: a Form Fields list on the left, a Live Preview on the right, and an Add Field menu offering Text Field, Number, Text Area, Check Box, Multi-Select, Dropdown Select, Radio Buttons, Date and Select Member. Selecting a field opens its properties panel — Name, Label, Tooltip — with Duplicate and Delete at the foot. Save, and the form's Preview tab shows it as a user will see it, above an Updated toast.
Forms also Import and Export, which is how a form moves between teams.
Both directions are JSON. Import expects a JSON form definition and Export produces the same, so a form exported from one team imports into another unchanged. Hand it a file that is not a form definition and it refuses with That file is not a form definition.
Where these are used
Neither tab is an end in itself. A form template is attached to an asset category, and that category then resolves an Effective Status Set from it — see Team Settings: Asset Categories.
So editing a status set here changes what people see on assets elsewhere. That is the reason this page is a team-level page and not a per-project one.