What happens when you and a colleague open the same order
- User
- Admin
Whoever opens an order first gets the lock on it. Everyone else sees the order read-only, with the name of that person. That lasts until the person closes the order, their browser stops checking in for a minute, or someone clicks Take over.
Why only one person edits an inquiry
Since the release of 30 September 2026.
You work on an inquiry while it is in To validate. How an order reaches your ERP shows where that sits in the path of an order. If two people corrected the same inquiry at once, whoever saved last would overwrite the other's corrections. Neither would notice. For that reason, one person at a time holds the lock, and everyone else can see who.
The lock covers the whole inquiry, so on a split inquiry it covers every order. Hyperfox enforces the lock. While a colleague holds the lock, Hyperfox does not carry out your save, validate, reject or retry, and nothing changes. Reject in To validate then shows a message that names the colleague. The message tells you to try again once the colleague closes the inquiry.
What your colleague sees
In To validate, the Open by a colleague column shows the initials of whoever has an inquiry open. The list checks every 15 seconds. A colleague who opens the inquiry anyway gets the whole validation screen read-only. A bar at the bottom names the person who holds the lock and says since when they have the inquiry open. The bar offers Back to list and Take over. Meanwhile, the screen of the colleague keeps checking every 15 seconds. When you close the inquiry, the inquiry becomes editable for the colleague, with the orders as you saved them. Every message the bar can show is listed under Read-only states.
How the lock ends
The lock ends when you leave the inquiry: Close and go back, Back to list, or another page.
The lock also ends on its own. While its browser tab is visible, your open inquiry checks in every 15 seconds. After 60 seconds without a check-in, the lock expires. The next colleague whose screen checks in gets the lock. That happens when you close the browser, lose the connection, put the computer to sleep, or leave the tab in the background. A tab in the background counts too, because a hidden tab stops checking in. When you return to the tab, Hyperfox claims the lock for you again. If nobody took the lock, your unsaved changes are still there. The exception is an inquiry that was validated, rejected or retried in between.
Take over
Take over gives you the lock at once. Take over discards every change your colleague did not save. This cannot be undone. When to use it, and what each of you then gets on screen, is on The screen is read-only: a colleague has the inquiry open.
When the inquiry changed meanwhile
Since the release of 30 September 2026.
The lock sets who edits. It does not freeze the inquiry. While your lock had lapsed, a colleague may have validated or rejected the inquiry, or clicked Retry. Retry deletes every order of the inquiry, including the changes you saved, and replaces them with a new reading. Retry an order so Hyperfox reads it again from the start covers the rest of Retry. When your screen gets the lock back, Hyperfox loads the inquiry again. The screen becomes read-only with the reason, for example the name of the colleague who already validated the inquiry. Reject fails with the same reason. Save and Validate fail with "Save failed". Your unsaved changes belong to orders that changed since then, so Back to list is the way out.
If a retry finished after you opened the inquiry, the bar shows "This inquiry was reprocessed since you opened it." The bar then offers Reload, which discards your changes and loads the new orders.