Lookup Tables

Lookup Tables

A lookup table turns a code into a meaning. When a type-code segment is interpreted as a Lookup (see Type Code Rules), the app finds the segment's value in a table and uses the matching output. For example a voltage table that says U3 means 400 V.

Open Type Code → Lookup Tables in the left menu. You can also build one without leaving the rule wizard, using its New Table button.

---

What a table is for

Reach for a lookup table whenever a segment has a fixed set of options, each of which maps to a value: voltage codes, frame sizes, material letters, gear ratios. Anything where a short code stands for something longer.

You do not use a table for values that are calculated (use a Formula) or already correct as they are (use Direct).

---

Creating a table

Create table opens a form.

Field	What to enter
Table Name	A clear name, e.g. Supply Voltage.
Description	What it translates, e.g. Maps the voltage code to a value.
Shared / Private	A switch. Shared means other rules can use this table too. Private means only the rule you are building.

Then add the entries, one row per option:

Column	What to enter	Example
Code Value	The text as it appears in the type code.	U3
Meaning / Output	What that code becomes.	400 V
Document Set	Optional. A document set to attach whenever this value is matched.	a certificate bundle

Add Entry adds a row; the bin icon removes one. Save with Create and Select (or Save Changes when editing).

Example: a Supply Voltage table with two entries:

Code Value	Meaning / Output
U1	230 V
U3	400 V

Now any rule that interprets its voltage segment with this table turns U3 into 400 V.

---

Attaching documents to a value

This is the powerful part. Give an entry a Document Set, and whenever a parsed code hits that value, the set's documents are added to the product's export automatically.

Example: in an Options table, the entry EX (meaning explosion-proof) carries a document set holding the ATEX certificate and the explosion-proof manual. Every product parsed with an EX segment then gets those documents with no extra step.

You build the document set in the Document Library first, then pick it here.

---

Shared or private

• Shared tables appear in every rule's lookup picker and are the right choice for anything reusable, like a voltage or material table you use across product families.
• Private tables belong to one rule. Use them for a mapping that only makes sense for that one family.

You can change a table later from the list.

---

Managing tables

The Lookup Tables page lists every table as a card showing its name, whether it is Shared, how many entries it has, and how many of those entries have a document set linked. Each card has Edit (reopens the same form) and Delete.

---

Hints

• Make a table Shared if more than one product family uses the same codes. Build it once, use it everywhere.
• Fill the Code Value exactly as it appears in the code. The app matches on the raw segment text, so U3 and u3 are not the same; keep your codes consistent.
• Use the document-set column to make certificates follow an option automatically. It saves attaching the same file to every variant.
• Build the table from the wizard with New Table while you are setting up a Lookup segment; it pre-fills the values it already saw in your examples.

---

Limitations to know

• Matching is on the exact code value. A value not in the table falls back to the segment's default, if one is set, otherwise it is flagged. Keep the table complete.
• Document sets attach at parse and re-parse time, so a set you link after a product was created only reaches that product when you re-parse it.

For technical users

A lookup table has entries keyed on the raw extracted value (the regex capture), not the interpreted display value. Each entry optionally references a DocumentSet, whose items are appended to the generated Handover Documentation when that value matches during parse or re-parse. Tables are Shared (selectable by any rule) or Private (scoped to one rule). The rule wizard can create a table inline and seed its entries from the distinct segment values in the example codes.