DataMiner web apps Main Release 10.3.0 CU1
Note
For known issues with this version, refer to Known issues.
Tip
For release notes for this release that are not related to the web applications, see General Main Release 10.3.0 CU1.
Enhancements
GQI - Parameter table: Timestamps will now be displayed using the time zone configured in ClientSettings.json [ID 35515]
GQI queries against the following data sources will now return all parameter values of type date/time in the timezone configured in the ClientSettings.json file.
- Get parameters for element where
- Get parameter table by alias
- Get parameter table by ID
Up to now, these values were always displayed in UTC.
Tip
See also: Setting the default time zone for DataMiner web apps
Web Services API v1: Updated descriptions of GetAlarmHistory and GetAlarmDetails methods [ID 35651]
In the following interface files, the descriptions of the GetAlarmHistory and GetAlarmDetails methods have been updated:
http://DmaNameOrIpAddress/API/v1/soap.asmx
http://DmaNameOrIpAddress/API/v1/json.asmx
New description of the GetAlarmHistory method:
Get the alarm history for the specified alarm (optional full tree request). Use root alarm ID with requestFullTree for the details of a cleared non-root alarm.
New description of the GetAlarmDetails method:
Get the alarm details for the specified alarm (use GetAlarmHistory for the details of a cleared non-root alarm).
GQI: Clearer error message when querying a logger table without RTDisplay=true settings [ID 35706]
A clearer error message will now be returned when you are building a query against a logger table without RTDisplay=true settings, neither on table level nor on column level.
Web apps: Enhanced feedback after a failed login attempt [ID 35724]
When a login attempt fails, a clearer error message will now appear.
Dashboards app & Low-Code Apps - Line & area chart component: Enhanced performance when exporting trend data to CSV [ID 35727]
Because of a number of enhancements, overall performance has increased when exporting trend data to a CSV file.
Fixes
Web apps - Interactive Automation scripts: Component of type 'Time' would not be displayed as a time span picker [ID 35435]
In a web app, an interactive Automation script component of type Time with configuration options of type AutomationTimeUpDownOptions would incorrectly not be displayed as a time span picker.
Also, a number of enhancements have been made:
In web app environments, configuration options of type
AutomationTimeUpDownOptionsnow have a newShowTimeUnitsproperty. When this property is set to true, the component will display labels indicating the days, hours, minutes and seconds. Default setting: falseThe hours, minutes and seconds of the time span component will get leading zeros after focus is lost.
In a web app environment, a calendar component will now always show the picker button (as in Cube).
When an interactive Automation script run in a web app environment contains executable components, a message will now be displayed, saying that executable components are not supported in web apps.
Web apps: An invalid value entered into a text box would incorrectly be replaced by the last valid value that was entered [ID 35489]
When you entered an invalid value into a text box, an error message would be displayed for a very short moment, and the invalid value would incorrectly be replaced by the last valid value that was entered.
Dashboards app & Low-Code Apps - GQI: Problem with 'Update data' option when using the 'Get parameter table by ID' data source [ID 35490]
When a query using the Get parameter table by ID data source had the Update data option enabled, the component would incorrectly no longer automatically refresh the data when changes were detected.
Web apps - Interactive Automation scripts: Components in a row following a component with a row span greater than 1 would not be positioned correctly [ID 35504]
In an interactive Automation script executed in a web app, components positioned in a row following a row that contained a component with a row span greater than 1 would not be positioned correctly.
Note
If, in an interactive Automation script executed in a web app, a component is positioned on a cell that is overlapped by a component with a row span greater than 1, it will not be displayed.
Important
BREAKING CHANGE: If, in an interactive Automation script designed to be executed in a web app, the column property was altered to position a component at a specific spot, because of this fix, the component in question will no longer be displayed. It will be hidden by the component of which the row span is greater than 1. The component can be made visible again by changing the column property.
Low-Code Apps: Sidebar would incorrectly be displayed when there was only one visible page [ID 35544]
Up to now, whether the sidebar was displayed or not would incorrectly depend on the number of pages. From now on, it will depend on the number of visible pages. In other words, the sidebar will only be displayed when there are at least two visible pages.
Low-Code Apps: Clock components in a published low-code app would incorrectly only update when you moved the mouse [ID 35554]
Clock components in a published low-code app would incorrectly only update when you moved the mouse.
Dashboards app: Submenu in subheader bar would incorrectly be displayed when it did not contain any visible items [ID 35570]
The submenu in the subheader bar of a dashboard would incorrectly be displayed when it did not contain any visible items.
Web apps: No longer possible to clear a radio button group [ID 35603]
It would incorrectly no longer be possible to clear a radio button group.
GQI: Problem when applying an 'aggregation' or 'group by' operation on a datetime column of an Elasticsearch table [ID 35609]
When an aggregation or group by operation was applied on a datetime column of an Elasticsearch table, the datetime values in that column would be parsed incorrectly.
Web apps: Auto-complete control could clear its content while you were entering a value [ID 35623]
In some cases, an auto-complete control could clear its content while you were entering a value.
Web apps: Problem when retrieving spectrum element parameters [ID 35660]
When the parameters of a spectrum element were retrieved in a web app, in some cases, an exception could be thrown, causing a No parameters available message to appear.
Dashboards app - Line & area chart component: Trend data could not be retrieved for spectrum parameters [ID 35676]
When, in a dashboard, you added a trended spectrum parameter to a line & area chart component, the component would not be able to retrieve the trend data of that parameter.
Dashboards app - Line & area chart component: Duplicate data in exported CSV file [ID 35688]
When you exported the data shown in a line & area chart component to a CSV file, the file could incorrectly contain duplicate data.
Low-Code Apps: Feeds used in queries would incorrectly not get updated [ID 35689]
In some cases, a feed used in a query would incorrectly not get updated when the data inside the feed was updated.
Dashboards app & Low-Code Apps - State component: Changing the query order would incorrectly only be applied when the browser was refreshed [ID 35690]
When you changed the order of the queries added to a State component, this change would incorrectly only be applied when you refreshed the browser. From now on, the change will be applied immediately.
Dashboards app - Line & area chart: Problem when selecting a new time range [ID 35691]
When a line & area chart was filtered by means of a time range feed, in some cases, the dashboard would incorrectly keep on loading when a new time range was selected.
Dashboards app & Low-Code Apps: Not possible to filter a GQI table by a boolean column [ID 35692]
Up to now, it would incorrectly not be possible to filter a GQI table by a boolean column.
Dashboards app & Low-Code Apps: Last nodes of a migrated query would incorrectly be cut off [ID 35693]
When a GQI was migrated, in some cases, the last nodes of the migrated query would incorrectly be cut off.
Dashboards app & Low-Code Apps - Node edge component: An incorrect tooltip would appear when hovering over a segment of an edge [ID 35696]
When you hovered over a segment of an edge, in some cases, an incorrect tooltip would appear.
Dashboards app & Low-Code Apps - Query builder: Problem when linking a data source argument of type string to a query column of type GUID [ID 35700]
When configuring an ad hoc data source in a GQI query, you can link the arguments of that ad hoc data source to a feed. However, in some cases, it would incorrectly not be possible to link an argument of type string to a query column of type GUID.
Also, in the query builder, the Link [argument name] to feed for [argument name] command has been renamed to Use feed for [argument name].
Dashboards app: 'Clear all' button would incorrectly also be displayed when the dashboard did not contain any feeds [ID 35709]
When you selected a dashboard, the Clear all button would incorrectly also be displayed when the dashboard did not contain any feeds.
Dashboards app: 'Data used in dashboard' section would incorrectly not list DOM instances [ID 35717]
When editing a dashboard, DOM instances used by components on that dashboard would incorrectly not be listed in the Data used in dashboard section of the DATA tab.
GQI: Display value of an empty cell of type 'double' would incorrectly be set to a "0" string [ID 35718]
The display value of an empty cell of type double would incorrectly be set to a "0" string. From now on, it will be set to an empty string instead.
Web apps: Node edge actions would incorrectly no longer work [ID 35723]
Node edge actions would incorrectly no longer work.
Web apps - Query builder: Query nodes that by default only had a single value would incorrectly not be displayed [ID 35735]
In the query builder, query nodes that by default only had a single value would incorrectly not be displayed.
Dashboards app & Low-Code Apps - Query builder: Problem when trying to create a GQI query with an ad hoc data source that contained an optional DateTime argument [ID 35738]
When you tried to create a GQI query with an ad hoc data source that contained an optional DateTime argument, in some cases, the following exception could be thrown:
Skyline.DataMiner.Web.Common.v1.Utilities.UTCToDateTimeUTC(long)' has some invalid arguments
GQI: Queries containing float or GUID values would not get migrated correctly [ID 35759]
GQI queries containing float or GUID values would not get migrated correctly.
Dashboards app & Low-Code Apps - Query builder: Problem when linking a feed component to an argument of an ad hoc data source [ID 35808]
When a feed component was linked to an argument of an ad hoc data source, in some cases, the feed would not work correctly.
GQI - Parameter table component: Display values of discrete and exception values for DateTime columns would be rendered incorrectly [ID 35910]
When discrete values and exception values for DateTime parameters were requested via GQI, their display values would be rendered incorrectly.