Handbook — gull system

Short explanations of the places in gull system where it is easy to do something other than what you meant.

Handbook

Short how-tos for the places where gull system can quietly do something other than what you meant. Not a feature tour — only what the buttons themselves cannot show.

The handbook answers the questions you ask while working in the app: what exactly this button does, why nothing happened, and what an empty field means. Every article exists because that spot can be got wrong — often silently, so the order completes and only looks wrong on the shop floor.

The questions you ask before buying — what the product does, what it costs, who owns your models — belong in the FAQ and on the product pages.

How the handbook is arranged

• CAD configurators. What you do in gull system and in the CAD: capturing parameters, rules, the finish libraries, and taking orders from a form or a spreadsheet.
• Web configurators. The page your customer gets: what is frozen into it, how it prices itself, and what happens to an order placed on it.

What holds everywhere

• The model is yours and stays yours. gull system connects to your finished assembly, part and drawing and drives them — it does not draw them and does not generate them. What is not in the CAD, a configurator cannot produce; what is in it, it can control.
• A configurator is built in eight steps. 1 Settings, 2 CAD connection, 3 Capture parameters, 4 Define inputs, 5 Rules, 6 Input sources, 7 Output documentation, 8 Workflow. The articles refer to them by number — "in step 5" means this list.
• A name is the wiring, not a caption. The name you give a captured item or an input is exactly what your rules, your folder-name formulas and your form refer to. Renaming it rewrites every reference — which is why it pays to name things the way you talk about them.
• Nothing is sent by itself. A capture reaches gull system only when you click Save; a web configurator changes only when you press Export again. That is deliberate: a half-finished edit should not change what is running.
• When gull system is not sure, it refuses. An ambiguous setup is never guessed at, and a material is picked from a list rather than typed — because the CAD does not report most of these mistakes: it leaves the old value on the part and behaves as though all is well. A refusal is loud; a silent failure is not.
• When something did not happen, read the log. Every order shows what reached the model and what did not — including rules marked Not set, which is not an error but "send nothing". It is faster than guessing from the result.