Step Validation

Creating correct registrations is key when working in the warehouse. Therefore the application contains a lot of different types of validation to match any need. Most validation can be done without the need for network access, and relies on the data object (e.g. an order line) and the workflow which for planned work is setup in the configuration files. There is also a fleet of online validation, which of cause requires network access, but adds the possibility for backend logic.

Offline validation

The level of validation is defined by the workflow and the data object from which the registration is created. If a registration is created for an order line which is serial number controlled, specific offline validation is enabled by default like only allowing one registration with the same value. This can of cause be overwritten, in those cases where that does not make sense. Specifically for the serial number that is done on the service level.

Controlling a specific barcode format can also be done through validators for order lines, utilizing the BarcodeFormat element.

Besides being controlled from the data object, specifics in the workflow can also affect validation, such as min/max value.

See Offline Validation validation for more information.

Online validation

Sometimes, offline validation is not enough, and backend logics is needed to have the confidence that the registration will be correct. In those cases online validation can be enabled, which will allow the application to contact the backend when creating a registration. The request to the backend can be setup to contain all previously collected values until that step, enabling it to make an informed decision about whether the current registration will be correct.

See Configure Onlinevalidation for setting it up.