By default, a term only needs its text and language to be saved, so a single glossary can hold well-documented terms next to bare ones. Glossary Required Fields lets an Account Admin choose which term fields must be filled in each glossary. wxrks then blocks saving, approving or importing a term that leaves a required field empty.

Each field is either Optional or Required. Six term fields can be required in every glossary:

A glossary's own custom attributes (extra term fields an admin adds to a glossary, set up under Custom Attributes when editing it) can also be required, one glossary at a time. Yes/no term options such as Case Sensitive and Forbidden are not on the list.

A field counts as empty if it holds only spaces or invisible characters. For Part of speech and Gender, the Undefined option also counts as empty.

Go to Settings > Translation > Glossary Required Fields. The page has two parts:

Every glossary created from now on copies this rule, including glossaries created by import or through the wxrks API. Existing glossaries keep their own rule, so changing the default does not change them.

ℹ️ Note: the default covers the six term fields only. Custom attributes belong to each glossary, so you require them glossary by glossary (next section).

ℹ️ Note: if a custom attribute is removed from the glossary, it is also removed from the rule. Terms are never blocked by an attribute that no longer exists.

Example. Glossary A requires Gender and glossary B does not. You select both, set Concept definition to Required and leave the other fields on Keep. After saving, both glossaries require Concept definition, A still requires Gender, and B still doesn't.

Bulk editing covers the six term fields only. To require custom attributes, edit each glossary.

The rule applies when a term is added or edited in a glossary, when a term is approved on the Terminology Board, and when terms are imported.

In the Add Concept and Edit Term forms, and when editing a term on the Terminology Board, required fields are marked with an asterisk (*). Until they are filled, the Publish, Request and Save buttons look disabled.

Clicking one of them anyway saves nothing. wxrks opens More Options where the missing fields are, moves the cursor to the first one, and shows the message Fill in the required fields.

A card can't move into an approved lane while one of its terms has an empty required field, whether you drag it or use Actions > Move selected requests. wxrks shows Not approved: fill in the required fields of these terms, with each term, its language and the fields it is missing. The message stays until you close it. Edit the terms and move the card again.

If a card publishes to more than one glossary, the term must meet the rules of all of them.

Terms can still enter the board incomplete: the rule is not applied to terms added from the Editor or learned by AI until the card is approved.

When you import an XLSX or TBX file into a glossary with required fields, wxrks imports the complete terms and skips the incomplete ones. A concept whose terms are all skipped is not created. The import does not fail.

💡 Tip: name the columns exactly as an exported glossary names them, for example definition and gender in lowercase. A column header written another way is not read as that field, so its terms are skipped as incomplete.

To see how many terms were skipped, open the glossary and click Import History. The Skipped terms column shows the count for each import. For the file layout, see How to Format Your XLSX File for Glossary Import.

The rule is not applied to terms already in the glossary. They stay valid until someone edits them. At that point, the term must be completed before it can be saved.