Acknowledging conflicts

Not every conflict gets resolved. Sometimes the double booking on Friday has simply been talked through and accepted. That is what the "Acknowledge" button is for: in the sidebar under Conflicts on the affected entry, as well as in the "Conflicts" tab on the order and in the resolve dialog.

What happens

The conflict remains in place but no longer counts as open. It disappears from the tiles and from the number on the menu item, while the row stays visible in the list, marked "Acknowledged" together with name, time and note. An optional note (up to 500 characters) records why the decision was made, for example "discussed with the foreman, team will help out". In the resolve dialog, acknowledging happens without a note.

An acknowledged conflict stays quiet: it does not appear in the morning conflict preview and does not trigger a notification when it draws closer and becomes more urgent.

Admins, planners and team leads may acknowledge by default. Purchasing/Warehouse also finds the Conflicts page in the sidebar and sees all of the company's conflicts there, as in the "Conflicts" tab on the order. The role cannot acknowledge; via "Resolve" it can use „Auf „Zu bestellen“ setzen“ (set to "To order") for material shortages, while the other suggestions are locked. Employees only see conflicts concerning themselves and their own items, as a "Conflict: …" label under My Work, and do not acknowledge anything.

"Assign anyway" acknowledges automatically

Anyone who deliberately schedules a person despite a booking or an absence has already seen the conflict. This concerns two confirmation prompts:

• in the "Schedule Order" dialog: "Assign despite conflict?"
• on the item in the "Assignments" section: "Assign despite absence?"

If you confirm there with "Assign anyway", the conflict is still created (the boss should see that someone on vacation has been scheduled), but Gantway acknowledges it immediately in your name with the note "Consciously confirmed when assigning ("Assign anyway") — absence/booking was known." It then does not count as open and does not trigger a notification.

Two exceptions in which the conflict stays open:

• The date shifted during scheduling. Your confirmation then applied to a different day. Gantway reports: "Deliberate assignment despite booking not acknowledged: the date was moved — please check the conflicts at the new date."
• You lack the right to acknowledge. You may still assign; the conflict stays open and is reported as usual.

Revoking

"Revoke acknowledgment" makes the conflict open again at any time, for instance when the arrangement does not hold after all. The row then carries the note "Acknowledgment withdrawn", so it stays visible that a decision was made. An already acknowledged conflict cannot be acknowledged twice; Gantway then reports "Conflict has already been acknowledged by you."