Declining a cost rule on a Production Run
Auto-apply cost rules emit extra-cost lines onto a Production Run whenever conditions match. These rows are locked (read-only) to show they are rule-managed, not manually entered. If a rule applies in general but should not apply to a particular run, you can decline it for that run only.
Step-by-step
- Open the Production Run and select the Costs tab. Rule lines appear in the Assembly costs grid.
- Find the row added by the cost rule. Rule-added rows are read-only: their fields are greyed out and can't be edited.
- Click the ⊘ (decline) icon at the end of that row. Hovering it shows "Don't apply this cost rule to this document".
- If you have unsaved edits in the grid, the icon is disabled and shows "Save your changes first — Don't apply reloads this grid". Save first, then decline.
- The grid reloads. The rule's line is removed and won't come back on future saves of this run.
What this does — and does not — affect
| Scope | Effect |
|---|---|
| This Production Run | Rule is permanently suppressed for the life of this run |
| Other Production Runs | Rule continues to apply normally wherever conditions match |
| The cost rule itself | Unchanged — still active for all other documents |
Important notes
- Declining is permanent for that run. There's no undo button; contact Luminous support if you need the rule re-applied.
- The decline survives adding or removing Work Orders, editing the run header, and any other save.
- Work Orders also show rule-added rows as read-only, with a lock icon ("Added automatically by a cost rule. Edit the rule to change it."). Work Orders don't offer a decline option — to change those rows, edit the cost rule itself.
Troubleshooting
The ⊘ icon is greyed out. You have unsaved changes in the grid, or a save is in progress. Save, wait for it to finish, then decline.
The row came back after I saved. Only rule-added (read-only) rows can be declined. A row you can edit is a manual line — delete it the normal way.