Release summary
Users can now add observations and attachments to Employee, Driver, Vehicle, and Equipment entities, keeping supporting information directly connected to day-to-day operations. The release also improves integration management with tenant- and center-level controls that prevent unnecessary validations in environments where integrations are not used, while adding integration details to Production Orders, Reception Planning, and Production Movements.
🆕 Improvements & New Functionalities
Support for Observations and Attachments in New Entities (Employees, Drivers, Vehicles, and Equipment)
Users can now add observations and attachments to Employee, Driver, Vehicle, and Equipment records, keeping relevant notes and supporting documents easily accessible within each entity.
Add Integration Information to Production Entities (Production Orders, Production Movements, and Reception Planning)
Users can now view integration information directly within Production Orders, Production Movements, and Reception Planning, making it easier to track connected data and verify integration status throughout production workflows.
🎯 Improvements
Improved Validation When Closing a Transport Organization So Integrations Aren’t Required to Close the Document
Transport Organizations can now be closed without requiring integration data, preventing unnecessary validation errors for environments where integrations are not configured or used. NOTE: The system enforces integration when an ExternalCode is configured in DocumentSerie.
Improved SSCC Validation Across Stock Movements to Prevent Duplication
Improved SSCC validation now prevents duplicate codes from being created during stock movements, ensuring more accurate stock traceability and avoiding inconsistencies in inventory records.
Improved Stock Existence Reports by Excluding Materials Without Stock
Stock existence reports now exclude materials with no available stock, providing a clearer and more accurate view of current inventory while reducing unnecessary information.
Improved Label Printing to Automatically Support AI 3102 or AI 3103 Based on Weight
Label printing now automatically selects AI 3102 or AI 3103 based on the weight format, reducing manual configuration and helping ensure accurate barcode labels. NOTE: AI 3102 is used automatically when weight is greater than 999 kg; otherwise, the system uses AI 3103
Added New Filters to the Occurrence Management Page in the Back Office
New Group and Type filters make it easier to find and manage relevant occurrences in the Back Office, reducing the time spent searching through records.
Fixed an Issue Where Editing a User Changed the User’s Language
Editing a user no longer changes their selected language unexpectedly, ensuring that language preferences remain unchanged unless deliberately updated.
Improved Product Class Creation in the Back Office
Product class creation in the Back Office now correctly imports all selected batch attributes and displays the appropriate import window title, providing a clearer and more reliable configuration process.
Prevented Navigation to Partner Details Without Both the Partner and Partner Profile
Navigation to Partner details is now only available when both the Partner and Partner Profile are present, preventing invalid links and avoiding errors when required information is missing.