Release Changes Requiring Customization Review
Early Awareness – Upcoming NDE Changes That May Impact Customizations
August 2026 Release
Main Menu Layout Changes
To maximize the number of entries displayed in the main menu, several UI adjustments will be introduced in the August release:
- The logo will be aligned to the left.
- Additional space will be allocated to the menu tabs to allow more menu entries to be displayed.
- The expanded drop-down menu will use the full available width and will be aligned with the first menu entry.
Action Required:
If you have implemented customizations in the header or main menu area, we recommend validating them in your July sandbox environment to ensure compatibility with these changes.
For example:
Before the change that will be implemented in the August release:

After the change is implemented In the August release:

Locations and Item Availability UX Improvements
The August release will also introduce several usability improvements to the Locations and Item Availability section, including:
- New labels for the Expand All / Collapse All actions.
- Updated display of the Filter by panel for both locations and item-level availability.
- Improved display of holding-level request options, such as Request Other and Digitize Other.
Action Required:
Institutions with customizations in the Locations, Availability, or Request sections should review and test their custom code in the sandbox environment before upgrading to the August release.
For example:



November 2026 Release
Upgrade to Angular 20
As part of our technology roadmap, Primo NDE is planned to upgrade from Angular 19 to Angular 20 in the November release.
This change may impact:
- Custom components
- Add-ons
- Extensions built using the NDE customization framework
Action Required:
All custom developments will need to be rebuilt and validated against Angular 20 for November 2026.
We plan to provide additional guidance and, after September, make available an environment that will allow customers to test and prepare their customizations ahead of the upgrade. Further details and timelines will be communicated in upcoming releases.
This wording keeps the message at an early awareness level while clearly highlighting the potential impact on customer customizations and the recommended actions.

