How errors and warnings decide whether you can validate an order
- User
- Admin
One order stops you at Validate while another only shows a warning, because Hyperfox checks every order in two ways. Errors come from checks that set whether the order can go to your ERP. Warnings come from checks that only ask you to look again. Only errors block Validate. Where each message shows on the screen is described under Errors pane.
Errors, warnings and info
An error means the order cannot go to your ERP as it is. A field that must be filled is empty, or a value is not allowed. You clear an error by correcting the field. While one order of the inquiry has an error, Validate stays disabled for the whole inquiry.
A warning means the value may be right but needs a check against the document. Info is a note to read. Neither blocks Validate, and neither disappears when you correct the field. A warning is not a verdict on the value, so it can stay on a field that is correct.
Each message sits on the field it is about. A message about the order as a whole, or about a field the screen does not show, appears in the banner above the form. The errors pane lists them all, errors first. The order tab shows how many errors that order has. If the order has no errors, the tab shows how many warnings it has.
Checks built into Hyperfox
Your order model sets which fields an order must have. When you open an inquiry, Hyperfox checks every order against the order model. It checks fields that are required or may not stay empty, and values that must come from a fixed list. It also checks that dates and numbers have the right format. Every problem becomes an error, for example "Customer is required". Hyperfox runs the same check when you click Save, and once more when you click Validate. An order that is not complete therefore never reaches your ERP. An error from this check stays on its field until Hyperfox checks the order again. When that happens, A field stays red after you filled it in gives the fix.
Some environments have checks of their own on top of the order model. Hyperfox sets up these checks. The best known is the unit check. In a stock order, a line may only use a unit of its item. Hyperfox already corrects the unit after it matches the order. The unit check: why boxes can become pieces explains that correction. If the item and the unit no longer fit after you change one of them, the line shows the error "Unit is not valid for this item". These checks follow your edits. The error appears and disappears as you change the line.
One warning is built in too. Some pickers only list the records that belong to another field, such as the delivery addresses of the customer. For such a picker, your admin can switch on Warn on multiple options. The field then shows "Several options are possible. Check the selection." whenever more than one record fits. The warning counts how many records fit, not which one you chose. The steps for the setting are in Switch a picker filter on, off or to enforced.
Rules your admin adds to the AI mapping
Every field of an AI mapping, and the order as a whole, can carry warning rules. Your admin writes them under Warnings in Admin settings > Mappings. A rule has a condition in plain words and the message you see when the condition holds. A rule on a field shows its message on that field. A rule on the Order row is for the order as a whole. It shows its message in the banner above the form.
After Hyperfox has read and matched the order, it checks for every rule whether its condition holds. It reads the finished order for this check. A rule can therefore compare two values on the order or test whether a value is missing. For a picker limited to the records of the customer, the check also receives the number of records the customer has. A rule such as "the customer has more than one delivery address" rests on that count. The message appears word for word as your admin wrote it, in the language your admin wrote it in.
These rules run once, when Hyperfox reads the inquiry, and again on every Retry. Your corrections do not run them again. If the check of the rules fails, the order still reaches To validate, without warnings. A missing warning therefore does not prove that the order is right.
Rules in the AI mapping only give warnings, so a rule saved as Info never shows. A rule cannot block Validate.
What blocks Validate
Only errors block Validate. They come from the checks of your order model and the checks Hyperfox set up for your environment. Warnings and info never block it, whether they come from Hyperfox's reading, from a rule in the AI mapping or from Warn on multiple options. If any order of the inquiry has an error, Validate stays disabled. Validate is disabled: "Resolve all errors to validate" says what to do then.
An error has to be cleared before you can validate. A warning asks for a comparison with the document. When the two match, the order is right and the warning stays.
Why a warning on a correct order keeps coming back
A warning rule describes a situation, not a mistake. When the condition holds for the next order too, Hyperfox shows the warning again, even when that order is right. Validating does not make it skip the warning. Codex learns which record you choose for a customer, an item or a unit. Codex has no effect on warning rules. How Codex learns from your corrections describes what Codex does record. The same goes for Warn on multiple options. While the customer has several records that fit, the warning shows on every order of that customer.
If a warning keeps showing on orders that are right, the rule is too broad. Your admin can make the condition narrower or delete the rule. A changed rule applies only to inquiries Hyperfox reads after the change. How a changed rule applies is explained in The safety net.
Where a new check belongs
A check that only signals something is a warning rule in the AI mapping. Examples are a delivery on the same day as the order, or a quantity above 1,000 on one line. Your admin writes the rule, because operators cannot open Mappings. What to ask your admin for is under A field or the order shows a warning.
A check that must stop the order cannot be a warning rule. Only the order model and the checks Hyperfox sets up for your environment can block Validate. What you can configure, and what Hyperfox configures lists what Hyperfox sets up.