Bosch IoT Insights

Input widget

Using the Input widget, you can add input masks to your dashboard. With these input fields, you can trigger an action via the Action Button widget. It is also possible to place input masks next to a Table widget to trigger multiple actions within the Table widget.

Example

images/confluence/download/attachments/3694133036/input-widget-fields-version-1-modificationdate-1722342258000-api-v2.png

Proceed as follows

  1. Select the Input widget in the widget list.
    → The widget configuration page is displayed.

    images/confluence/download/attachments/3694133036/input_widget_configuration-version-1-modificationdate-1722342259000-api-v2.png
  2. Configure the settings as described below.

  3. Click the Add button.
    → The widget is added to the dashboard.

    To create this widget, the following settings are mandatory to be configured:

    • Data Source

    All other settings are optional.

Dashboard Settings

Open the Dashboard Settings pane to set how the widget is displayed in the dashboard.

  1. In the Size drop-down list, decide how much space the widget should take in the form of columns.

  2. In the Visibility drop-down, set whether the widget should be visible or hidden. You can also define for which specific roles the widget will be shown or not. This setting allows you to customize dashboards for specific user groups that have a certain role.

    Visible: The widget is visible for all (default)
    Visible for roles: The widget is visible if any of the selected roles matches one of the user's project role
    Hidden: The widget is hidden for all
    Hidden for roles: The widget is hidden if any of the selected roles matches one of the user's project role

  3. In the Layout behavior drop-down list, decide how the size of the widget should be adapted in the dashboard.

  4. In the Title field, enter a title for the widget.

    For a dynamic title, you can add placeholders with the ${...} notation. Possible placeholder sources are filterParams (if a filter widget exists on the dashboard, e.g. ${filterParams.paramName}) or data from the data source (if source is specified, e.g. ${[0].payload.value}), insights (user context), dashboardName or widgetId.

General Settings

Open the General Settings pane to configure some general aspects for the widget.

  1. In the Widget Refresh Interval in Seconds field, enter a value in seconds after which the widget should be refreshed.

  2. In the Lazy Loading drop-down list, select whether you want to enable or disable lazy loading.

    Lazy loading is disabled by default.

  3. In the Store Values in User Settings drop-down list, define whether the input settings shall be stored.

    • Yes (default): The local settings are stored until the next session.

    • Yes, reset storage: The local settings are reset once the web browser is closed.

    • Disable: The local settings are not stored for next.

      The configuration of the Input widget involves a storageKey.

      • If a storageKey is available, the local storage is used.

      • If a storageKey is not available, the local storage is disabled.

      • If the Yes, reset storage option is selected, the storageKey is changed, which is basically resetting the storage for the Input widget for the currently logged user.

      Please, be aware that the Input widgets which have been created before this functionality was introduced (refer to Release notes) do not have a storageKey. This means that the local storage is automatically disabled for them and if you want to enable it, you need to change the configuration manually to Yes.

Data Sources

Open the Data Sources pane to configure the data source for the widget.

You can select a maximum of three data sources.

  1. Click the + Add Source button to add a data source.

  2. Select any of the following options further explained underneath:

Query Template

  1. In the Query Template drop-down list, select a query template that you configured under Explore > Data Explorer, refer to Creating a query template.

    A query template is a template that has been created, parameterized, and provided for others. It is similar to an SQL View and shows data in a table view.

    To connect the widget with the Filter Panel widget you created for this dashboard, click the Available references icon images/confluence/download/thumbnails/1083888325/icon_reference-version-1-modificationdate-1616506558000-api-v2.png and select the Filter Panel.

    If you have a time parameter, you can choose between absolute time, relative time, and a preset by clicking the time icon images/confluence/download/thumbnails/1083888325/icon_absolute_relative_time-version-1-modificationdate-1616506558000-api-v2.png .

    There is a Target collection parameter, if the selected query template allows multiple target collections. Select one of the allowed collections from the drop-down list, or select a dynamic reference using the Available references icon images/confluence/download/thumbnails/1083888325/icon_reference-version-1-modificationdate-1616506558000-api-v2.png .

  2. For Caching, add the Duration in seconds to load existing cache entries that match your parameters during that time frame.

    The default cache time of 30 minutes is set automatically.

  3. Click the Source data preview icon images/confluence/download/thumbnails/1083888325/refresh%281%29-version-1-modificationdate-1725282826000-api-v2.png to open a preview.

  4. Click the Save Data Source button.

Single Device

  1. In the Default Device ID drop-down list, select a Device ID.

    To connect the widget with the Filter Panel widget you created for this dashboard, click the Available references icon images/confluence/download/thumbnails/1083888325/icon_reference-version-1-modificationdate-1616506558000-api-v2.png and select the Filter Panel.

  2. Click the Source data preview icon images/confluence/download/thumbnails/1083888325/refresh%281%29-version-1-modificationdate-1725282826000-api-v2.png to open a preview.

  3. Click the Update Source button.

Multiple Devices

  1. In the Select Device Types drop-down list, select a device type.

  2. Click the Advanced Settings button to narrow down the output.

  3. In the Start field, enter a value to specify the device to start with.

    Example: If you select 3, the first two devices are skipped.

  4. In the Limit field, enter a value to specify the last device.

    The maximum is 200 devices.

  5. In the Fields field, enter the fields whose information shall be retrieved from Bosch IoT Things.

  6. In the Sort field, enter a field configured in Bosch IoT Things according to which the data shall be sorted.

  7. In the Namespaces field, add namespaces separated by a comma.

  8. In the Filter field, add a filter to narrow down the search results. Placeholders are also supported.

  9. Click the Source data preview icon images/confluence/download/thumbnails/1083888325/refresh%281%29-version-1-modificationdate-1725282826000-api-v2.png to open a preview.

  10. Click the Update Source button.

Device Count

The Device Count data source is based on the counting functionality in Bosch IoT Things and is used to count things.

  1. In the Select Device Type drop-down list, select the device types/devices to be used as data source.

    • All Devices: Counts all devices regardless of the fact that they have a device type or not

    • All Device Types: Counts the devices that have the thing attribute type which means that the device belongs to a device type

    • Without Device Type: Counts the devices without the thing attribute type

    • Device Type xy: Counts the devices of the selected device types

  2. Click the Advanced Settings button to narrow down the output.

  3. In the Namespaces field, add namespaces separated by a comma.

  4. In the DefaultFilter field, add a filter to narrow down the search results.

    To connect the widget with the Filter Panel widget you created for this dashboard, click the Available references icon images/confluence/download/thumbnails/1083888325/icon_reference-version-1-modificationdate-1616506558000-api-v2.png and select the Filter Panel.

  5. Click the Source data preview icon images/confluence/download/thumbnails/1083888325/refresh%281%29-version-1-modificationdate-1725282826000-api-v2.png to open a preview.

  6. Click the Update Source button.

Devices from Filter Selection

Devices will be loaded that match the Device filter type configured in the Filter Panel widget.

  1. In the Pagination Limit field, enter a limit of devices that shall be displayed per page.

  2. In the Sort field, enter a property according to which the devices shall be sorted.

  3. Click the Source data preview icon images/confluence/download/thumbnails/1083888325/refresh%281%29-version-1-modificationdate-1725282826000-api-v2.png to open a preview.

  4. Click the Update Source button.

Playback: All Frames

The Playback widget must have been configured for your dashboard.

  1. Select Playback: All Frames to display all data that has been recorded.

Playback: Current Frame

The Playback widget must have been configured for your dashboard.

  1. Select Playback: Current Frame to display the data that is just being recorded.

External Data Source

Using the external data source, an external endpoint can be specified to reference data.

  1. Select an HTTP method.

  2. In the Request URL field, enter the URL of the request.

  3. In the Type drop-down list, select the type of authorization.

  4. Click the Set Configuration button to set up the selected authorization.

    1. For Basic Auth:

      1. In the Username field, enter the username.

      2. In the Password field, enter the password.

    2. For OAuth 2.0

      1. In the Grant Type drop-down list, select the type of credentials.

      2. Enter the Access Token URL.

      3. Enter the Client ID.

      4. Enter the Client Secret.

      5. If you selected Password Credentials as Grant Type, also enter the Username and the Password .

    3. For OAuth 2.0 (On-behalf grant type)

      1. In the Grant Type drop-down list, select Azure AD On-Behalf.

      2. Configure the scopes of your application API as described in External data source: on-behalf-of (OBO) flow.

  5. If you selected the GET HTTP method:

    1. In the Headers pane, enter a key and a value to specify the header information of the external system.

    2. Activate the Secret Header checkbox to flag the header as secret.

      When editing the data source, the header information has to be provided.

    3. In the Test Parameters pane, enter a filter parameter to test it.

      This pane can be used if a filter widget is configured for the dashboard. The filter values can be referenced as described in this pane within the URL and Headers.

      Modifiers can be used to manipulate referenced filter values. The following modifiers are available:

      • noencode: Only used in URLs. The value is not encoded as it is done by default.

      • join: Concatenates multiple values in one string separating them with the provided separator.

      • replace: Replace multiple occurrences of a search pattern with a specified replacement pattern.

      • queryParams: Creates an entry with the provided parameterName for each value.

      • relativeTimestamp: Calculates a relative time according to the current time. It offers a way to dynamically change the time range with the use of the Filter Panel widget, e.g. gt{$filterParams.dateTime.from | relativeTimestamp}

      • addTime:<insert number in milliseconds>: Calculates the relative time according to the given time from insights.timestamp and using the number from addTime, e.g. gt{insights.timestamp | addTime:-300000}. This modifier is designed for static usage so that a Filter Panel widget is not required. A positive number is also allowed if relevant.

      Usage examples:

      Example filter context: 

        "multi": ["v1", "v2"],

        "mixedValues": ["v1", undefined, "v2"]

      }

      join:

      ${filterParams.multi | join: ','} will result in v1,v2

      replace:

      ${filterParams.mixedValues | replace: 'undefined','N/A'} will result in ["v1","N/A","v2"]

      queryParams:

      ${filterParams.multi | queryParams: 'multiParam'} will result in multiParam=v1&multiParam=v2

      Independently from the test parameters, user-specific information and randomly generated sequences (UUID v4, alphanumeric or hex string) can be referenced.

  6. If you selected the PUT HTTP method:

    1. In the Body pane, select the type of data in the Type drop-down list.

    2. Activate the Secret Header checkbox to flag the header as secret.

      When editing the data source, the header information has to be provided.

    3. In the Test Parameters pane, enter a filter parameter to test it.

      This pane can be used if a filter widget is configured for the dashboard. The filter values can be referenced as described in this pane within the URL, Headers and the Body.

      Modifiers can be used to manipulate referenced filter values. The following modifiers are available:

      • noencode: Only used in URLs. The value is not encoded as it is done by default.

      • join: Concatenates multiple values in one string separating them with the provided separator.

      • replace: Replace multiple occurrences of a search pattern with a specified replacement pattern.

      • queryParams: Creates an entry with the provided parameterName for each value.

      • relativeTimestamp: Calculates a relative time according to the current time. It offers a way to dynamically change the time range with the use of the Filter Panel widget, e.g. gt{$filterParams.dateTime.from | relativeTimestamp}

      • addTime:<insert number in milliseconds>: Calculates the relative time according to the given time from insights.timestamp and using the number from addTime, e.g. gt{insights.timestamp | addTime:-300000}. This modifier is designed for static usage so that a Filter Panel widget is not required. A positive number is also allowed if relevant.

      Usage examples:

      Example filter context: 

        "multi": ["v1", "v2"],

        "mixedValues": ["v1", undefined, "v2"]

      }

      join:

      ${filterParams.multi | join: ','} will result in v1,v2

      replace:

      ${filterParams.mixedValues | replace: 'undefined','N/A'} will result in ["v1","N/A","v2"]

      queryParams:

      ${filterParams.multi | queryParams: 'multiParam'} will result in multiParam=v1&multiParam=v2

      Independently from the test parameters, user-specific information and randomly generated sequences (UUID v4, alphanumeric or hex string) can be referenced.

  7. If you selected the POST HTTP method:

    1. In the Body pane, select the type of data in the Type drop-down list.

    2. Activate the Secret Header checkbox to flag the header as secret.

      When editing the data source, the header information has to be provided.

    3. In the Test Parameters pane, enter a filter parameter to test it.

      This pane can be used if a filter widget is configured for the dashboard. The filter values can be referenced as described in this pane within the URL, Headers and the Body.

      Modifiers can be used to manipulate referenced filter values. The following modifiers are available:

      • noencode: Only used in URLs. The value is not encoded as it is done by default.

      • join: Concatenates multiple values in one string separating them with the provided separator.

      • replace: Replace multiple occurrences of a search pattern with a specified replacement pattern.

      • queryParams: Creates an entry with the provided parameterName for each value.

      • relativeTimestamp: Calculates a relative time according to the current time. It offers a way to dynamically change the time range with the use of the Filter Panel widget, e.g. gt{$filterParams.dateTime.from | relativeTimestamp}

      • addTime:<insert number in milliseconds>: Calculates the relative time according to the given time from insights.timestamp and using the number from addTime, e.g. gt{insights.timestamp | addTime:-300000}. This modifier is designed for static usage so that a Filter Panel widget is not required. A positive number is also allowed if relevant.

      Usage examples:

      Example filter context: 

        "multi": ["v1", "v2"],

        "mixedValues": ["v1", undefined, "v2"] 

      }

      join:

      ${filterParams.multi | join: ','} will result in v1,v2

      replace:

      ${filterParams.mixedValues | replace: 'undefined','N/A'} will result in ["v1","N/A","v2"]

      queryParams:

      ${filterParams.multi | queryParams: 'multiParam'} will result in multiParam=v1&multiParam=v2

      Independently from the test parameters, user-specific information and randomly generated sequences (UUID v4, alphanumeric or hex string) can be referenced.

  8. In the Duration in seconds field under Caching, specify the caching duration in seconds.

  9. Click the Source data preview icon images/confluence/download/thumbnails/1083888325/refresh%281%29-version-1-modificationdate-1725282826000-api-v2.png to open a preview.

  10. Click the Save Data Source button.

Data Transformation

With the data transformation activated, you can select entries from arrays in arrays or a specific range of arrays.

Also refer to the JMESPath documentation.

Open the Data Transformation pane to activate the data transformation to JMES.

  1. Activate the toggle switch.

  2. In the Filter field, add a string to filter the data, e.g. [0] to display only the first item or [?contains(thingId,'yourThingName')] to filter by contains in the thingId property.

  3. Click the Transformed data preview icon images/confluence/download/thumbnails/1081316247/refresh%281%29-version-1-modificationdate-1725282802000-api-v2.png to open a preview.
    → The data transformation is activated for the widget.

If you selected more than one data source, the Data Aggregator pane is displayed.

  1. Activate the toggle switch.

  2. In the Data Aggregator drop-down list, select an aggregation method with which each entry of the same index is merged into one result.

  3. Activate the Merge Properties checkbox to merge the properties of the index.

  4. In the Filter field, add a string to filter the data, e.g. [0] to display only the first item or [?contains(thingId,'yourThingName')] to filter by contains in the thingId property.

  5. Click the Transformed data preview icon images/confluence/download/thumbnails/1081316247/refresh%281%29-version-1-modificationdate-1725282802000-api-v2.png to open a preview.
    → The data transformation is activated for the widget.

Input Fields

Open the Input Fields pane to add the fields that should be added to the widget.

  1. Choose between Disabled (default) and Enabled in the Auto Save field.

    1. If Auto Save is Enabled, your changes will be automatically saved after five seconds or upon a click anywhere in the UI.
      In that case there are no Apply and Cancel buttons. If you need to restore the default values of the input fields, open the context menu of the already added widget via the options icon images/confluence/download/thumbnails/3694133036/options%281%29-version-1-modificationdate-1722342258000-api-v2.png and select the option images/confluence/download/thumbnails/3694133036/redo-version-1-modificationdate-1722342258000-api-v2.png Restore to defaults.

    2. If Auto Save is Disabled, you will need to manually click the Apply button to save your changes. The Cancel button allows you to restore the default values.

  2. Click the Add field button and select a field to be added.

  3. In the Technical name field, enter a technical name for the field.

  4. In the Label field, enter a name for the field that is displayed in the widget.

  5. In the Description field, enter a description for the field.

  6. For Text, Multi-line text, Date, Date range, and Number fields, enter the Default value.

    You can also set the default value as a query parameter in the url with the following syntax: ?inputFields.<nameOfTheField>=<initialValue>.
    In that case the value is automatically applied without the need to click Save. When set as a query parameter, this value will have a priority over any value set in the configuration, which in turn will have priority over the local storage.

    Please, be aware that setting to many fields via url parameters can lead to issues, as there is a general limit on the length of an HTTP url, depending on the used client browser and server configuration. Therefore, it is not recommended to use this option on too many input widgets.

  7. For the Boolean field, activate the Default value checkbox to have the value True set to default.

    You can also set the default value as a query parameter in the url with the following syntax: ?inputFields.<nameOfTheField>=<initialValue>.
    In that case the value is automatically applied without the need to click Save. When set as a query parameter, this value will have a priority over any value set in the configuration, which in turn will have priority over the local storage.

    Please, be aware that setting to many fields via url parameters can lead to issues, as there is a general limit on the length of an HTTP url, depending on the used client browser and server configuration. Therefore, it is not recommended to use this option on too many input widgets.

  8. For Selection and Multi-selection, activate the Dynamic values checkbox to enter a data path of a specific data source that provides the selection options.

  9. For Text and Multi-line text, enter a regular expression to the Validation regex field which validates the input.

  10. For Date and Date range, select the start date and end date in the Validation range field.

  11. For Number, add values to the Min value and Max value fields to define a validation range.

  12. For Selection and Multi-selection, add the selection values using the Label and Value fields.

    To add another value for the selection, click the Add row button.

  13. For Selection and Multi-selection, select a default value from selection values you added in the Default value drop-down list.

    You can also set the default value as a query parameter in the url with the following syntax: ?inputFields.<nameOfTheField>=<initialValue>.
    In that case the value is automatically applied without the need to click Save. When set as a query parameter, this value will have a priority over any value set in the configuration, which in turn will have priority over the local storage. If a non-existent selection has been set as a query parameter, no value will be applied.

    Please, be aware that setting to many fields via url parameters can lead to issues, as there is a general limit on the length of an HTTP url, depending on the used client browser and server configuration. Therefore, it is not recommended to use this option on too many input widgets.

  14. Activate the Mark as required checkbox to have the user fill out this field.

  15. Open the Advanced Settings pane to define the background color and the text color for the field.

    1. In the drop-down list next to the Color field, select one of the following options for the background color:

      • Value
        Enter a color code or click the color square to select another color.

      • Data Source
        Select a parameter path from the drop-down list.

      • User Context
        Select a user information parameter as a source for the color.

      • Filter Widget
        Select a Filter widget parameter from your dashboard.

      • Input Widget
        Select an Input widget parameter from your dashboard.

    2. In the drop-down list next to the Color field, select one of the following options for the text color:

      • Value
        Enter a color code or click the color square to select another color.

      • Data Source
        Select a parameter path from the drop-down list.

      • User Context
        Select a user information parameter as a source for the color.

      • Filter Widget
        Select a Filter widget parameter from your dashboard.

      • Input Widget
        Select an Input widget parameter from your dashboard.

Use the reset icon images/confluence/download/thumbnails/3694133036/icon_reset-version-1-modificationdate-1701699791000-api-v2.png to set the colors back to default.