August 2025

In some scenarios, certain services were installed with the Startup Type (ST) set to Automatic, or had this setting changed by the user. However, the responsibility for starting or stopping these services lies solely with the DCA and Cloud Connector agent. Therefore, only the agent should remain with the ST set to Automatic, while the services should be set to Manual.

Starting with this update, during service monitoring, the DCA and Cloud Connector agent will automatically check the ST of each service. If it identifies any services set to Automatic, it will automatically correct them to Manual.

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.0, as instructed at Update the agent or gateway on portal.

Fixes

Services running with incorrect information in memory prevented activation (Agent: DCA and Cloud Connector)

In some scenarios (likely caused when the Startup Type (ST) of a service was set to Automatic), certain services ran with incorrect information in memory, which prevented them from activating.

Example:

The DCA and Cloud Connector agent installation is started and the NDD - Printer Monitor service is installed with the ST set to Automatic. Because it is in this mode, the service starts immediately after installation, before the agent assigns the correct information in the appsettings.

The service runs and attempts to communicate with the NDD Orbix portal, but fails due to incorrect data.

Although the agent updates the service's appsettings, since it is already running, the information loaded into memory remains incorrect.

This prevents the service from activating due to incorrect information.

Now, on every monitoring, the DCA and Cloud Connector agent will validate the following essential information for each service:

Tenant (provider)
OrganizationId (customer key)
NDD Orbix URL
IsEnabled (indicates whether the service is enabled in the NDD Orbix portal)

If any discrepancies are identified, the agent will update this information in the appsettings of the respective service. If the service is running (enabled in the portal), it will be restarted so that the correct information is loaded into memory. If the service is stopped (disabled in the portal), nothing happens.

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.0, as instructed at Update the agent or gateway on portal.

August 07, 2025

Fixes

Inconsistency in the calculation of pages with savings in the EcoPrint Comparative report (Service: NDD - Supply Watch)

In the EcoPrint Comparative report, we identified that the number of pages with savings recorded in the period was higher than that indicated by the printer meter. The analysis showed that the same accounting (number of pages printed with savings) was being saved in the database several times.

The problem occurred when sending data from the NDD - Supply Watch service to the NDD Orbix portal. In situations of high usage volume, the process could not handle the level and resent the same information repeatedly, resulting in duplicate data.

To correct this, we made improvements to the NDD - Supply Watch service to support high data levels, created mechanisms to prevent duplicate data from being sent, and implemented the sending of a unique identifier for each accounting sent to the NDD Orbix portal.

In addition, we performed optimizations and performance improvements to speed up data processing, and included mechanisms to identify duplicates using the unique identifier implemented, discarding repeated readings.

The DCA and Cloud Connector (Windows) agent must be updated to version 1.1.31 and the NDD - Supply Watch (Windows) service to version 1.2.1, respectively, as instructed at Update the agent or gateway on portal.

August 04, 2025

Improvements

New fields in the response of the GET /v1/organizations/{organizationId}/printers and GET /v1/printers endpoints of the Printers API

To make the response more complete and facilitate data integration and consumption, the following field has been added to the return of the GET /v1/organizations/{organizationId}/printers and GET /v1/printers endpoints:

siteId: identifier of the site where the printer is located.

Developer Portal ➝