Übersicht der Updates
📰 Summary
This release significantly advances the ePLR Check ecosystem by introducing granular customer-specific exceptions and enhanced reasoning for check results. We have streamlined the user experience with more intuitive submodule navigation and improved filtering capabilities across product lists. Additionally, the new Public API Get scope by reference numbers has been introduced to provide the basis for further automation potential within the ePLR-check, while backend optimizations to the invitation system ensure a more robust and reliable user onboarding process.
🆕 New features
- Customer-specific exceptions can now be managed directly within the Previous load restrictions list
- Detailed reasoning is now displayed within ePLR Check results to provide full transparency on why a product was allowed or forbidden
- The newly introduced public API Get scope by reference numbers allows users to retrieve the ePLR check scope by product reference number, including any required preloads and specific cleaning requirements
- Advanced search in the ePLR Check now automatically queries the PreProducts Database if no direct match is found in the local list
➕ Improvements and extensions to existing features
- Direct submodule editing allows users to jump straight to the relevant section, eliminating unnecessary scrolling
- Enhanced list filtering now includes the ability to search for blanks, helping users identify missing data like CAS Numbers or PLR-Master assignments
- Business Partner reference numbers are now integrated into the Previous load restrictions search for more precise entity selection
- Searchable request lists now allow filtering by receiver email and status to streamline the management of pending updates
- Clarified terminology for PLR-lists, now explicitly labeled as Master restrictions or Local restrictions based on their source
- Refined invitation system now uses a dedicated acceptance flag to prevent the premature deletion of pending users
🐛 Bug fixes
- History accuracy improved by correcting a backend error that displayed Transport Forbidden for allowed results in the history tab
- UI layout fixes resolved an issue where tags were overlapping with submodule menus in the new interface