May 2026

These are the May 2026 release notes of NDD Orbix.

See a summary of all updates and click on the links to navigate each one.

May 28, 2026

NDD Orbix portal:

IMPROVEMENTS

• New variables in the demand generation email rule

Integration APIs:

IMPROVEMENTS

• Adjustment to the return of site fields in the GET /v1/supply-demands endpoint of the Printers API

DCA and Cloud Connector agent (Windows version 1.2.20):

IMPROVEMENTS

• Update of the Microsoft .NET Runtime and Microsoft ASP.NET Core Runtime prerequisites to the latest version (Agent: DCA and Cloud Connector)

• Renewal of the digital certificate for the agent and services (Agent: DCA and Cloud Connector)

• Digital signature of agent Custom Actions (Agent: DCA and Cloud Connector)

FIXES

• Mirror classes did not correctly reflect the properties of the appsettings.json files (Agent: DCA and Cloud Connector)

• Incorrect capture of Ricoh device names (Service: NDD - Printer Monitor)

• Inconsistency in processing supplies marked as “other” and “unknown” (Service: NDD - Printer Monitor)

• Error loading supplies from the Brother DCP-L5602DN printer (Service: NDD - Printer Monitor)

• Failure to retrieve the serial number on Lexmark USB equipment (Service: NDD - Printer Monitor USB)

APPROVALS

• Approved USB printers (Service: NDD - Printer Monitor USB)

• Adjusted network printers models (Service: NDD - Printer Monitor)

May 18, 2026

NDD Orbix portal:

IMPROVEMENTS

• New columns for responsible persons in the computer grid

May 28, 2026

Improvements

New variables in the demand generation email rule

To make demand generation notifications more comprehensive and provide more operational context about the supply, we have added new variables to the Demands field in the email rule settings. The new variables available are:

• Current supply level

• Current supply yield

• Estimated end date of current supply

The content returned by the variables varies depending on the demand type:

• Replenishment demands: displays data for the current supply linked to the demand at the time the email is generated. If the current supply is not available, no content will be displayed.

• Safety demands: no content will be displayed.

To configure email rules, access:

• Conventional printers: Create sending e-mail rule when generating a printer supply demand

• Thermal printers: Create sending e-mail rule when generating a thermal printer supply demand

Adjustment to the return of site fields in the GET /v1/supply-demands endpoint of the Printers API

We have adjusted the GET /v1/supply-demands endpoint to change the return of the siteId and siteName fields based on the demand type:

• Safety demands: these fields will now return data from the site linked to the delivery location. If there is no linked site, the value null will be returned.

• Replenishment demands: the fields will continue to return data from the site linked to the printer.

Update of the Microsoft .NET Runtime and Microsoft ASP.NET Core Runtime prerequisites to the latest version (Agent: DCA and Cloud Connector)

The Microsoft .NET Runtime and Microsoft ASP.NET Core Runtime prerequisites have been updated to version 8.0.27, the latest version in the 8 series. The new version includes security fixes for previous versions.

Renewal of the digital certificate for the agent and services (Agent: DCA and Cloud Connector)

We have renewed the digital certificate used by the agent and services, updated the internal library responsible for certificate management, and implemented dual signing for the DCA and Cloud Connector installer.

Digital signature of agent Custom Actions (Agent: DCA and Cloud Connector)

We have made improvements to the digital signature process for Custom Actions (CAs) used during DCA and Cloud Connector installations, updates, and uninstallations.

With this adjustment, all agent and service CAs are now digitally signed, increasing compatibility with security policies in restricted environments and preventing blockages during the execution of installation processes.

Fixes

Mirror classes did not correctly reflect the properties of the appsettings.json files (Agent: DCA and Cloud Connector)

DCA and Cloud Connector have mirror classes for the appsettings.json files of each service. These classes were not correctly mirroring the properties present in the services appsettings.json files.

To fix this, we adjusted how appsettings.json files are handled, ensuring that all existing configurations are correctly preserved when the agent manages the services.

Incorrect capture of Ricoh device names (Service: NDD - Printer Monitor)

On Ricoh equipment, the device name was not always captured correctly using the default OID applied to other manufacturers. As a result, the device name might be displayed incorrectly or not retrieved during monitoring.

To fix this, we implemented a specific validation for Ricoh equipment. With this adjustment, the device name is now captured primarily using the default Ricoh OID. If this OID does not return a value, a fallback to the default OID used by other manufacturers will be performed automatically.

Inconsistency in processing supplies marked as “other” and “unknown” (Service: NDD - Printer Monitor)

During the processing of equipment supply information, items marked as “other” were discarded by the system, preventing them from being correctly included in the processing.

To fix this, we implemented a specific handling process for supplies identified with the colors “other” and “unknown”. Following this adjustment, these colors are now processed as “NoApply”, preventing the supplies from being discarded and ensuring they are processed correctly by the system.

Error loading supplies from the Brother DCP-L5602DN printer (Service: NDD - Printer Monitor)

While capturing supplies from the Brother DCP-L5602DN printer, the data returned by the printer in hexadecimal format was not interpreted correctly, causing a conversion error.

To fix this, we adjusted the conversion of the hexadecimal data. With this adjustment, the information is now captured normally.

Failure to retrieve the serial number on Lexmark USB equipment (Service: NDD - Printer Monitor USB)

During the USB equipment monitoring process, when the serial number was not returned during the initial collection, the system would make a second attempt using PJL commands as a fallback. On Lexmark equipment, this behavior caused communication failures and instability in the collection process due to the incompatibility of these devices with PJL commands.

To fix this, we added a specific validation for Lexmark equipment. With this adjustment, when equipment from this manufacturer does not return the serial number during the initial collection, the system will no longer perform a second attempt using the PJL INFO CONFIG command. In this situation, a log entry will indicate that the serial number was not collected, and a new attempt to obtain it will be performed automatically during the next monitoring cycle.

Approvals

Approved USB printers (Service: NDD - Printer Monitor USB)

Adjusted network printers models (Service: NDD - Printer Monitor)

May 18, 2026

Improvements

New columns for responsible persons in the computer grid

To make it easier to identify and manage the persons responsible for devices, we have added two new columns to the grid in the Monitoring > Computers > Devices menu:

• Responsible name

• Responsible email

The information displayed in these columns reflects the data entered on the Info tab of the computer's properties.

To view or change this information, go to View computer inventory.