Orchestrate: Release notes v7.83 Hotfix 2

BOM save error resolved (2664682): Fixed an issue in the Bill of Materials where saving changes could fail with the error "The data modification cannot be saved due to some errors." BOM edits now save reliably.

Plan reload no longer freezes on unplannable task (2609669): Fixed a hang that occurred during plan reload/refresh when a single existing task could not be planned during the auto-shuffle. Previously the application would freeze and require a forced close; the reload now completes and reports the issue instead of locking up.

Shuffle-failure dialog no longer hidden on plan open (2607798): Fixed a problem where the shuffle-failure dialog shown while opening a plan was displayed behind the TopMost loading progress bar, making the plan appear stuck at "Step 17 of 20" (~85%). The dialog is now visible and can be actioned so the plan can continue loading.

Plan opens with unsatisfiable Start-Start maximum offset (2631203): Fixed an issue where a plan would fail to open when an unsatisfiable Start-Start maximum offset aborted the load-time shuffle. The plan now opens and handles the constraint gracefully instead of blocking the load.

Deleting Purchase Orders and Works Orders fixed (2660749): Resolved failures when deleting Purchase Orders and Works Orders, including a NullReferenceException when the plan was closed, a DBConcurrencyException when the plan was open, and a defined-pegging foreign key conflict. Deletions now complete correctly in all these scenarios.

Edit Processes screen error loop fixed (2539676): Fixed a defect on the Edit Processes screen where the error "Value cannot be null. Parameter name: key" would repeat in a loop and could not be dismissed. The screen now handles this condition without the recurring, undismissable error.