March 2023

What purpose? Perform data processing of meters and supplies separately, in order to avoid queues in the existing data processing of printers and products/compatibilities and to speed up the display of new printers registered in the NDD Orbix portal.

What was done? Created a new specific data processing for meters and supplies, in order to keep the data processing of printers and products/compatibilities separate.

What will be affected? The data processing of meters, supplies, printers and products/compatibility will be faster.

What is the impact on the environment? There isn't one.

Observations? There isn't one.

Fixes

Abrupt variation in the values of reference meters

How did the problem happen? There was an abrupt variation in the values of reference meters, impacting the visualization of printed pages.

When did the problem happen? By having a reference rule that has no flexibility to perform the meter calculation, if a reading arrived and it had a zero meter, the reference was left as unprocessed, not saving the initial and final values in the database. By setting this rule to flexible, to perform the meter calculation even in the absence of values, when a new reading arrived, the initial meter value was not updated, performing an erroneous calculation of printed pages.

Where was the problem? In the rules of the Settings > Reference meters menu, reflecting the value shown in the “Printed pages” indicator of the Panels menu.

What was done to fix it? When there is a rule that is not flexible, the meter value comes reset to zero and is present in a rule, when adjusting the rule to flexible and a new reading comes in, the initial value will be adjusted to the same value as the final meter, impacting the printed pages calculation.

Display of removed supplies on the grid

How did the problem happen? The system was not applying the filter to not show removed supplies, generating duplication of items and joining active items with inactive/invalid items.

When did the problem happen? When there was an ending supply demand requested, and the printer received histories of readings that generated invalid supplies and readings that were disabled by the advanced change correction system, it generated the marking of the supply as "removed".

Where was the problem? In the grid of the Supplies > Demand planning menu.

What was done to fix it? Updated the system so that removed supplies are not shown in the grid.

March 20, 2023

New features

Consumption of supplies in use and exchanged through integration

What is the new functionality? Enable the user to consume the data of supplies currently in use and the supplies exchanged in the printer fleet in a period.

What is the benefit of the new functionality? Perform the consumption, through integration, of the list of supplies in use or supplies exchanged in a period, with the intelligence and assertiveness of the NDD Orbix indicators.

How does the new functionality work? The "SupplyExchanges" call was included in the Printer integration API.

March 8, 2023

Fixes

Error in updating the site and the unit of computers

How did the problem happen? After updating the site and the unit of one or more computers, the information was not updated in the grid of computers and in the details of the affected computers.

When did the problem happen? After changing the site and/or the unit of one or more computers.

Where was the problem? In the grid in the Devices > Computers menu and when opening the computer details in the Devices > Computers > Select computer > Open > SUMMARY tab menu.

What was done to fix it? Corrected the rules for processing computer updates.

March 6, 2023

Improvements

DCA and Cloud Connector SDK version update

What purpose? Improved the logs displayed and fixed the incident where it was not possible to change the log levels by NDD Orbix.

What was done? Updated the nddSmart.Agent.SDK to version 5.11.9.

What will be affected? Projects that use the nddSmart.Agent.SDK will now use version 5.11.9 of the component.

What is the impact on the environment? You need to update DCA and Cloud Connector to version 1.0.1.

Observations? There isn't one.

DCA and Cloud Connector LiteDB version update

What purpose? Updated the database component (LiteDB) to the latest available version in order to improve the incident search.

What was done? Updated the database component (LiteDB) to version 5.0.15.

What will be affected? Projects that use LiteDB will now use version 5.0.15 of the component.

What is the impact on the environment? You need to update DCA and Cloud Connector to version 1.0.1.

Observations? There is no note in the version that is specific to the incident.

Workstation Agent SDK version update

What purpose? Improved the logs displayed and fixed the incident where it was not possible to change the log levels by NDD Orbix.

What was done? Updated the nddSmart.Agent.SDK to version 5.11.9.

What will be affected? Projects that use the nddSmart.Agent.SDK will now use version 5.11.9 of the component.

What is the impact on the environment? You need to update Workstation Agent to version 1.0.3.

Observations? There isn't one.

Changing the view of meters information in the printer summary

What purpose? The goal is for the user to have a view of the main indicators within the printer summary screen, in particular the meters indicator.

What was done? Changed the meters indicator to include reference and readings meters data.

What will be affected? The "Meters" indicator in the Devices > Printers > Select printer > Open > SUMMARY tab menu.

What is the impact on the environment? There isn't one.

Observations? There isn't one.

Changing the view of supplies information in the printer summary

What purpose? Better organize the supplies information in the printer summary.

What was done? Changed the supplies indicator to show the data in a grid.

What will be affected? The "Supplies" indicator in the Devices > Printers > Select printer > Open > SUMMARY tab menu.

What is the impact on the environment? There isn't one.

Observations? There isn't one.

More complete "Usage time" and "Period of use" fields

What purpose? Make the fields "Usage time" and "Period of use" more complete.

What was done? The fields were adjusted to consider the time/period in years and months. Previously the fields showed only the time/period in years, without the months, such as "1 year". After the update, it will show the time/period in years and months, for example "1 year 1 month".

What will be affected? All places where the fields "Usage time" and "Period of use" exist, as below:

Devices > Printers > Select printer > Open > SUPPLIES tab > IN USE > Select supply > Open > SUMMARY tab
Devices > Printers > Select printer > Open > EXCHANGED tab > IN USE > Select supply > Open > SUMMARY tab
Supplies > Supplies running low > Select supply > Open > SUMMARY tab
Supplies > Demand planning > Select supply > Open > SUMMARY tab
Supplies > Completed demands > Select supply > Open > SUMMARY tab
Supplies > Premature exchanges > Select supply > Open > SUMMARY tab

What is the impact on the environment? There isn't one.

Observations? In languages, it was used between years and months:

"e" for Portuguese. Example: 1 ano e 1 mês.
"y" for Spanish. Example: 1 año y 1 mes.
in English the "and" was not used. Example: 2 years 2 months.

Changes to the view of indicators in the summary of supplies running low

What purpose? The goal is for the user to have the view of the main indicators within the summary screen of the supplies running low.

What was done? Three changes were made in the supply summary:

inverted the position of the "Supply information" indicator with that of "Printer";
added the information about the last read update in the "Printer" indicator;
added the icon and information about the printer type (if Manual, Network or USB), the monitoring status (if Monitored or Not monitored) and the connection status to the "Printer" indicator.

What will be affected? The "Supply information" and "Printer" indicators in the Supplies > Supplies running low > Select supply > Open > SUMMARY tab menu.

What is the impact on the environment? There isn't one.

Observations? There isn't one.

New last reading column in supplies running low grid

What purpose? Show the data of the last supply reading in the supplies running low grid.

What was done? Added a new column "Last reading" in the supplies running low grid.

What will be affected? The grid in the Supplies > Supplies running low menu.

What is the impact on the environment? There isn't one.

Observations? There isn't one.

Fixes

Reading supplies with too many items crashed the API

How did the problem happen? On some devices the supply list exceeded 50,000 items with blank reads, causing the NDD Orbix API to crash.

When did the problem happen? We caught the incident on a specific model, but the incident could occur with any equipment during the readings of the supplies information.

Where was the problem? When reading supplies from the equipment.

What was done to fix it? Implemented limitation so that the supplies readings send a maximum of 30 items in the list.

March 1, 2023

Fixes

Future dates in the last computer communication field

How did the problem happen? Future dates were shown in the last communication field with the computer.

When did the problem happen? If the computer had an incorrect date, a future date was shown in the last communication field of the report.

Where was the problem? In the "Computer inventory" report from the Reports > Standard menu.

What was done to fix it? The conversion of date and time values was carried out according to the time zone where the user is located.

Loading screen indefinitely when searching for printers

How did the problem happen? After installing a new printer agent (DCA and Cloud Connector) and trying to search for printers, it would only show the loading screen indefinitely. After a few moments, the screen would reload normally, if the page was reloaded.

When did the problem happen? When accessing the printer search in the printer type agent settings, right after its installation.

Where was the problem? In the "PRINTER SEARCH" option in the Agents > Services > Select the NDD - Printer Monitor service > Open > SETTINGS tab menu.

What was done to fix it? Created a new processor to receive messages specific to the printer monitoring module, so that the server-side agent creation processing is isolated to a faster processing component. This way, it is expected that by having a specific queue for messages that create an agent and assign printers to the agent, these messages will not need to wait in the queue for other processing of the module (supplies, reads, etc.), and thus it will be possible to perform the proper configurations.