Administering Grid Layouts in EDGEBIC

EDGEBIC saves grid and panel layouts per user automatically, reconciles them against new columns on load so personalization survives an upgrade, and lets an administrator reset a drifted layout per view without touching anyone else. In EDGEBIC by User Solutions the grids that fill the job view, the work center screens, and the reports are not fixed. Each planner shapes them, EDGEBIC remembers the shape, and the administration of that behavior is light: know that it is per user, know that new columns still appear, and know how to reset one when it drifts.

This post is the administrator's view of layout persistence. For the full reference behind the controls here, read the EDGEBIC admin guide. It names controls that live in each view's configuration and the data-management screen, never any internal path.

Layouts Are Personal, and They Save Themselves

When a planner resizes a column, hides one, reorders them, or rearranges a docked panel, EDGEBIC remembers that arrangement for that user. The save is automatic. There is no Save Layout button to press and no risk of losing a change because someone forgot to save. On the next visit the view opens the way the planner left it.

Because layouts are per user, personalization is private. One planner widening the due-date column to read long dates does not shove a colleague's carefully packed layout around. This matters on a shared install: a team of eight can each shape the same job view to their own habit, and nobody steps on anyone. The administrator does not manage a single shared layout; the application manages one per person.

The scope is per view as well as per user. The job view, a work center screen, and a report each remember their own arrangement independently, so tuning one does not disturb the others.

Why New Columns Still Appear

The obvious risk with saved layouts is that they freeze the past. If a new version adds a column and every existing user has a saved layout from before it existed, would they all be stuck without it? EDGEBIC avoids that by reconciling.

On load, EDGEBIC compares each saved layout against the current set of columns. It keeps the widths and order the user chose, adds any columns that are new since the layout was saved, and drops any that no longer exist. The result is that a planner keeps their personalization through an upgrade and still sees the new feature. You do not choose between honoring saved layouts and shipping new columns; reconciliation gives you both.

This is worth knowing at rollout time, because it removes a task you might otherwise plan. When you upgrade a team and a new column arrives, you do not need to reset everyone to expose it. It appears on its own, alongside the arrangement each person already had. Upgrading is covered in upgrading EDGEBIC safely.

Resetting a Drifted Layout

Layouts drift. A planner hides a column during a busy week and forgets it, or reorders things past usefulness, or wants a fresh start. The fix is a reset from that view's own configuration, which restores the default arrangement for that grid.

Two properties make this safe. It is per user and per view, so resetting a planner's job view changes only that planner's job view and nothing else. And it is cosmetic, not structural: a layout reset rearranges the display and carries no risk to the underlying data. There is nothing to back up before a reset and nothing to recover after one. It is the lightest administrative action in the application.

For a wider clean-up, layouts can also be reset through the data-management screen, which is useful when several views on one machine have drifted. But the common case is a single planner and a single screen, and the single-view reset is the right tool for it.

What to Tell a New Planner

Layout persistence is one of the small things that makes a scheduling application feel like the planner's own tool rather than a fixed report. When you onboard someone, three sentences cover it.

• Arrange each grid however you read best; it saves itself and it is yours alone.
• New columns will show up on their own after an upgrade, keeping your widths.
• If you scramble a view or hide something you need, reset that view from its configuration and start clean.

That is the whole story from the user's side. From the administrator's side, the story is even shorter: layouts are per user, they reconcile against new columns, and a reset is a per-view, no-risk cosmetic action.

A Small Feature That Earns Its Keep

Grid layout persistence is not the headline of a scheduling platform, but it removes a daily friction. A planner who has shaped the job view to show exactly the columns their plant cares about, in the order they scan them, works faster and misreads less. That the arrangement survives upgrades and stays private to each user is what keeps it useful across a team and across years.

For how the rest of a planner's environment is set up, see onboarding users and roles, and for the broader picture of an organized scheduling workspace, read what production scheduling is. The full administrator reference is the EDGEBIC admin guide.