Why Planner View Focus Is Never Saved in EDGEBIC

Click a bar on the EDGEBIC by User Solutions Planner board and the machine block re-orders around that operation. Click it again and the order goes back. Nothing in between is ever saved. The re-ordering is a way of looking at the board, not a setting, and EDGEBIC is careful to keep that line clean.

It is a small design decision with an outsized effect on whether people trust the software, which is why it deserves its own explanation rather than a footnote in the Planner view overview.

What Focus Actually Does

Clicking an operation's bar re-sorts the machine block so the machines relevant to that operation sit directly under the job lanes: the machine it currently runs on, then the other active members of that machine's work center group, then the rest of that job's routing. Each floated lane gets a small triangle in front of its caption. The mechanics are in how to float the machines that matter.

What it does not do is equally specific. It does not add or remove a lane. It does not change any operation. It does not write to your configuration. It does not mark anything unsaved. It does not survive a click on the same bar, and it does not follow you to tomorrow.

The Failure It Was Designed Around

Consider the version of this feature that does persist. You click a bar to see your options, the lane order changes, and the configuration is now marked dirty because a persisted ordering just changed. Apply & Save lights up.

You did nothing but look.

That behavior is corrosive in a way that is easy to underestimate. Once a read-only gesture can light up an unsaved-changes indicator, the indicator stops meaning anything. People learn that it fires for no reason, so they stop reading it, and then they either save reflexively, which quietly persists whatever else was on the screen, or dismiss it reflexively, which discards a real edit somebody made earlier. Either way the warning has been trained out of usefulness.

So EDGEBIC keeps the two categories apart. Looking never dirties. If the unsaved-changes indicator is lit, something genuinely was edited, and it is worth going to find out what.

This is the same treatment expanded group lanes get on the Resource Group board, and the reasoning transferred deliberately rather than being re-derived.

Ways of Seeing Versus Settings

The distinction is worth generalizing, because it applies well beyond one click.

A setting is a decision you want to keep. It should be explicit, it should persist, it should be shareable, and changing it should be a deliberate act with a save behind it. On the Planner board the durable lane ordering is a setting: you set Seq.No in the Detail Schedule Resources grid on the Configuration sub-tab, and you click Apply & Save.

A way of seeing is a temporary arrangement in service of the question in front of you right now. It should be instant, reversible with the same gesture that created it, and invisible to everyone else. Focus is a way of seeing.

Mixing them produces the worst of both. A setting that changes without a save is unpredictable. A view state that demands a save is friction on every glance.

The two do not fight. Release the focus and the machine block returns to exactly the Seq.No order you saved.

Your Pending Work Is Safe Through It

The second reassurance matters more in practice than the first.

Focusing the board re-orders lanes that are already on screen. It is not a reload. Nothing is fetched, no bar is rebuilt, and the pending set is not rebuilt either.

That means staged but unsaved drags survive the click untouched. If you had moved three operations and not yet saved, then clicked a bar to check an alternative machine, all three are still pending, still counted on the toolbar, and still ready for Save Changes. Releasing the focus is equally safe.

This is what makes the click usable mid-decision. You can stage a move, click around to check whether it was the right move, and either save or Discard the whole set with the same confidence you had before you clicked. The staging model itself is covered in staged changes on the Planner board and staging Gantt changes with save and discard.

The Escape Hatch Is the Same Gesture

One more property worth naming: a second click on the same bar always releases the focus. There is no state in which the board is re-ordered and you cannot get it back.

That is not a small thing on a board with a long machine list. A planner who re-orders twenty lanes and cannot find the reset is a planner who reloads the screen, loses their pending changes, and stops using the feature. Making the release identical to the trigger removes the whole class of problem: whatever you did, do it again.

Clicking a different bar does not release, it re-focuses on that operation instead, which is usually what you want when you are working through several moves in a row.

What to Take From It

If the unsaved-changes indicator is lit on your Schedule View configuration, believe it. It did not fire because you clicked a bar to see where a mill operation could otherwise run. Go and look at the Configuration screen before you save, because something on it was genuinely edited.

And if you want a lane order that lasts, say so explicitly with Seq.No and Apply & Save. The board will honor it, and every focus click will hand it back to you when you release.

User Solutions has been building scheduling tools with manufacturers since 1991, in small shops and in organizations including the US Navy, GE, BAE Systems, and Cummins, and the habit behind this rule is one of the oldest: never make a person save something they only looked at.

See the full EDGEBIC platform, start with the visual scheduling pillar guide, or bring your shared Gantt configuration to a demo and let US show you which of its settings are decisions and which are just views.