Release 2026.32 is focused on the QMS module, delivering the next set of core quality capabilities. The release strengthens quality reporting, introduces validation and accountability over Quality Controls, brings quality feedback into daily operational workflows, and makes quality data reusable across processes.
🆕 Improvements & New Functionalities
🌐 Web Application
New quality reports — two new reports are available: Quality Occurrences and Quality Controls, the latter including the validation responsible and the overall compliance percentage in the report header, giving quality teams a consolidated view of what was executed and how compliant it was.
Validation of Quality Controls — Quality Controls now support a Responsible Operator and a Validated / Not Validated status, so the quality responsible can formally review and approve controls and everyone can distinguish validated controls from those still pending review.
QA feedback inside operational workflows — Reception, Production, Warehouse and Dispatch no longer show only “QA done / not done”: operators now see the QA result, deviation level, recommended action and block status directly in their workflow, including basic blocking of products/batches when the outcome is Analyze or Reject.
Reusable Quality Control answers — GlobalQualityControl inheritance was generalized so a new Quality Control can pre-fill compatible answers from a previous one across different entities:
Transport Organization → Vehicle Reception, instead of being limited to the Vehicle Reception → Reception Document scenario, reducing duplicated data entry and making behaviour consistent across flows.
🎯 Minor Improvements
🌐 Web Application
Stock level sorting — fixed an error when ordering stock levels by weight, improving reliability when reviewing warehouse stock.
Document quantity calculations — fixed an error that could occur when a product had more than one EAN active, ensuring quantities are grouped and calculated correctly.
Quality occurrence severity — corrected how severity is handled in form instance items, ensuring Quality Occurrences display and retain the appropriate severity.
🪩 Back-Office
Production Order Control Type options — fixed dropdown fields in the create and edit modal so they correctly load the available database values.
Consistent Document Type labels — standardized the label for packaging movement and tare control settings across the create, edit and details screens, reducing configuration ambiguity.













