How to Batch Your Gantt Edits Before Saving in EDGEBIC

EDGEBIC by User Solutions stages Gantt edits by default: each drag becomes a pending overridden change and nothing reaches the database until you press Save Changes. That review step is a setting, not a law of nature, and it can be turned off. This is where it lives, what the alternatives do, and how to keep the safety net on the machines that need it.

For the drag itself, see how to move a job on the Gantt chart. Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• Jobs are scheduled, so there are bars to drag.
• You know what a drag writes. The drag mode selector decides whether a saved drag records actual dates or a planned pin, which is a separate setting covered in how to change the drag mode on the Gantt.
• You understand the model: the Gantt is override and warn. It will let you make a questionable move and tell you about it, rather than block you.

Step 1: Open the Display Configuration

Open the Schedule area, select the Schedule View sub-tab, then the Configuration tab beside the scheduler. This is the display and interaction home, and nothing in it changes what the engine computes. Site-wide scheduling policy lives in Settings instead.

Go to the General tab and find the Host Scheduler card.

Step 2: Set the Three Settings That Matter

Keep Multi on any shared planning station. Batch save with a review step before committing is the standard way to work an interactive schedule, and it is the only thing standing between a mis-drop and a written record.

Step 3: Apply the Configuration

Click Save and Apply Now Configuration at the bottom of the tab. Reset to Defaults returns the factory settings if an experiment goes sideways, and Import and Export move a whole configuration between machines, which is worth doing once you have it tuned. See how to copy your scheduler display settings.

Step 4: Work a Batch

With Multi mode on, the loop is:

1. Drag a bar to its new slot, or onto another work center's lane. The bar takes the Overridden state and the pending-changes count on the toolbar goes up.
2. Repeat for as many operations as the change needs. Everything stages together.
3. Read the whole pending set before committing. This is the point of the mode.
4. Click Save Changes to write them all, or Discard to snap every pending bar back where it was.

There is no per-bar undo inside a pending set. Discard reverts all of it, which is another reason to keep batches small.

Step 5: Read the Post-Save Warning

With Scheduler Update Warning on, a batch save that leaves operations in a questionable order pops a list of the affected jobs. It is a time-order heuristic, not a dependency check, so treat it as a prompt rather than a verdict.

The correct response is usually the Re-Schedule button, which re-plans the jobs you touched and leaves the rest of the plant alone. The engine honors your saved changes and re-flows everything around them.

What Changes When You Save

Saving writes the dates for exactly the bars you moved, according to the drag mode. The engine's original scheduled dates are kept alongside, so the system always knows plan against reality. Bars move from Overridden to a saved state, later operations in the same job take a Downstream Changed review flag, and every save writes an audit event.

One thing a save does not do: it does not re-check or re-balance capacity. You may have knowingly overloaded a machine, and that is the override-and-warn contract working as designed. Run a reschedule when you want the engine to plan around your changes.

How to Check It Worked

Drag one bar and look at the toolbar. In Multi mode the pending count increments and Save Changes becomes available. Navigate away without saving and come back: the bar should be where it started, because pending changes live only in memory. If a single drag persists with no save click, Auto Update is on with Single mode.

Common Mistakes

• Leaving pending changes on screen at the end of the day. They exist only in memory and are gone when the application closes.
• Expecting a save to validate feasibility. It records dates. Capacity is resolved by the next scheduling run.
• Ignoring the Downstream Changed flag. It marks operations that may now be out of order. Either drag them too or run a reschedule.
• Turning on Auto Update to save clicks. The click is the review, and on a planning desk it is the cheapest safety in the product.
• Assuming the setting is site-wide. Display configuration is per machine, so a colleague can be working a different way at the next desk.

See how staged edits, reschedules, and audit history fit together on the EDGEBIC product page.