Check violations before generating outputs
Run the violation checks that flag sizing, SKU and design-rule problems before pricing, production files and schedules are generated.
Before outputs (pricing, production files, schedules) are generated, the design is checked unit by unit for violations: unit width/height/depth outside the catalogue item's min/max, corner-unit specific limits (front width, side depth, shutter partition widths), end panel height limits, custom panel sizing limits, shutter design and handle size limits, drawer/basket/tandem-box size limits, brand preference mismatches, edgeband SKUs that cannot be found in their group, and — if the admin enabled the category-mismatch warning — invalid or wrong-category SKUs on panels (core, finish, edgeband, shutter design). Panels are also checked for radius-mode arcs that cannot join their end points at the current size (the end points are too far apart for the given radius); such an arc is not rebuilt, so the panel's cut, drawings and CNC outputs do not follow it, and the message asks you to change the panel size or the arc parameters.
Design-constraint rules are also re-checked against already-placed units, so a rule added by the admin after a design was built can flag existing units.
A modal lists the violations before continuing to outputs.
✓ Diperiksa di produk pada 11 Oktober 2026Each violation entry in the pre-output modal names the cabinet it belongs to and the specific colliding item (for example a groove colliding with another groove, or a connector clash), so the designer can tell what to move.
A panel whose finished length or width comes out at or below zero is reported as a "Panel dimension violation" with the offending L and W values, and is grouped with the sizing-rule violations shown in the pre-output modal.
✓ Diperiksa di produk pada 19 Oktober 2026Changing a cabinet's depth or width after hardware has been added can surface hardware/size violations on that unit, which designers should review before sending a quotation.
Units marked 'disabled in outputs' are skipped from violation checks by default.
✓ Diperiksa di produk pada 11 Oktober 2026If the org admin enabled 'no outputs for designs with violations and issues', downloads are blocked while any violation exists, unless the specific design has been granted an exemption (in which case an informational message appears instead).