Bosch IoT Insights – New Service Update – Device Access Rights for Input History, Retention Time extension, and more

Device Access Rights for Input History

This feature enables you to bind you uploads to devices and to restrict the download to the specific device permissions.
So, it is now possible to control which user can access which kind of uploaded content.

To use this feature, you need to add a “X-ThingId” header containing the appropriate device IDs to your uploads. In case of a manual upload inside of the Bosch IoT Insights UI you are now able to add devices to your upload as you can see in the screenshot.

When using this feature, you can see which devices are bound to a specific upload inside the Input History,
by expanding the details or selecting the preview of an entry.

The following rules are applied in general:

1. If no devices are bound to an upload
   the user with access to Input History can download / preview the payload.
2. If devices are bound to an upload and a user can access all bound devices
   the user can also download / preview the payload.
3. If devices are bound to an upload, but the user can not access all or some of the bound devices
   the user will not be able download / preview the payload which is also signaled by the tag “no-access”.
4. When using the “Download All” function, only payloads will be downloaded on which the user has access (all bound devices).
   

Furthermore, it is now possible to filter for bound devices.

Retention Time Management now includes Query History

In a  previous release note we introduced Retention Time Management.
Now, you can also set the retention time for Query History entries.
As the project admin you can define it based on the creation time of the query request.
The default is 90 days.
Further options will be added in the next update.

Redis Service Side Caching Optimization

Placeholder Support in Widget Titles

It is now possible to use placeholders inside of widget titles.
Depending on whether a filter widget or a widget data source exists, you can add the corresponding placeholder: e.g.

• Widget ${filterParams.param}
• Widget ${[0].payload.value}

Update of Icon Library

The front-end icon library was updated to provide a more icons to all users.

Rework Admin/Users layout

The Management UI has been refactored to allow a better usability and focus on the most important functions.

Extended RAM and Disk Size for Pipeline Apps

As a result of the infrastructure migration to Microsoft Azure, you get higher infrastructure limits for processing pipelines:

• the limit for RAM per pipeline instance was increased from 8GB to 32GB.
• the limit for disk space per pipeline instance was increased from 4GB to 32GB.

In case of problems with this limit, or if a higher amount is needed, please contact our support.

Second y-axis option for signal chart

An option to change the assigned Y axis is added under advanced settings.
You can change from the default Y axis to the Y2 axis where all values will be transferred and vice versa.
E.g., for Line Chart

Action Button with new type to Copy URL

The Link Button inside of the Action Button widget – as well as the hyperlink custom column definition type inside of the table widget – now support a new “Copy to clipboard” option, which allows the underlying link to be copied when clicked instead of navigating.

JMES Data Transformation

JMES Data Transformation enables the user to transform data on client side.
Especially when a widget has multiple data sources, or sources which are not based on a query template, this additional transformation stage allows you to adapt the retrieved data to your visualization needs.

This powerful tool extension provides new options to all users to optimize data for visualization.
See also the JMESPath documentation for a set of options.

SingleKey ID

Bosch ID will be migrated to SingleKey ID within 2023.
More details on SingleKey ID can be found at https://singlekey-id.com.

In preparation for the switch several changes have been made to support it and an announcement has been sent to each user.
As soon as it is available in early April you will see a screen like the following:

Rich Text Widget with Datatype Conversion

The rich text widget now supports data type conversion for reference values.
The data type conversion offers general transformation properties (like prefix, suffix, etc.), but also type specific options for String, Number and Date.

The following sample shows how to modify the output of a date field.
For more details see Rich Text.

  –> 

Tab Widget with URL for Bookmarking

You may already be aware that you can share and bookmark URLs of dashboards with filter parameter. Now you can also share and bookmark them if the dashboard contains a tab widget.

Technically, the URL will have a selectedTab number showing the index of the selected tab.
This guarantees that the dashboard will be opened within the same tab.

Further improvements

• Device Details Widget: images can be replaced directly from the device widget.
• Signal Chart: a “name” field is added to reference the signals visualized inside the chart; this is similar to other charts, e.g. Line Chart.

Bugfixes

In this release, we have addressed and fixed the following bugs:

• INS-4458 – Map Widget connected to “no data” Replay Widget should show “No data available”
• INS-4554 – Linking for processing information with multiples IDs does not work
• INS-4450 – Processing Information: Delete processed data does not work
• INS-4408 – Simple Search: Broken Input Validation and Chip-Update Mechanism
• INS-4468 – Data Browser: It shouldn’t be possible to add a search filter with an empty path
• INS-4462 – Map should be centered also when showing a legend
• INS-3680 – Device Details Widget: Issues in Notes Information Block edit mode
• INS-4592 – Widgets Data Sources: External Data Source cannot be removed
• INS-4907 – Map Widget: Defined Symbols should be shown in legend with all pins chosen
• INS-4909 – GPX map flickering
• INS-4892 – GPX Tracks are not shown anymore in Map Widget
• INS-4602 – Attributes feature in device management is not working properly