Table of Contents

DataMiner Cube Feature Release 10.5.11

This Feature Release of the DataMiner Cube client application contains the same new features, enhancements, and fixes as DataMiner Cube Main Release 10.4.0 [CU20] and 10.5.0 [CU8].

Note

For known issues with this version, refer to Known issues.

Tip

Changes

Enhancements

Visual Overview: Load time metric will now include the time it took to load embedded visual overviews [ID 43467]

From now on, the load time metric of a visual overview will include the time it took to load any embedded visual overviews.

Visual Overview: Load time metric will now include the time shapes with data fields of type 'Property' wait for data [ID 43469]

From now on, the load time metric of a visual overview will include the time shapes with data fields of type 'Property' wait for data.

Clearer message will now appear when Cube experiences a CRL freeze [ID 43663]

When an internet connection is not available on the client machine, the DataMiner Cube application freezes for about 20 seconds during the session. From now on, when this happens, a more detailed message will appear, explaining what can be done to prevent this in the future.

This type of freezes happen because Windows and .NET try to verify the application's digital signatures by checking an online Certificate Revocation List (CRL). The system times out during this process, causing the delay and impacting user productivity.

Spectrum analysis: Trace color can now be modified when a measurement point is selected [ID 43669]

Up to now, it would not be possible to modify the trace color when a measurement point was selected. From now on, it will be possible to modify the trace color when either no measurement point or one single measurement point is selected.

Also, an issue has been fixed that caused the trace color to be incorrect in View Buffer mode, View script mode, or Watch mode when you had changed the color without closing the card.

Enhanced login screen behavior when an automatic login fails [ID 43682]

From now on, when an automatic login with the Administrator user fails, a login screen will appear with the Administrator user pre-selected, prompting you to enter the password of the Administrator account.

Also, when an automatic login with a Windows user fails because (a) that Windows user is not a DataMiner user or (b) the stored credentials of that Windows user are no longer valid, a login screen will appear, prompting you to enter (a) both the user name and the password or (b) the password of the pre-selected Windows user.

Fixes

When you opened a trend graph containing trending of string values combined with exception values, up to now, the following issues could occur:

  • Only the label of the exception value was displayed. None of the other values would have their label displayed.
  • In some cases, the average value that was displayed would incorrectly be a value that had only occurred for a short period of time.
  • The histogram would incorrectly not include any exceptions.

Problem when updating the log levels of an element that had been migrated or swarmed to another DMA [ID 43581]

In some cases, DataMiner Cube would fail to update the log levels of an element log file, especially when the element in question had been migrated or swarmed from the DMA to which you were connected to another DMA in the DataMiner System.

Also, in some cases, it would incorrectly not be possible to clear multiple element log files in one go.

When you zoomed in on a trend graph, the alarm timeline on the X axis would incorrectly be displayed either on top of or beyond the Y axis.

When, in a trend graph showing discreet values, you hover over the graph, the legend will show a percentage indicating how much of the time a value has occurred in the graph. However, since a server-side change in DataMiner version 10.1.10, this percentage has been incorrect.

Problem when a broadcast message expired [ID 43634]

When a broadcast message expired, up to now, an exception could be thrown.

When an open trend graph containing trending of string values had received new data, up to now, the graph could incorrectly show gaps.

When, in a visual overview, a shape showing a trend component was configured to not show the bottom navigator chart (i.e. by means of the "NavigatorChart:false" option set in the ParametersOptions shape data field), up to now, changes made to the Display the alarm template in the trend graph option in the component's settings would incorrectly not be applied.

Also, when a shape showing a trend component was configured to not show the bottom navigator chart, up to now, changes made to the mouse actions in the component's settings would incorrectly not be applied until the card was re-opened.

Bookings module: Listed bookings would be sorted incorrectly [ID 43641]

When, in Cube's Bookings module (or the Skyline Booking Manager connector), the List View component was configured to show a custom culture-invariant DateTime property, up to now, the listed bookings would be sorted incorrectly.

When, in a trend graph, you zoomed out right after new real-time trend data was received, in some cases, part of the graph would incorrectly flatline or all average trend data would disappear.

In a trend graph showing trending of string values, in some cases, exception values would incorrectly not be marked as such, causing DataMiner to interpret those values as valid trend points without Y axis label.

Problem when sending a ParameterChangeEventMessage for a non-string parameter [ID 43701]

When you retrieved the string value of a non-string parameter that was being updated, an exception would be thrown as the string value was null.

When you exported a multiline trend graph to a CSV file with the Line graph instead of block graph option selected, up to now, the data in the CSV file would be incorrect. Also, certain data would be missing.

Cube UI could get stuck when an error occurred while an embedded web browser was initialized [ID 43732]

Up to now, when an error occurred while an embedded web browser was initialized, in some cases, the entire Cube UI could get stuck.

Overall error handling has now been improved. When an embedded web browser throws an exception, that exception will now be caught, information about the error will be logged, and an appropriate error message will appear in the browser control.

No longer possible to edit a service that included a child service [ID 43823]

When a service included a child service, and that child service was a regular service rather than an enhanced service, in some cases, it would not be possible to edit the parent service.

Improve this page