What problem does it solve? Deciding whether a variant is the right mechanism — and then configuring it correctly — is the hardest part of working with Thinkwise Software Factory variants. This Skill guides the judgment call (variant versus prefilter, screen type, or separate object) and the mechanics of field-level overrides versus set-level snapshots via an MCP connector. ## Core Features & Use Cases - Variant creation and lifecycle: Create, copy, rename, and delete table variants via bound tasks, add report variants directly, and configure task variants through the companion tasks skill. - Inheritance management: Distinguish field-level settings (independently overridable, no activation) from set-level settings (grid, form, tree, detail, filter, search, sort) that require an explicit Setup snapshot, and reset either back to inheritance. - Drift auditing and safe deletion: Query tab_variant_change to compare a variant against its default and check tab_variant_used before deleting anything referenced by menus, details, lookups, or process flows. - Use Case: Build a shop-floor table variant of a production order table — locked to the current workstation, card layout, limited task set — while keeping the default's grid and form inheriting. ## Quick Start Ask the assistant to create a shop-floor variant of the production_order table in the Software Factory model with a card layout and only the start and complete tasks visible.
