November 2025
Hello, these are the november 2025 Release Notes of NDD Print, we have a lot of news, and we hope you like it.
Here you can download the latest versions.
See a summary of all updates and click on the links to navigate each one.
NDD Print Epson 5.8.3
FIXES
NDD Print Releaser 5.30.9
FIXES
NDD Print Portal 360 Server 5.65.13
IMPROVEMENT
Increase in the number of characters in the “printer name” field
Addition of fields for integration via API quotas (QuotasWS)
NDD Print Portal 360 DC 5.78.0
IMPROVEMENT
NDD Print n-MF Kyocera 4.7.1
FIXES
NDD Print Epson – 5.8.3
Released on 25 November 2025
Fixes
Failure to perform connection test during mass addition of equipment
How did the problem happen? When attempting to add printers in bulk, the process failed because, even when the addition was made by IP, the system attempted to obtain the hostname of the equipment to store this information. If it was unable to resolve the hostname, the addition was interrupted, preventing the user from completing the addition by IP.
When did the problem ? During the mass printer addition process.
Where did the problem happen? In the equipment addition flow.
What was done to fix it? The process was adjusted so that when communication via hostname fails, the addition continues normally if the device is being added by IP. For addition by hostname, the behaviour remains the same: if it cannot be resolved, the device is not added.
Failure to add equipment due to administrator password
How did the problem happen? When attempting to add equipment whose password contained the special character #, the operation failed. This happened because, in order to verify that the printer was compatible, a request was sent via an HTTP link, and the special character broke the URL, returning an error.
When did the problem ? When attempting to add a printer.
Where did the problem happen? On the equipment addition screen.
What was done to fix it? An adjustment was implemented so that the request correctly handles links containing special characters, ensuring compatibility.
NDD Print Releaser – 5.30.9
Released on 24 November 2025
Fixes
Version control fix
How did the problem happen? After installing NDD Print Releaser, the “VersionControl” field in the Windows registry displayed an incorrect value.
When did the problem ? The failure only became apparent after installing add-on modules, such as MFs, which depend on this field to validate the version of NDD Print Releaser.
Where did the problem happen? The problem was not noticeable initially, only manifesting itself after installing add-on modules.
What was done to fix it? Adjusted the value received by the “VersionControl” variable in regedit
A communication failure with the NDD Print Host server was generated when attempting to print.
How did the problem occur? When releasing print jobs through the printer interface, an error was generated in communication with the NDD Print Host
When did the problem occur? When releasing documents in the client application installed on the printer.
Where did the problem occur? On the client screen for releasing documents retained in the printer.
What was done to fix it? Correction made to the information that was sent to NDD Print Host
NDD Print Portal 360 Server 5.65.13
Released on 24 November 2025
Improvement
Increase in the number of characters in the “printer name” field
What is the objective? To allow the “printer name” field to accept up to 300 characters in NDD Print Portal 360 Server, enabling the use of more descriptive names that adhere to printer network standards.
What was done? The limit of the “printer name” field was increased to up to 300 characters, allowing the use of more descriptive names that are aligned with network standards. The change includes validation with an error message if the limit is exceeded, applies to all screens, APIs, and reports, and ensures that the display and export of the name respect the new size without truncating or affecting the layout.
What will be affected?
Printer registration and editing screens in NDD Print Portal 360 Server.
APIs related to the ‘printer name’ field.
Reports and interfaces that display or export the printer name.
What is the impact on the environment?
Users will be able to use longer and more detailed names for printers, whereas previously they were limited to 150 characters.
Registration and editing experience more aligned with extensive naming standards.
No negative impact on reports or exports, as the limit is respected in all outputs.
Permission for SSO (Single Sign-On) authentication
What is the objective? To facilitate and streamline access to Portal 360, allowing users to log in using their corporate Windows credentials, without the need to enter their Portal login and password. In addition, integration with SSO improves security, reduces the need for multiple passwords, and ensures greater centralised access control.
What has been done? Support for authentication via SSO API has been implemented and integrated into Portal 360. Configuration parameters have also been added to web.config and .env to enable SSO and define the API URL.
The login flow was adjusted to allow direct authentication via a dedicated route (/sso) or via the ‘Corporate Login’ button on the home screen.
Support for Windows authentication in IIS was added, and the CORS module was configured for secure communication between the API and the Portal.
Specific keys were created for token validation, ensuring alignment between the 360 SSO API and the 360 Portal.
What will be affected?
360 Portal login screen: now features the ‘Corporate Login’ option.
Authentication process: users will be able to authenticate directly with their Windows credentials.
Environment configuration: SSO API must be installed and configured in IIS, and adjustments must be made to the Portal configuration files.
What is the impact on the environment? Reduced login time and greater convenience for users, resulting in centralised access control via Active Directory. This will reduce the risk of authentication errors and forgotten passwords.
Addition of fields for integration via API quotas (QuotasWS)
What is the objective? The objective of this improvement is to enable the QuotaWS WebService to provide quota information per user. This will make it possible to consult the data directly via integration.
What has been done? A new call has been implemented in the WebService called GetUserQuotas, which is responsible for returning the quota information associated with a specific user.
What will be affected? The change is restricted exclusively to the QuotaWS service. There are no changes to other WebServices or systems; only the addition of the new GetUserQuotas endpoint within the existing WebService itself.
What is the impact on the environment? No impacts on the current environment are expected. The change is evolutionary, with no change to existing behaviours, ensuring that integrations that already use QuotaWS continue to function normally.
Extend extensions for exporting reports
What is the objective? To provide new HTML report export formats (XML, CSV and TXT), offering greater flexibility and compatibility with different systems and data analysis tools.
What has been done?
The option to export reports in XML, CSV and TXT formats has been implemented, in addition to the existing Word, PDF and Excel formats.
The exported files retain all the information presented in the original HTML report.
The new export options are available in the same interfaces already used for exporting reports.
Adjustment to the interface so that when selecting Excel, CSV, TXT or XML formats, only all pages are exported (hiding the selection of specific pages).
Renaming of existing extensions to a more concise standard (visible to all customers):
Adobe Acrobat PDF → PDF
Microsoft Word → WORD
Microsoft Excel → EXCEL
What will be affected?
HTML report export functionality.
Names displayed in export options for all customers.
Customers with the new export enabled by database will have access to additional formats (XML, CSV and TXT).
What is the impact on the environment? Enabled customers will have access to new formats, expanding the compatibility of report usage. Non-enabled customers will continue to use the exports already available (PDF, Word, and Excel).
The export default remains PDF, ensuring consistency with current usage.
NDD Print Portal 360 DC 5.78.0
Released on 15 November 2025
Improvement
Inclusion of the user email field in the export report
What is the objective? To improve traceability and user management in export reports by adding a column with the user's email address.
What has been done? Added the ‘Email’ column to the export report available in NDD Print Portal 360.
What will be affected? It will now be possible to manage data using the Email field, as this information will now appear in the exported report.
What is the impact on the environment? No impact. No action is required on the part of the user.
Addition of fields for integration via API quotas (QuotasWS)
What is the objective? The objective of this improvement is to allow the QuotaWS WebService to provide quota information per user. This will make it possible to consult the data directly via integration.
What has been done? A new call has been implemented in the WebService named GetUserQuotas, responsible for returning the quota information associated with a specific user.
What will be affected? The change is restricted exclusively to the QuotaWS service. There are no changes to other WebServices or systems; only the addition of the new GetUserQuotas endpoint within the existing WebService itself.
What is the impact on the environment? No impact on the current environment is expected. The change is evolutionary, with no change to existing behaviours, ensuring that integrations that already use QuotaWS continue to function normally.
Inclusion of the printer location filter in the GetPrintJobs call of the web service (API) PrintJobsWS
What is the objective? To enable the use of the printer location field through integration, ensuring automated access to data.
What has been done? The PrinterLocation field has been added to the fieldsList parameter, enabling the search for printer information based on its location.
What will be affected? The GetPrintJobs call of the PrintJobsWS Web Service now includes the printer location filter, expanding the data options available in the query.
What is the impact on the environment? No impact for the end user. No additional action is required.
NDD Print n-MF Kyocera 4.7.1
Fixes
Failure to install the n-MF Kyocera module
How did the problem happen? When attempting to install the n-MF Kyocera module on an approved Windows Server (2016 or 2022), an error message was displayed indicating incompatibility with the operating system.
When did the problem ? During the installation process of the Kyocera n-MF module.
Where did the problem happen? On the installation screen, preventing the installation from proceeding.
What was done to fix it? Instead of obtaining the operating system information via the Windows Registry, a direct call to the machine being installed was implemented to identify the OS, since reading via the Registry failed even on approved systems.