Access Orchestrate v7.83 — Hotfix 1
We are pleased to announce hotfix 1 release for Access Orchestrate version 7.83. This is an additional release on top of v7.83 (see the v7.83 release notes) and contains the following fixes. No configuration changes are required; all fixes apply automatically on upgrade.
Deleting all tasks for an order now synchronises to other users (2599573)
When a user deleted all tasks for an order from the Order Planner, other users with the same plan open could still see those tasks after saving or refreshing — the deletion only cleared for them once they closed and reopened the plan. This could make deleted orders appear to still exist, produce apparently duplicated tasks if the order was re-added to the plan, and show misleading resource overload warnings. (Deleting from the Gantt chart was unaffected, as it used a different internal route.) Both delete routes now share the same corrected process, so every connected user sees the deletion on their next save or refresh, and a delete that cannot be completed is now reported to the user instead of failing silently.
Faster Add to Plan for large orders (2599470)
Add to Plan could take 20–25 seconds for a single works order on plans where an order expands into a large number of tasks. Planning now completes in well under a second for the same order — a customer order that previously took 23.4 seconds now takes 0.26 seconds — with no change to the resulting plan: the same tasks are created and scheduled exactly as before. Two related issues are also corrected: planning could run a full second planning pass when only one was needed, and the planning trace window did not open when planning was started from the progress bar.
Repair Pegging Links now respects a Usage KPI at task end (2576563)
Repair Pegging Links did not respect a Usage KPI measured at the end of a task. Where a consuming task recorded its material usage at task end, repair moved the task so that it started when the material became available, instead of finishing then — pushing the task later than necessary and, in the reported scenario, planning it well beyond what the pegged supply required. Repair now applies the material-availability date to the correct point of the consuming task — its start for usages measured at start or during the task, and its finish for usages measured at task end — so tasks move by the minimum valid amount, keep their duration, and remain valid against calendars and resource capacity. Tasks with a mix of start-side and end-side usages satisfy each independently.
Demand Planner no longer plans batches too late with Start By Date (2576445)
In the Demand Planner, made items added with a Start By Date method were released later than the Start By date shown in the grid — later by exactly the item's supplier lead time — so the batch could only ever be planned late, and available capacity between the Start By date and the release date could not be used. (For example, with a 4-day supplier lead time, a batch with a Start By date of 15 November was released, and planned, from 19 November.) This also made the Start By Date and Add to Plan Date methods behave inconsistently. Made items planned by Start By Date are now released on the Start By date itself, so the batch can be scheduled into any free capacity from that date onwards and meets its required date where capacity allows. Where the demand genuinely cannot be met, the existing planning exception is still raised rather than a batch being silently planned late. Purchased items, the Add to Plan Date and Campaign Start Date methods, and target-stock replenishment are unchanged.