From 248de5df8cf5c934db1b783429774d77da4489ac Mon Sep 17 00:00:00 2001 From: Edith Lansens <113898085+EdithLansens@users.noreply.github.com> Date: Fri, 7 Mar 2025 12:11:50 +0100 Subject: [PATCH 1/4] RN 42202 --- .../ClientSettings_json.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/user-guide/Reference/Skyline_DataMiner_Folder/More_information_on_certain_files_and_folders/ClientSettings_json.md b/user-guide/Reference/Skyline_DataMiner_Folder/More_information_on_certain_files_and_folders/ClientSettings_json.md index 1649ea2b22..84a38d2229 100644 --- a/user-guide/Reference/Skyline_DataMiner_Folder/More_information_on_certain_files_and_folders/ClientSettings_json.md +++ b/user-guide/Reference/Skyline_DataMiner_Folder/More_information_on_certain_files_and_folders/ClientSettings_json.md @@ -247,6 +247,11 @@ To configure this setting: 1. Save and close the file. +1. Perform an IIS restart to apply the time zone changes. + + > [!NOTE] + > Prior to DataMiner 10.4.0 [CU13]/10.5.0 [CU1]/10.5.4, changes made to the time zone in *ClientSettings.json* take effect immediately after refreshing the web app. + ## Configuring settings for Cube UI freezing The Cube logging can display logs of type "Freeze" to indicate when the Cube UI has been frozen. In *C:\\Skyline DataMiner\\Users\\ClientSettings.json*, you can configure how long the Cube UI has to be frozen before an entry is logged in the Cube logging. In addition, you can also configure how long the UI has been frozen before a pop-up is displayed. From a6c270ac74c998185c2fed7f7987846f3e0a30fe Mon Sep 17 00:00:00 2001 From: Edith Lansens <113898085+EdithLansens@users.noreply.github.com> Date: Fri, 7 Mar 2025 13:11:08 +0100 Subject: [PATCH 2/4] Moving page --- .../Visios/DashboardAndAppsNavigation.md | 4 ++-- .../Web_apps_Feature_Release_10.3.5.md | 4 ++-- .../Web_apps_Feature_Release_10.5.4.md | 2 +- .../Dashboards_app/Tutorials/Embed_Dashboard_in_Visio.md | 2 +- .../Specifying_data_input_in_a_dashboard_URL.md | 4 ++-- .../Basic_controls/DashboardNumericInput.md | 2 +- .../Basic_controls/DashboardSearchInput.md | 2 +- .../Basic_controls/DashboardTextInput.md | 2 +- .../Visualizations/Available_visualizations/Feeds.md | 2 +- .../Available_visualizations/Tables/Table_component.md | 2 +- user-guide/Advanced_Modules/toc.yml | 4 ++-- .../Visio/linking_shapes/Linking_a_shape_to_a_webpage.md | 4 ++-- .../Using_visio_to_control_dashboard_feed_components.md | 2 +- user-guide/Reference/Feature_overview.md | 2 +- 14 files changed, 19 insertions(+), 19 deletions(-) rename user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/{Dashboards_app/Creating_and_configuring_dashboards => }/Specifying_data_input_in_a_dashboard_URL.md (99%) diff --git a/develop/DMI/EPM_Integration_Training/Visios/DashboardAndAppsNavigation.md b/develop/DMI/EPM_Integration_Training/Visios/DashboardAndAppsNavigation.md index b2f6a946e2..182a0579b7 100644 --- a/develop/DMI/EPM_Integration_Training/Visios/DashboardAndAppsNavigation.md +++ b/develop/DMI/EPM_Integration_Training/Visios/DashboardAndAppsNavigation.md @@ -12,7 +12,7 @@ To do so, use a **Link** shape data field. The value has to be the dashboard or http:///dashboard/#/db/Training/Station/01.%20Device%20Overview.dmadb?data={"version":1,"feed":null,"components":[{"cid":1,"select":{"epm-selections":["[param:[cardVar: _elementInfo],901]/5502/[fieldId]"]}}],"feedAndSelect":{}} ``` -For detailed information about the JSON syntax, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_a_dashboard_URL). +For detailed information about the JSON syntax, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). To link to EPM objects in this JSON syntax, you will need to use the **epm-selections** field, with the DMA ID, element ID, field PID and primary key value, separated by forward slashes. This field has to be used within a component field, which means you will need to find the ID of the component. You can do so by editing the dashboard or low-code app and looking up the number in the lower right corner of the component: @@ -30,4 +30,4 @@ Here is an example of what this will look like in a live system: > See also: > > - [Linking a shape to a dashboard component](xref:Linking_a_shape_to_a_dashboard_component) -> - [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_a_dashboard_URL) +> - [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL) diff --git a/release-notes/Web_apps/Web_apps_Feature_Release_10.3/Web_apps_Feature_Release_10.3.5.md b/release-notes/Web_apps/Web_apps_Feature_Release_10.3/Web_apps_Feature_Release_10.3.5.md index b8ab2d8186..f60268ce5d 100644 --- a/release-notes/Web_apps/Web_apps_Feature_Release_10.3/Web_apps_Feature_Release_10.3.5.md +++ b/release-notes/Web_apps/Web_apps_Feature_Release_10.3/Web_apps_Feature_Release_10.3.5.md @@ -123,7 +123,7 @@ A default value can be set by means of a URL option: - `?data=` -For more information on how to pass data using a JSON object, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_a_dashboard_URL). +For more information on how to pass data using a JSON object, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). #### Dashboards app & Low-Code Apps: New 'Numeric input' feed [ID 35911] @@ -148,7 +148,7 @@ A default value can be set by means of a URL option: - `?data=` -For more information on how to pass data using a JSON object, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_a_dashboard_URL). +For more information on how to pass data using a JSON object, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). #### Low-Code Apps: 'Open monitoring card' action can now also be linked to a feed [ID 35986] diff --git a/release-notes/Web_apps/Web_apps_Feature_Release_10.5/Web_apps_Feature_Release_10.5.4.md b/release-notes/Web_apps/Web_apps_Feature_Release_10.5/Web_apps_Feature_Release_10.5.4.md index 8455c5a8d6..1eb0cf594e 100644 --- a/release-notes/Web_apps/Web_apps_Feature_Release_10.5/Web_apps_Feature_Release_10.5.4.md +++ b/release-notes/Web_apps/Web_apps_Feature_Release_10.5/Web_apps_Feature_Release_10.5.4.md @@ -91,7 +91,7 @@ When you add the following argument to the URL of a low-code app, all UI compone Up to now, low-code apps would only support using URL data to pass default values to components. For example, to select a particular default value in a dropdown box. From now on, low-code apps will also be able to consume data passed via their URL using either the JSON syntax or the legacy syntax. For example, you will now be able to use an element specified in the URL to filter a GQI query. -For more information regarding the above-mentioned JSON syntax and legacy syntax, see [Specifying data input in a dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL). +For more information regarding the above-mentioned JSON syntax and legacy syntax, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). > [!NOTE] > Contrary to dashboards, low-code apps will not push data to the URL. In other words, the URL will not change when data is selected in a component. diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Tutorials/Embed_Dashboard_in_Visio.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Tutorials/Embed_Dashboard_in_Visio.md index 42242f51c1..b7d4936f24 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Tutorials/Embed_Dashboard_in_Visio.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Tutorials/Embed_Dashboard_in_Visio.md @@ -115,7 +115,7 @@ Before you can actually use the URL you have copied, some manual adjustments are https://\/dashboard/#/db/Generic Dummy.dmadb?data=%7B%22version%22%3A1,%22feed%22%3Anull,%22components%22%3A%5B%7B%22cid%22%3A1,%22select%22%3A%7B%22elements%22%3A%5B%22[EscapeDataString:[this elementID]]%22%5D%7D%7D%5D,%22feedAndSelect%22%3A%7B%7D%7D&embed=true > [!TIP] -> See also: [Specifying data input in a dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL) +> See also: [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL) ## Step 3: Create a Visio file and embed the dashboard diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Creating_and_configuring_dashboards/Specifying_data_input_in_a_dashboard_URL.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Specifying_data_input_in_a_dashboard_URL.md similarity index 99% rename from user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Creating_and_configuring_dashboards/Specifying_data_input_in_a_dashboard_URL.md rename to user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Specifying_data_input_in_a_dashboard_URL.md index 343bc46451..44081cbfd2 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Creating_and_configuring_dashboards/Specifying_data_input_in_a_dashboard_URL.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Specifying_data_input_in_a_dashboard_URL.md @@ -1,8 +1,8 @@ --- -uid: Specifying_data_input_in_a_dashboard_URL +uid: Specifying_data_input_in_URL --- -# Specifying data input in a dashboard URL +# Specifying data input in a dashboard or app URL In the URL of a dashboard, you can specify data input for the dashboard. This way, you can immediately make the dashboard display specific data when it is opened. From DataMiner 10.2.0/10.2.2 onwards, you can pass the data using a [JSON object](#json-syntax) in the URL. Prior to DataMiner 10.2.0/10.2.2, you can use the [legacy syntax](#legacy-syntax), which continues to be supported in recent DataMiner versions for now. diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardNumericInput.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardNumericInput.md index 2cac65a1ac..a9d6a94b66 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardNumericInput.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardNumericInput.md @@ -33,7 +33,7 @@ In the *Settings* pane, you can also configure the following optional settings: - *Maximum*: The maximum value for the numeric input. > [!NOTE] -> From DataMiner 10.3.0 [CU10]/10.4.1 onwards, you can drag data to the component to link it to that data, or [specify data input in the URL](xref:Specifying_data_input_in_a_dashboard_URL). This way, the component will be filled in based on the linked data, but users will still be able to modify the value. +> From DataMiner 10.3.0 [CU10]/10.4.1 onwards, you can drag data to the component to link it to that data, or [specify data input in the URL](xref:Specifying_data_input_in_URL). This way, the component will be filled in based on the linked data, but users will still be able to modify the value. ## Component actions diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardSearchInput.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardSearchInput.md index d29f1fa37c..9c5d86ef7a 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardSearchInput.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardSearchInput.md @@ -6,7 +6,7 @@ uid: DashboardSearchInput Available from DataMiner 10.3.0 [CU16]/10.4.0 [CU4]/10.4.7 onwards. This basic control allows users to enter text that will then be available as text data in the dashboard or low-code app. The text data can be used by queries and by script parameters in low-code app actions. This text data can also be cleared with an "x" button available in the input. -You can drag data to the component to link it to that data, or [specify data input in the dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL). This way, the component will be filled in based on the data, but users will still be able to modify the value. +You can drag data to the component to link it to that data, or [specify data input in the dashboard URL](xref:Specifying_data_input_in_URL). This way, the component will be filled in based on the data, but users will still be able to modify the value. The following options are available to fine-tune the component layout: diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardTextInput.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardTextInput.md index ad2dda0306..b9086d7568 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardTextInput.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardTextInput.md @@ -27,7 +27,7 @@ In the *Settings* pane, you can also configure the following optional settings: - *Multiline*: Determines whether the input can consist of multiple lines or not. > [!NOTE] -> From DataMiner 10.3.0 [CU10]/10.4.1 onwards, you can drag data to the component to link it to that data, or [specify data input in the dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL). This way, the component will be filled in based on the data, but users will still be able to modify the value. +> From DataMiner 10.3.0 [CU10]/10.4.1 onwards, you can drag data to the component to link it to that data, or [specify data input in the dashboard URL](xref:Specifying_data_input_in_URL). This way, the component will be filled in based on the data, but users will still be able to modify the value. ## Component actions diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Feeds.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Feeds.md index 3db08354db..ababcc92e3 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Feeds.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Feeds.md @@ -16,7 +16,7 @@ From DataMiner 10.3.0 [CU21]/10.4.0 [CU9]/10.4.12 onwards, these components are - Other: [List](xref:DashboardList), [tree](xref:DashboardTree), [parameter picker](xref:DashboardParameterPicker), and [EPM picker](xref:DashboardEPMPicker) components. > [!NOTE] -> Feeds can be pre-configured in dashboard URLs. See [Specifying data input in a dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL). +> Feeds can be pre-configured in dashboard URLs. See [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). > [!TIP] > Prior to DataMiner 10.3.0 [CU21]/10.4.0 [CU9]/10.4.12, the term "feeds" is also used for [component data](xref:Component_Data) and [URL data](xref:URL_data). diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Tables/Table_component.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Tables/Table_component.md index 83a95a8ee3..9013786417 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Tables/Table_component.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Tables/Table_component.md @@ -211,7 +211,7 @@ You can do this in several different ways, for example: 1. Hover over the component, click the filter icon, and then add a filter from the *URL > Text* section of the *Data* pane. Prior to DataMiner 10.3.0 [CU21]/10.4.0 [CU9]/10.4.12, add a filter from the *Feeds > URL > Strings* section of the *Data* pane. - 1. Pass a string data object within the URL, as explained in [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_a_dashboard_URL). + 1. Pass a string data object within the URL, as explained in [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). This URL will automatically display a filtered version of the table when the dashboard or app is opened. diff --git a/user-guide/Advanced_Modules/toc.yml b/user-guide/Advanced_Modules/toc.yml index 628d87c11c..295d177db8 100644 --- a/user-guide/Advanced_Modules/toc.yml +++ b/user-guide/Advanced_Modules/toc.yml @@ -283,8 +283,6 @@ items: topicUid: Configuring_the_dashboard_layout - name: Embedding a dashboard component in a webpage or Visio drawing topicUid: Embedding_a_dashboard_component_in_a_webpage_or_Visio_drawing - - name: Specifying data input in a dashboard or app URL - topicUid: Specifying_data_input_in_a_dashboard_URL - name: Sharing a dashboard topicUid: Sharing_a_dashboard - name: Generating a report based on a dashboard @@ -715,6 +713,8 @@ items: topicUid: Query_updates - name: Importing a query topicUid: Importing_a_query + - name: Specifying data input in a dashboard or app URL + topicUid: Specifying_data_input_in_URL - name: Logging topicUid: Dashboards_and_Low_Code_Apps_Logging - name: Style Guide diff --git a/user-guide/Basic_Functionality/Visio/linking_shapes/Linking_a_shape_to_a_webpage.md b/user-guide/Basic_Functionality/Visio/linking_shapes/Linking_a_shape_to_a_webpage.md index 628e765cff..3b80f5c1da 100644 --- a/user-guide/Basic_Functionality/Visio/linking_shapes/Linking_a_shape_to_a_webpage.md +++ b/user-guide/Basic_Functionality/Visio/linking_shapes/Linking_a_shape_to_a_webpage.md @@ -125,7 +125,7 @@ http://localhost/foo/test.php?id=123&action=save#SL_ALLOW_POPUPS# > - Prior to DataMiner 10.3.6/10.4.0, adding a URL fragment to a linked webpage causes the connection info to be automatically added after the fragment, rendering the URL invalid and requiring a reload of the page, which means the user may need to log in again. From DataMiner 10.3.6/10.4.0 onwards, Visual Overview can recognize if a URL fragment is added or changed and update only the necessary parts of the page, avoiding the need to recreate the browser instance. > [!TIP] -> If you want to pass data to a dashboard using placeholders, take a look at [how to specify data input in a dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL). +> If you want to pass data to a dashboard using placeholders, take a look at [how to specify data input in a dashboard URL](xref:Specifying_data_input_in_URL). > > It can also be useful to copy the URL directly from the Dashboards app. However, some of the URL parameters may be compressed. If you need the uncompressed URL parameters to insert placeholders, [retrieve the URL via the sharing option](xref:Sharing_a_dashboard#sharing-a-dashboard-url) and select *Use uncompressed URL parameters*. @@ -172,7 +172,7 @@ You can link to a dashboard or low-code app in the same way as you would link to In the URL of the dashboard or low-code app, you can add placeholders in order to dynamically specify data for the dashboard or low-code app. > [!TIP] -> For more information about the URL syntax, refer to [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_a_dashboard_URL). +> For more information about the URL syntax, refer to [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). > [!NOTE] > It is also possible to [link a shape to a component of a dashboard](xref:Linking_a_shape_to_a_dashboard_component) instead of the entire dashboard. diff --git a/user-guide/Basic_Functionality/Visio/tutorials/Using_visio_to_control_dashboard_feed_components.md b/user-guide/Basic_Functionality/Visio/tutorials/Using_visio_to_control_dashboard_feed_components.md index e14cc9c438..d194723063 100644 --- a/user-guide/Basic_Functionality/Visio/tutorials/Using_visio_to_control_dashboard_feed_components.md +++ b/user-guide/Basic_Functionality/Visio/tutorials/Using_visio_to_control_dashboard_feed_components.md @@ -243,5 +243,5 @@ For each table row that was added in [step 1](#step-1-create-a-new-virtual-conne - [Visio drawings](xref:visio) - [Getting started with basic shapes](xref:Getting_started_with_basic_shapes) - [Component data](xref:Component_Data) -- [Specifying data input in a dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL) +- [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL) - [Generating shapes based on table rows](xref:Generating_shapes_based_on_table_rows) diff --git a/user-guide/Reference/Feature_overview.md b/user-guide/Reference/Feature_overview.md index 3800a33751..28152a10dc 100644 --- a/user-guide/Reference/Feature_overview.md +++ b/user-guide/Reference/Feature_overview.md @@ -34,7 +34,7 @@ Below you can find an overview of the main features that have been added to Data | Cube: [Hiding the close button](xref:Working_with_cards_in_DataMiner_Cube#marking-cards-as-non-closable) and [Selecting a Master card](xref:Working_with_cards_in_DataMiner_Cube#selecting-a-master-card) | DataMiner Cube 10.3.9/10.4.0 | | Cube: [*UseInitialArgumentsAfterDisconnect* argument](xref:Options_for_opening_DataMiner_Cube#useinitialargumentsafterdisconnecttrue) | DataMiner Cube 10.2.0 [CU22]/10.3.0 [CU10]/10.4.1 | | Dashboards: [*Alarm table* component](xref:DashboardAlarmTable) | DataMiner 10.1.5/10.2.0
DataMiner 9.6.8 with [soft-launch option](xref:Overview_of_Soft_Launch_Options#reportsanddashboardsalarmlist) | -| Dashboards: [JSON input in URL parameters](xref:Specifying_data_input_in_a_dashboard_URL) | DataMiner 10.2.0/10.2.2 | +| Dashboards: [JSON input in URL parameters](xref:Specifying_data_input_in_URL) | DataMiner 10.2.0/10.2.2 | | Dashboards: [*Node edge graph* component](xref:DashboardNodeEdgeGraph) | DataMiner 10.1.5/10.2.0 | | Dashboards: [PDF export](xref:Sharing_PDF_report_from_Dashboards_app) | DataMiner 10.2.12/10.3.0
DataMiner 10.2.2 with [soft-launch option](xref:Overview_of_Soft_Launch_Options#reportsanddashboardsexport) | | Dashboards: [*Progress bar* component](xref:DashboardProgressBar) | DataMiner 10.1.7/10.2.0 | From e3ff8c21b61871224143805db6146f7e9d92a3a0 Mon Sep 17 00:00:00 2001 From: Edith Lansens <113898085+EdithLansens@users.noreply.github.com> Date: Fri, 7 Mar 2025 13:17:51 +0100 Subject: [PATCH 3/4] Revert "Moving page" This reverts commit a6c270ac74c998185c2fed7f7987846f3e0a30fe. --- .../Visios/DashboardAndAppsNavigation.md | 4 ++-- .../Web_apps_Feature_Release_10.3.5.md | 4 ++-- .../Web_apps_Feature_Release_10.5.4.md | 2 +- .../Specifying_data_input_in_a_dashboard_URL.md | 4 ++-- .../Dashboards_app/Tutorials/Embed_Dashboard_in_Visio.md | 2 +- .../Basic_controls/DashboardNumericInput.md | 2 +- .../Basic_controls/DashboardSearchInput.md | 2 +- .../Basic_controls/DashboardTextInput.md | 2 +- .../Visualizations/Available_visualizations/Feeds.md | 2 +- .../Available_visualizations/Tables/Table_component.md | 2 +- user-guide/Advanced_Modules/toc.yml | 4 ++-- .../Visio/linking_shapes/Linking_a_shape_to_a_webpage.md | 4 ++-- .../Using_visio_to_control_dashboard_feed_components.md | 2 +- user-guide/Reference/Feature_overview.md | 2 +- 14 files changed, 19 insertions(+), 19 deletions(-) rename user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/{ => Dashboards_app/Creating_and_configuring_dashboards}/Specifying_data_input_in_a_dashboard_URL.md (99%) diff --git a/develop/DMI/EPM_Integration_Training/Visios/DashboardAndAppsNavigation.md b/develop/DMI/EPM_Integration_Training/Visios/DashboardAndAppsNavigation.md index 182a0579b7..b2f6a946e2 100644 --- a/develop/DMI/EPM_Integration_Training/Visios/DashboardAndAppsNavigation.md +++ b/develop/DMI/EPM_Integration_Training/Visios/DashboardAndAppsNavigation.md @@ -12,7 +12,7 @@ To do so, use a **Link** shape data field. The value has to be the dashboard or http:///dashboard/#/db/Training/Station/01.%20Device%20Overview.dmadb?data={"version":1,"feed":null,"components":[{"cid":1,"select":{"epm-selections":["[param:[cardVar: _elementInfo],901]/5502/[fieldId]"]}}],"feedAndSelect":{}} ``` -For detailed information about the JSON syntax, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). +For detailed information about the JSON syntax, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_a_dashboard_URL). To link to EPM objects in this JSON syntax, you will need to use the **epm-selections** field, with the DMA ID, element ID, field PID and primary key value, separated by forward slashes. This field has to be used within a component field, which means you will need to find the ID of the component. You can do so by editing the dashboard or low-code app and looking up the number in the lower right corner of the component: @@ -30,4 +30,4 @@ Here is an example of what this will look like in a live system: > See also: > > - [Linking a shape to a dashboard component](xref:Linking_a_shape_to_a_dashboard_component) -> - [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL) +> - [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_a_dashboard_URL) diff --git a/release-notes/Web_apps/Web_apps_Feature_Release_10.3/Web_apps_Feature_Release_10.3.5.md b/release-notes/Web_apps/Web_apps_Feature_Release_10.3/Web_apps_Feature_Release_10.3.5.md index f60268ce5d..b8ab2d8186 100644 --- a/release-notes/Web_apps/Web_apps_Feature_Release_10.3/Web_apps_Feature_Release_10.3.5.md +++ b/release-notes/Web_apps/Web_apps_Feature_Release_10.3/Web_apps_Feature_Release_10.3.5.md @@ -123,7 +123,7 @@ A default value can be set by means of a URL option: - `?data=` -For more information on how to pass data using a JSON object, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). +For more information on how to pass data using a JSON object, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_a_dashboard_URL). #### Dashboards app & Low-Code Apps: New 'Numeric input' feed [ID 35911] @@ -148,7 +148,7 @@ A default value can be set by means of a URL option: - `?data=` -For more information on how to pass data using a JSON object, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). +For more information on how to pass data using a JSON object, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_a_dashboard_URL). #### Low-Code Apps: 'Open monitoring card' action can now also be linked to a feed [ID 35986] diff --git a/release-notes/Web_apps/Web_apps_Feature_Release_10.5/Web_apps_Feature_Release_10.5.4.md b/release-notes/Web_apps/Web_apps_Feature_Release_10.5/Web_apps_Feature_Release_10.5.4.md index 1eb0cf594e..8455c5a8d6 100644 --- a/release-notes/Web_apps/Web_apps_Feature_Release_10.5/Web_apps_Feature_Release_10.5.4.md +++ b/release-notes/Web_apps/Web_apps_Feature_Release_10.5/Web_apps_Feature_Release_10.5.4.md @@ -91,7 +91,7 @@ When you add the following argument to the URL of a low-code app, all UI compone Up to now, low-code apps would only support using URL data to pass default values to components. For example, to select a particular default value in a dropdown box. From now on, low-code apps will also be able to consume data passed via their URL using either the JSON syntax or the legacy syntax. For example, you will now be able to use an element specified in the URL to filter a GQI query. -For more information regarding the above-mentioned JSON syntax and legacy syntax, see [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). +For more information regarding the above-mentioned JSON syntax and legacy syntax, see [Specifying data input in a dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL). > [!NOTE] > Contrary to dashboards, low-code apps will not push data to the URL. In other words, the URL will not change when data is selected in a component. diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Specifying_data_input_in_a_dashboard_URL.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Creating_and_configuring_dashboards/Specifying_data_input_in_a_dashboard_URL.md similarity index 99% rename from user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Specifying_data_input_in_a_dashboard_URL.md rename to user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Creating_and_configuring_dashboards/Specifying_data_input_in_a_dashboard_URL.md index 44081cbfd2..343bc46451 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Specifying_data_input_in_a_dashboard_URL.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Creating_and_configuring_dashboards/Specifying_data_input_in_a_dashboard_URL.md @@ -1,8 +1,8 @@ --- -uid: Specifying_data_input_in_URL +uid: Specifying_data_input_in_a_dashboard_URL --- -# Specifying data input in a dashboard or app URL +# Specifying data input in a dashboard URL In the URL of a dashboard, you can specify data input for the dashboard. This way, you can immediately make the dashboard display specific data when it is opened. From DataMiner 10.2.0/10.2.2 onwards, you can pass the data using a [JSON object](#json-syntax) in the URL. Prior to DataMiner 10.2.0/10.2.2, you can use the [legacy syntax](#legacy-syntax), which continues to be supported in recent DataMiner versions for now. diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Tutorials/Embed_Dashboard_in_Visio.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Tutorials/Embed_Dashboard_in_Visio.md index b7d4936f24..42242f51c1 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Tutorials/Embed_Dashboard_in_Visio.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Dashboards_app/Tutorials/Embed_Dashboard_in_Visio.md @@ -115,7 +115,7 @@ Before you can actually use the URL you have copied, some manual adjustments are https://\/dashboard/#/db/Generic Dummy.dmadb?data=%7B%22version%22%3A1,%22feed%22%3Anull,%22components%22%3A%5B%7B%22cid%22%3A1,%22select%22%3A%7B%22elements%22%3A%5B%22[EscapeDataString:[this elementID]]%22%5D%7D%7D%5D,%22feedAndSelect%22%3A%7B%7D%7D&embed=true > [!TIP] -> See also: [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL) +> See also: [Specifying data input in a dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL) ## Step 3: Create a Visio file and embed the dashboard diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardNumericInput.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardNumericInput.md index a9d6a94b66..2cac65a1ac 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardNumericInput.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardNumericInput.md @@ -33,7 +33,7 @@ In the *Settings* pane, you can also configure the following optional settings: - *Maximum*: The maximum value for the numeric input. > [!NOTE] -> From DataMiner 10.3.0 [CU10]/10.4.1 onwards, you can drag data to the component to link it to that data, or [specify data input in the URL](xref:Specifying_data_input_in_URL). This way, the component will be filled in based on the linked data, but users will still be able to modify the value. +> From DataMiner 10.3.0 [CU10]/10.4.1 onwards, you can drag data to the component to link it to that data, or [specify data input in the URL](xref:Specifying_data_input_in_a_dashboard_URL). This way, the component will be filled in based on the linked data, but users will still be able to modify the value. ## Component actions diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardSearchInput.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardSearchInput.md index 9c5d86ef7a..d29f1fa37c 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardSearchInput.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardSearchInput.md @@ -6,7 +6,7 @@ uid: DashboardSearchInput Available from DataMiner 10.3.0 [CU16]/10.4.0 [CU4]/10.4.7 onwards. This basic control allows users to enter text that will then be available as text data in the dashboard or low-code app. The text data can be used by queries and by script parameters in low-code app actions. This text data can also be cleared with an "x" button available in the input. -You can drag data to the component to link it to that data, or [specify data input in the dashboard URL](xref:Specifying_data_input_in_URL). This way, the component will be filled in based on the data, but users will still be able to modify the value. +You can drag data to the component to link it to that data, or [specify data input in the dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL). This way, the component will be filled in based on the data, but users will still be able to modify the value. The following options are available to fine-tune the component layout: diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardTextInput.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardTextInput.md index b9086d7568..ad2dda0306 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardTextInput.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Basic_controls/DashboardTextInput.md @@ -27,7 +27,7 @@ In the *Settings* pane, you can also configure the following optional settings: - *Multiline*: Determines whether the input can consist of multiple lines or not. > [!NOTE] -> From DataMiner 10.3.0 [CU10]/10.4.1 onwards, you can drag data to the component to link it to that data, or [specify data input in the dashboard URL](xref:Specifying_data_input_in_URL). This way, the component will be filled in based on the data, but users will still be able to modify the value. +> From DataMiner 10.3.0 [CU10]/10.4.1 onwards, you can drag data to the component to link it to that data, or [specify data input in the dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL). This way, the component will be filled in based on the data, but users will still be able to modify the value. ## Component actions diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Feeds.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Feeds.md index ababcc92e3..3db08354db 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Feeds.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Feeds.md @@ -16,7 +16,7 @@ From DataMiner 10.3.0 [CU21]/10.4.0 [CU9]/10.4.12 onwards, these components are - Other: [List](xref:DashboardList), [tree](xref:DashboardTree), [parameter picker](xref:DashboardParameterPicker), and [EPM picker](xref:DashboardEPMPicker) components. > [!NOTE] -> Feeds can be pre-configured in dashboard URLs. See [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). +> Feeds can be pre-configured in dashboard URLs. See [Specifying data input in a dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL). > [!TIP] > Prior to DataMiner 10.3.0 [CU21]/10.4.0 [CU9]/10.4.12, the term "feeds" is also used for [component data](xref:Component_Data) and [URL data](xref:URL_data). diff --git a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Tables/Table_component.md b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Tables/Table_component.md index 9013786417..83a95a8ee3 100644 --- a/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Tables/Table_component.md +++ b/user-guide/Advanced_Modules/Dashboards_and_Low_Code_Apps/Visualizations/Available_visualizations/Tables/Table_component.md @@ -211,7 +211,7 @@ You can do this in several different ways, for example: 1. Hover over the component, click the filter icon, and then add a filter from the *URL > Text* section of the *Data* pane. Prior to DataMiner 10.3.0 [CU21]/10.4.0 [CU9]/10.4.12, add a filter from the *Feeds > URL > Strings* section of the *Data* pane. - 1. Pass a string data object within the URL, as explained in [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). + 1. Pass a string data object within the URL, as explained in [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_a_dashboard_URL). This URL will automatically display a filtered version of the table when the dashboard or app is opened. diff --git a/user-guide/Advanced_Modules/toc.yml b/user-guide/Advanced_Modules/toc.yml index 295d177db8..628d87c11c 100644 --- a/user-guide/Advanced_Modules/toc.yml +++ b/user-guide/Advanced_Modules/toc.yml @@ -283,6 +283,8 @@ items: topicUid: Configuring_the_dashboard_layout - name: Embedding a dashboard component in a webpage or Visio drawing topicUid: Embedding_a_dashboard_component_in_a_webpage_or_Visio_drawing + - name: Specifying data input in a dashboard or app URL + topicUid: Specifying_data_input_in_a_dashboard_URL - name: Sharing a dashboard topicUid: Sharing_a_dashboard - name: Generating a report based on a dashboard @@ -713,8 +715,6 @@ items: topicUid: Query_updates - name: Importing a query topicUid: Importing_a_query - - name: Specifying data input in a dashboard or app URL - topicUid: Specifying_data_input_in_URL - name: Logging topicUid: Dashboards_and_Low_Code_Apps_Logging - name: Style Guide diff --git a/user-guide/Basic_Functionality/Visio/linking_shapes/Linking_a_shape_to_a_webpage.md b/user-guide/Basic_Functionality/Visio/linking_shapes/Linking_a_shape_to_a_webpage.md index 3b80f5c1da..628e765cff 100644 --- a/user-guide/Basic_Functionality/Visio/linking_shapes/Linking_a_shape_to_a_webpage.md +++ b/user-guide/Basic_Functionality/Visio/linking_shapes/Linking_a_shape_to_a_webpage.md @@ -125,7 +125,7 @@ http://localhost/foo/test.php?id=123&action=save#SL_ALLOW_POPUPS# > - Prior to DataMiner 10.3.6/10.4.0, adding a URL fragment to a linked webpage causes the connection info to be automatically added after the fragment, rendering the URL invalid and requiring a reload of the page, which means the user may need to log in again. From DataMiner 10.3.6/10.4.0 onwards, Visual Overview can recognize if a URL fragment is added or changed and update only the necessary parts of the page, avoiding the need to recreate the browser instance. > [!TIP] -> If you want to pass data to a dashboard using placeholders, take a look at [how to specify data input in a dashboard URL](xref:Specifying_data_input_in_URL). +> If you want to pass data to a dashboard using placeholders, take a look at [how to specify data input in a dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL). > > It can also be useful to copy the URL directly from the Dashboards app. However, some of the URL parameters may be compressed. If you need the uncompressed URL parameters to insert placeholders, [retrieve the URL via the sharing option](xref:Sharing_a_dashboard#sharing-a-dashboard-url) and select *Use uncompressed URL parameters*. @@ -172,7 +172,7 @@ You can link to a dashboard or low-code app in the same way as you would link to In the URL of the dashboard or low-code app, you can add placeholders in order to dynamically specify data for the dashboard or low-code app. > [!TIP] -> For more information about the URL syntax, refer to [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL). +> For more information about the URL syntax, refer to [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_a_dashboard_URL). > [!NOTE] > It is also possible to [link a shape to a component of a dashboard](xref:Linking_a_shape_to_a_dashboard_component) instead of the entire dashboard. diff --git a/user-guide/Basic_Functionality/Visio/tutorials/Using_visio_to_control_dashboard_feed_components.md b/user-guide/Basic_Functionality/Visio/tutorials/Using_visio_to_control_dashboard_feed_components.md index d194723063..e14cc9c438 100644 --- a/user-guide/Basic_Functionality/Visio/tutorials/Using_visio_to_control_dashboard_feed_components.md +++ b/user-guide/Basic_Functionality/Visio/tutorials/Using_visio_to_control_dashboard_feed_components.md @@ -243,5 +243,5 @@ For each table row that was added in [step 1](#step-1-create-a-new-virtual-conne - [Visio drawings](xref:visio) - [Getting started with basic shapes](xref:Getting_started_with_basic_shapes) - [Component data](xref:Component_Data) -- [Specifying data input in a dashboard or app URL](xref:Specifying_data_input_in_URL) +- [Specifying data input in a dashboard URL](xref:Specifying_data_input_in_a_dashboard_URL) - [Generating shapes based on table rows](xref:Generating_shapes_based_on_table_rows) diff --git a/user-guide/Reference/Feature_overview.md b/user-guide/Reference/Feature_overview.md index 28152a10dc..3800a33751 100644 --- a/user-guide/Reference/Feature_overview.md +++ b/user-guide/Reference/Feature_overview.md @@ -34,7 +34,7 @@ Below you can find an overview of the main features that have been added to Data | Cube: [Hiding the close button](xref:Working_with_cards_in_DataMiner_Cube#marking-cards-as-non-closable) and [Selecting a Master card](xref:Working_with_cards_in_DataMiner_Cube#selecting-a-master-card) | DataMiner Cube 10.3.9/10.4.0 | | Cube: [*UseInitialArgumentsAfterDisconnect* argument](xref:Options_for_opening_DataMiner_Cube#useinitialargumentsafterdisconnecttrue) | DataMiner Cube 10.2.0 [CU22]/10.3.0 [CU10]/10.4.1 | | Dashboards: [*Alarm table* component](xref:DashboardAlarmTable) | DataMiner 10.1.5/10.2.0
DataMiner 9.6.8 with [soft-launch option](xref:Overview_of_Soft_Launch_Options#reportsanddashboardsalarmlist) | -| Dashboards: [JSON input in URL parameters](xref:Specifying_data_input_in_URL) | DataMiner 10.2.0/10.2.2 | +| Dashboards: [JSON input in URL parameters](xref:Specifying_data_input_in_a_dashboard_URL) | DataMiner 10.2.0/10.2.2 | | Dashboards: [*Node edge graph* component](xref:DashboardNodeEdgeGraph) | DataMiner 10.1.5/10.2.0 | | Dashboards: [PDF export](xref:Sharing_PDF_report_from_Dashboards_app) | DataMiner 10.2.12/10.3.0
DataMiner 10.2.2 with [soft-launch option](xref:Overview_of_Soft_Launch_Options#reportsanddashboardsexport) | | Dashboards: [*Progress bar* component](xref:DashboardProgressBar) | DataMiner 10.1.7/10.2.0 | From 4810810949ec281b2390b1f5b55a4e15a28a4564 Mon Sep 17 00:00:00 2001 From: Marieke Goethals <94605575+MariekeGO@users.noreply.github.com> Date: Wed, 12 Mar 2025 13:56:12 +0100 Subject: [PATCH 4/4] Update ClientSettings_json.md --- .../ClientSettings_json.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user-guide/Reference/Skyline_DataMiner_Folder/More_information_on_certain_files_and_folders/ClientSettings_json.md b/user-guide/Reference/Skyline_DataMiner_Folder/More_information_on_certain_files_and_folders/ClientSettings_json.md index 84a38d2229..1640e655f4 100644 --- a/user-guide/Reference/Skyline_DataMiner_Folder/More_information_on_certain_files_and_folders/ClientSettings_json.md +++ b/user-guide/Reference/Skyline_DataMiner_Folder/More_information_on_certain_files_and_folders/ClientSettings_json.md @@ -250,7 +250,7 @@ To configure this setting: 1. Perform an IIS restart to apply the time zone changes. > [!NOTE] - > Prior to DataMiner 10.4.0 [CU13]/10.5.0 [CU1]/10.5.4, changes made to the time zone in *ClientSettings.json* take effect immediately after refreshing the web app. + > Prior to DataMiner 10.4.0 [CU13]/10.5.0 [CU1]/10.5.4, an IIS restart is not necessary, and changes made to the time zone in *ClientSettings.json* will take effect immediately as soon as the web app is refreshed. ## Configuring settings for Cube UI freezing