Access Orchestrate v7.83 — Hotfix 3
We are pleased to announce hotfix 3 release for Access Orchestrate version 7.83. This is an additional release on top of v7.83 (see the v7.83 release notes), hotfix 1 (Orchestrate: Release notes v7.83 Hotfix 1 | Orchestrate Help Centre), hotfix 2 (Orchestrate: Release notes v7.83 Hotfix 2 | Orchestrate Help Centre) and contains the following fixes. No configuration changes are required; all fixes apply automatically on upgrade.
Bug Fixes
Gantt chart no longer jumps to the top when refreshing or saving a plan (2672847)
Previously, refreshing or saving a plan caused the Gantt chart to scroll back to the very first row, requiring you to scroll down again to find where you were working. The chart now stays at your current scroll position when you refresh or save. Switching to a different planner view will still start you at the top of the chart, as before.
Grey demand (pegging) lines now remain visible when the supplying task scrolls off-screen (2672814)
When viewing a plan in the Gantt chart, the grey dotted line showing where a task's material comes from would disappear as soon as the supplying task scrolled out of view, making it difficult to follow demand across a long plan. The line now stays on screen and points towards the supplying task even when that task is outside the visible area — consistent with how blue dependency lines already behave.
Secondary resource requirements are no longer lost when a task is unplanned and replanned (2667491)
Tasks could silently lose their secondary resources when an order was unplanned and replanned. The task appeared correct while the plan remained open, but after saving and reopening (or copying) the plan, a replan would allocate only the primary resource — dropping any secondary resource requirement defined on the process.
Secondary resource requirements are now saved to the database alongside the rest of the plan. If requirements are found to be missing during a replan, they are automatically recovered from the task's existing allocations, preserving both primary and secondary resources with their original quantity and timing. Plans already saved without secondary resource requirements are repaired automatically as part of the database upgrade.
Tasks no longer drift forwards unexpectedly when a plan allows overloads (2679161)
When a plan was configured to allow overloads, editing or saving it could push unrelated tasks several days later. This drift accumulated on every save, causing resources to appear overloaded in seemingly random parts of the plan.
Tasks now stay where they are unless a change has genuinely broken one of their dependency links, in which case they still move to keep the link valid. Dates that had already drifted before this fix are not moved back automatically, but no further drift will occur after upgrading.