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.
Asset types, then a tree inside each one
The left column lists Asset Types, searchable. Selecting one opens its category tree on the right — categories, subcategories beneath them, and a count on each node.
The header of the selected type names its owner and when it was last updated, with edit, duplicate, delete and Configure beside it.
A new type starts from the + beside the list: New Asset Type asks for a name and an optional description. It opens empty, with Add Root Category as the only thing on the right.
What a category carries
Selecting a category opens Category Properties: Name, Description, an Icon, a Form Template, and an Effective Status Set.
The last two are the reason this page matters beyond naming things. A category points at a form template, and the status set it resolves comes with it. So the fields and the workflow an asset gets are decided here, by which category it is in.
The panel also shows a line reading inherited from Template where a value is not set on the category itself — the same inheritance idea the permission dialog uses, in a different place.
On a category that has no form template of its own the panel shows Name, Description, Icon and Form Template (None) and no Effective Status Set line (pac demo 1.mp4 t=200s) — the line appears once a template resolves.
| Form Template | Effective Status Set | |
|---|---|---|
| How it resolves | Cumulative. Every ancestor's template plus the category's own, all the way to the root, de-duplicated by template identity | One template only. The category's own if it has one, otherwise the root's |
| Does it use the parent? | Yes — and the grandparent, and so on | No. It skips straight past the middle of the tree to the root |
| Worked example | 1(A) › 1-1(B) › 1-1-1(none) gives 1-1-1 the set {A, B} | 1-1-1 with no template of its own resolves to A, the root's — not B |
These two are not the same shape, and that is the thing to take away. Form templates accumulate down the tree; the status set resolves to exactly one and reaches past the parent to the root. There is no inheritance blocking in either direction, and a root category must always carry a template of its own — which is what makes the status-set rule always resolvable.
That is why the drawer names the template a status set came from: for a category with no template of its own the answer is the root's, and you cannot work that out by looking at the tree.
Configure mode
Configure turns the tree editable and adds Add Root Category, a control on each row to add a subcategory beneath it, and drag handles for reordering.
It also adds Import CSV and Export CSV. A taxonomy of any size is faster to build in a spreadsheet than in a tree.
Inside Configure, a delete needs no confirmation — because Discard reverts the whole session. Outside it, a delete does ask, because nothing reverts it. The test is whether the change can be taken back, not how large it looks.
Importing categories from a CSV
There are no required column names. Give the file one column per category level; step 2 of the Update via CSV wizard is where you say which column is which Asset Category level.
Each row is one path, and the rows merge into a tree — three rows sharing their first two columns make one branch with three leaves, not three branches.
Apply adds. It does not replace. A category already in the tree and absent from your file stays where it is; importing is not a way to prune.
A name that already exists is added again, as a duplicate. The import appends rather than matching on name and merging, and clearing the duplicates afterwards is manual — so it is worth checking your file against the tree before you apply rather than after.
One authority, on purpose
This page is the single place asset taxonomy is defined. Everywhere an asset category is chosen reads this list, which is why a category cannot be invented while working on a project.
If a category you need is not offered, it has not been defined here — the same shape as Team standards, and how they cascade.