Samsung CLX-4195 Fleet Admin Pro Release Notes - Page 5

Release Notes_5

Get Samsung CLX-4195 PDF manuals and user guides View all Samsung CLX-4195 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 5 highlights

1.00.050 1. The Device Detailed Usage report issue, caused by incorrect device data processing, was fixed. If the System received incorrect data from a device, this data was displayed in the report and could not be updated after receiving the correct data next time. As a result, the device total usage count in Device Total Usage report greatly exceeded the device usage count in the Device Detailed Usage report. Now the report data is displayed correctly. However, you might not see the historical device usage data per certain date. The missing data will be displayed upon the scheduled device data collection. The issue affected Samsung CLX-9201 model. Other models could have been affected as well. 2. The Device Detailed Usage report issue, caused by deadlocks in 1.0.38, was fixed. The System failed to update the Device Detailed Usage report data after a device had been added. As a result, the same way as in the issue above, the device total usage count in Device Total Usage report greatly exceeded the device usage count in the Device Detailed Usage report. Now the report data is displayed correctly. However, you might not see the historical device usage data per certain date. The missing data will be displayed upon the scheduled device data collection. The issue is reproduced, if you migrate from 1.0.38. 3. Device Detailed Usage History report issue, caused by incorrect data filtering, was fixed. The System failed to filter a device data by the device group, but summarized the device data from all groups (including dynamic ones) the device belongs to. As a result, the device usage count displayed in the report greatly exceeded the real count. Now the report data is displayed correctly. The correct historical data is not lost. It is displayed correctly the next time you create the report for the needed period. Release Notes_5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
Release Notes_5
1.00.050
1.
The Device Detailed Usage report issue, caused by incorrect device data processing, was fixed. If the System
received incorrect data from a device, this data was displayed in the report and could not be updated after receiving
the correct data next time. As a result, the device total usage count in Device Total Usage report greatly exceeded
the device usage count in the Device Detailed Usage report. Now the report data is displayed correctly. However,
you might not see the historical device usage data per certain date. The missing data will be displayed upon the
scheduled device data collection.
The issue affected Samsung CLX-9201 model. Other models could have been affected as well.
2.
The Device Detailed Usage report issue, caused by deadlocks in
1.0.38
, was fixed. The System failed to update the
Device Detailed Usage report data after a device had been added. As a result, the same way as in the issue above,
the device total usage count in Device Total Usage report greatly exceeded the device usage count in the Device
Detailed Usage report. Now the report data is displayed correctly. However, you might not see the historical device
usage data per certain date. The missing data will be displayed upon the scheduled device data collection.
The issue is reproduced, if you migrate from 1.0.38
.
3.
Device Detailed Usage History report issue, caused by incorrect data filtering, was fixed. The System failed to filter
a device data by the device group, but summarized the device data from all groups (including dynamic ones) the
device belongs to. As a result, the device usage count displayed in the report greatly exceeded the real count. Now
the report data is displayed correctly. The correct historical data is not lost. It is displayed correctly the next time you
create the report for the needed period.