Table of Contents

DataMiner web apps Feature Release 10.6.1

This Feature Release of the DataMiner web applications contains the same new features, enhancements, and fixes as DataMiner web apps Main Release 10.5.0 [CU10].

Note

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

Tip

Highlights

New features

Dashboard reports can now be generated in PDF, HTML, and/or CSV format [ID 43888]

Up to now, a report of a dashboard could only be generated in PDF format (.pdf). Now, it is possible to generate a report in PDF, archived HTML format (.mhtml) and/or CSV format.

MHTML files include all necessary information to allow the report to be rendered in a web browser: HTML code, images, CSS stylesheets, etc.

Also, the default file name has been changed from Report.pdf to <dashboard name>.pdf, <dashboard name>.mhtml, or <dashboard name>.csv.zip.

Important

This feature will only work in conjunction with DataMiner server version 10.6.0/10.6.1 or newer.

Low-Code Apps - Templates: Preset templates are now available [ID 44040]

From now on, preset templates are included in the overview of available templates, which you can access by clicking the Browse templates button while editing a component that supports templates.

When you apply a preset template to a component, you can then configure it further using the Template Editor.

Note

Currently, only a preset template for the table component is available, and it is supported only in the Low-Code Apps module. You can apply it to other components that support templates, but its appearance on those components may be inconsistent.

Dashboards app: Private dashboards can now also be shared via cloud share [ID 44067]

Up to now, it was only possible to share public dashboards via cloud share. From now on, it will also be possible to share private dashboards via cloud share.

Dashboards/Low-Code Apps - Node edge graph component: Read/Edit mode [ID 44078]

From now on, a node edge graph component can be switched from Read mode to Edit mode and back. Only when in Edit mode will it be possible to reposition nodes.

Also, custom positioning mode has now been replaced by the following two positioning modes.

Mode Description
Layered In this mode, the component will automatically arrange nodes and edges in the most logical way.
When the component is in Edit mode, nodes can be repositioned by hand.
Note: The new node positions will only be stored when the user has edit permission.
Linked to data In this mode, nodes will be positioned automatically based on their data.
When the component is in Edit mode, nodes can be repositioned by hand.
By default, the new node positions will not be stored.
Note

In existing node edge components, the positioning modes will be migrated as follows:

  • When previously set to Custom positioning, the component will now by default be set to Edit mode with Layered positioning.
  • When previously set to Layered or Linked to data, the component will now by default be set to Read mode.

Dashboards/Low-Code Apps - Node edge graph component: New 'Node move' event [ID 44144]

Per node query linked to a Node edge graph component, you can now configure node move events that will be triggered when a node belonging to that query is moved.

When triggered, a node move event will provide the following parameters:

  • The row data of the node that was moved.
  • The old position of the node: {x,y}
  • The new position of the node: {x,y}

Changes

Breaking changes

Annotations are now End of Life [ID 44136]

Annotations are now End of Life, and will no longer work when connected to a DataMiner Agent running main release version 10.6.0 or feature release version 10.6.1 (or above).

Also, when connected to a DataMiner Agent running main release version 10.6.0 or feature release version 10.6.1 (or above), the following Web Services API methods (v1) will return an error:

  • GetAnnotationsLinkForElement
  • GetAnnotationsLinkForService
  • GetAnnotationsLinkForView

Enhancements

Dashboards/Low-Code Apps - Line & area chart component: Exporting trend data of aggregation parameters is now supported [ID 43939]

When a Line & area chart component was displaying trend data of aggregation parameters, up to now, it was not possible to export that trend data to a CSV file. Exporting that data is now supported.

GQI DxM: Enhanced performance when using the 'Get parameters for elements where' data source [ID 43989]

Because of a number of enhancements, overall performance has increased when using the Get parameters for elements where data source, especially on systems using the GQI DxM instead of SLHelper.

Low-Code Apps - Form component: Clearer error will now appear when a DOM instance contains an incorrect value for a DomInstanceFieldDescriptor or DomInstanceValueFieldDescriptor [ID 44017]

When, in a low-code app, a DOM instance contained an invalid value for a DomInstanceFieldDescriptor or DomInstanceValueFieldDescriptor, up to now, a The item no longer exists error message would appear on top of the field in question. This error message has now been changed to Instance was not found.

When relevant, this error message will also mention that one or more DOM definition IDs are invalid.

Dashboards app: Enhanced error handling when generating PDF reports [ID 44019]

Because of a number of enhancements, error handling has improved when generating PDF reports.

Dashboards/Low-Code Apps: DataMiner Copilot renamed to DataMiner Assistant [ID 44028]

In the Dashboards app and all low-code apps, the name DataMiner Copilot has now been replaced by DataMiner Assistant.

Dashboards/Low-Code Apps - Form component: Datetime values displayed in the same way as in the Table Component [ID 44039]

On Form components, datetime values will now be displayed in the same way as in Table components.

The datetime format is based on the regional settings of the web browser. If a browser is set to e.g. "English (US)", datetime values will be displayed as "12/31/2029 8:00 PM".

Dashboards/Low-Code Apps: Enhanced visibility of query buttons in the edit pane [ID 44048]

Up to now, when you selected a query in the edit pane, the color of the query button would not get properly adapted to the color of the background, causing visibility issues.

From now on, these query buttons will clearly be visible, whatever the color of the background.

Jobs app is End of Life [ID 44052]

The Jobs app has been declared End of Life. On systems running DataMiner main server version 10.6.0 or higher as well as on all systems using STaaS, it will no longer appear on the DataMiner landing page.

Up to now, by default, DataMiner web applications used the SLHelper process for GQI-related operations. From now on, they will by default use the GQI DxM instead.

If you want the web applications to continue to use the SLHelper process for GQI-related operations, you will have to set the gqi:useDxM key to false in the C:\Skyline DataMiner\Webpages\API\Web.config file. See the following example.

<appSettings>
    <add key="gqi:useDxM" value="false" />
</appSettings>
Note

Currently, the GQI DxM cannot be used on Dashboard Gateway servers yet. Dashboard Gateway servers will continue to use SLHelper, even if the gqi:useDxM key is set to true.

Interactive Automation scripts: UI version will now be set to WebUIVersion.V2 by default [ID 44059]

When connected to a DataMiner Agent with main release version 10.6.0 or feature release 10.5.12 (or above), from now on, interactive Automation scripts executed in a web app will use the new UI version (V2) by default.

This also means that, when you set engine.WebUIVersion to WebUIVersion.Default in a script, the UI version will now be set to the new UI version (V2).

Note that, if you still want to use UI version V1 instead, you can set engine.WebUIVersion to WebUIVersion.V1. See the example below.

engine.WebUIVersion = WebUIVersion.V1

Web apps: Apps menu item 'dataminer.services' will only appear when the DMA is connected to the cloud [ID 44104]

Up to now, when you opened the Apps menu of a web app (e.g. the Monitoring app), the top-most item would be a link to dataminer.services.

From now on, that link will only appear in the Apps menu of a web app when the DataMiner Agent is connected to the cloud.

Low-Code Apps: Enhanced performance [ID 44114]

Because of a number of enhancements, overall performance of low-code apps has increased.

Dashboards/Low-Code Apps - Templates: Enhanced 'Browse templates' window [ID 44123]

When, in a dashboard or low-code app, you are editing a component that uses templates, you can click the Browse templates button to select a template to be applied.

From now on, the Browse templates window will contain a search box that allows you to search for a specific template by name.

Also, you will be able to specify whether you want the list to show custom templates, preset templates, or both.

Dashboards/Low-Code Apps: 'Pivot table' and 'Group' components will only be visible when using the 'showAdvancedSettings=true' URL option [ID 44128]

The Pivot table and Group components are being retired. From now on, both will no longer appear in lists of available visualizations, unless you use the showAdvancedSettings=true URL option.

GQI DxM: DOM data source now supports reading only a selected subset of fields from DomInstance objects [ID 44141]

When connected to a DataMiner Agent running main release version 10.6.0 or feature release 10.6.1 (or above), the DOM data source will now support reading only a selected subset of fields from DomInstance objects. This will reduce the amount of data transferred and can significantly improve performance in cases where a GQI query only need a few fields from each instance.

For more information, see DataMiner Objects Models: DomInstances CRUD helper now supports reading only a selected subset of fields from DomInstance objects [ID 43852]

When connected to a DataMiner Agent running a version older than main release version 10.6.0 or feature release 10.6.1, the DOM data source will continue to read DomInstance objects as before.

Web apps: Option to log in with a local user account [ID 44152]

When a DataMiner Agent was configured to used external authentication, up to now, it would not be possible to log in to a web app with a local user account.

From now on, when you add the skipAutoLogin=true argument to the URL of the app, the login screen will allow you to log in using either external authentication or a local user account.

Example: https://dma.company.local/?skipAutoLogin=true

Note

After having logged in using external authentication, you will now find a new Sign in with another user option in the user menu. This option will allow you return to the login screen, where you will be able log in using either external authentication or a local user account.

Fixes

Visual Overview in web apps: Children shapes would incorrectly be displayed on top of a clickable group of shapes [ID 43465]

In DataMiner Cube, when a visual overview contains a clickable group of shapes that is linked to e.g. an element, that clickable group will always be displayed on top of other shapes (e.g. Children shapes).

Up to now, a visual overview in a web app would behave differently. Children shapes would incorrectly be displayed on top of the clickable group, causing that group to not be clickable.

From now on, a visual overview in a web app will behave in the same way as a visual overview in DataMiner Cube.

Dashboards/Low-Code Apps - Alarm table component: Fetching alarm table data could time out [ID 43986]

In some cases, fetching the data to be displayed in an Alarm table component could time out.

From now on, the table data will be fetched asynchronously using a WebSocket.

Dashboards/Low-Code Apps - Node edge graph component: Selected edges would not be selected again after the graph had been refreshed [ID 43992]

When you had selected one of several edges that went in the same direction between two nodes, up to now, that edge would incorrectly not be selected again after the graph had been refreshed.

Dashboards/Low-Code Apps - Table component: Current selection would not immediately become visible when the browser was refreshed [ID 44003]

After you had refreshed your browser, a Table component would correctly re-apply the current selection, but that selection would incorrectly only become visible when you hovered the mouse pointer over the dashboard or low-code app. From now on, when you refresh your browser, the current selection will immediately be visible.

Dashboards/Low-Code Apps - Alarm table component: Not possible to filter by the service.propertyname column [ID 44020]

In an Alarm table component, up to now, it would incorrectly not be possible to filter by the Alarm Console column service.propertyname (propertyname being the name of the service property). This has now been made possible.

Note

Note that the following Web Services API methods, which allow filtering by service, have all been modified. Up to now, services were checked by ID. From now on, services will be checked by name:

  • GetAlarmPages
  • GetAlarmPagesV2
  • GetAlarmPageUpdates
  • GetAlarmPageUpdatesV2
  • GetAlarmPageWithAlarms
  • GetAlarmPageWithAlarmsV2
  • GetAlarms
  • GetAlarmsV2

DataMiner landing page: Problem when 'Show draft applications' option was enabled [ID 44027]

When, on the DataMiner landing page (by default accessible via https://<DMA IP or hostname>/root), the Show draft applications option was enabled, up to now, you would always be directed to the draft version of an app (if a draft version existed), even when you did not have permission to edit the app. When you did not have edit permission, an HTTP 403 error would appear.

From now on, when you do not have edit permission, the "Draft" label will be hidden, and you will be directed to the last published version of the app.

Dashboards/Low-Code Apps - Form component: Error messages would unexpectedly disappear [ID 44029]

Up to now, when an error message appeared in a Form component, that message would unexpectedly disappear.

From now on, when an error message appears, it will stay visible until an action is performed in the Form component or until a button is clicked.

Interactive Automation scripts: Numeric values containing leading zeros would not update correctly [ID 44037]

In interactive Automation scripts launched from a web app, up to now, numeric values containing leading zeros would not update correctly.

DataMiner web apps authentication page: Problem logging in when using a Firefox browser [ID 44043]

When you had opened the DataMiner web apps authentication page in a Firefox web browser, in some cases, an error could occur when you tried to log in to a web app.

Dashboards app: Problem when generating a PDF report if a trend graph with valid data was followed by a trend graph without valid data [ID 44143]

Up to now, it would not be possible to generate a PDF report if a trend graph with valid data was followed by a trend graph without valid data.

Dashboards/Low-Code Apps - Node edge graph component: Users without edit permission would incorrectly not be allowed to move nodes [ID 44154]

Up to now, in a low-code app, users without permission to edit low-code apps would incorrectly not be allowed to move nodes in a node edge graph component.

From now on, users with permission to view low-code apps will be allowed to move nodes. However, if the node edge graph component is using Layered positioning, the new node positions will not be stored. New node positions will only be stored when the user has edit permission.

Low-Code Apps: Post actions of an 'Execute a script' action would not be able to link the script's output values [ID 44157]

Up to now, when an Execute a script action had been triggered by means of a header bar button, the post actions would not be able to link the script's output values.

Improve this page