- February
- February 09, 2026: Overview | Download Traffic added in Project stats widget
- February 05, 2026: Data Recorder Service | The maximum total upload size increased
- February 04, 2026: Event Services and Event Notifications | Test Button added for Subscription Actions
- February 03, 2026: Breadcrumbs | Navigation improved with currentURL parameter
- February 02, 2026: Usage and Estimated Costs | New metric Download Traffic introduced
- January
- January 27, 2026: Table widget | New parameter pageIndex supported
- January 26, 2026: Feedback banner | Placeholders supported
- January 23, 2026: Collections | Atlas Search view added
- January 22, 2026: Chart widgets | Personal reports available
- January 19, 2026: Data Transformation | Placeholder in JMES Path Query
- January 14, 2026: User APIs | New property naming
- January 13, 2026: Table widget | 'Clickable row' functionality extended to support multi action buttons
February
February 09, 2026: Overview | Download Traffic added in Project stats widget
We improved the Overview of a project with a new Download Traffic item in the Project stats widget. Now, it is easier for you to monitor the download volume of a project for the current month for data downloads and REST requests:
For more information about Project stats widget, refer to Project Stats user guide.
February 05, 2026: Data Recorder Service | The maximum total upload size increased
For resumable uploads via the Data Recorder Service, the maximum total upload size was increased from 50 to 256 GB.
Find more information about the Data Recorder Service and the resumable upload in Data Recorder Service developer guide.
February 04, 2026: Event Services and Event Notifications | Test Button added for Subscription Actions
Test buttons are now available for all subscription actions, based on the current configuration. For example:
Use the following test buttons to validate your current configurations:
- Send Test E-Mail button sends the actual E-Mail.
- Send Test SMS sends the actual SMS – supported in Event Services.
- Send Test HTTP-Request button sends the actual REST request.
- Send Test Notification button creates the actual notification – supported in Event Notifications.
- Send Test Notification to myself button creates the actual notification, but only for the current user – supported in Event Services.
When the button is clicked it sends a request with the action definition and the example payload, which is shown on the UI, to the endpoint.
The status appears below the button showing the loading status and the result status or error:
For more information about the Event Notification and Event services, refer to Event Notifications and Event Service user guides.
February 03, 2026: Breadcrumbs | Navigation improved with currentURL parameter
To spear you from manually adding the navigation path when dashboards navigate to the same detail views from different entry points, we have introduced a new context parameter currentUrl to the list of the default Insights parameters:
The parameter is available in the basic widget context. The following is an example of how to set the link with the ${insights.currentUrl} placeholder:
The new navigation context parameter currentUrl allows widgets to build URLs relative to the current dashboard path. Navigation using the current URL reference results in correct breadcrumb hierarchy as described in the following example:
The dashboards of Widgets (Compact Grid) and Dashboard can both navigate to shared views, but via different URL paths. For example, migration can be reached through:
- /Widgets (Compact Grid)/dummy/migration
- /Dashboard/dummy/migration
Similarly, dummy can be accessed from both dashboards. The image below is a visualization of the shared migration detail view via Dashboard/dummy path:
For more information about the breadcrumbs, refer to the Nesting a dashboard section of Dashboards user guide.
February 02, 2026: Usage and Estimated Costs | New metric Download Traffic introduced
Requests to endpoints for downloading Input Data and requests based on customer-defined REST request definitions now unblock read tickets as soon as the download has started. The number of downloaded bytes is measured and billed per GB. The usage in GB is always rounded down. For the current pricing details, refer to the internal pricing information.
Previously, read tickets were blocked for the whole duration of input data downloads and REST requests, which caused other users' requests being blocked. This situation is now improved and the slow download speed does not impact the overall user experience in the mentioned cases anymore.
As a project administrator, you can monitor the accumulated download traffic per billing month by navigating to Admin > Usage and Estimated Costs > Metric, and selecting the new Download Traffic option from the drop-down menu:
Starting with one of the next releases, we will enhance the Query History to provide you with more information about how download traffic is tracked.
January
January 27, 2026: Table widget | New parameter pageIndex supported
In the External Data Source, the list of parameters, namely pageSize, pageNumber, and pageOffset, is now extended with pageIndex. The pageIndex parameter is always one number lower than the pageNumber. Depending on your endpoint pagination, you can either use pageIndex or pageNumber.
If you use Bosch IoT Insights endpoints, it is preferable to use pageIndex parameter instead of pageNumber, as the respective endpoints use a Zero-based counter.
For details about Table widget, refer to Table widget user guide.
January 26, 2026: Feedback banner | Placeholders supported
Navigating to Admin > White Labeling > Basic Settings allows you to configure a feedback banner link for your dashboard. Now, the feedback link supports placeholders as the one of $(insights.user.id) in the example below:
For more information on the feedback banner and the White Labeling settings, refer to the Basic Settings user guide.
January 23, 2026: Collections | Atlas Search view added
The new Atlas Search view allows management of MongoBD indexes. Now, you can list, update, and delete existing indexes, and create new ones. Each index in a list can be expanded to reveal a read-only JSON editor displaying its configuration. The Atlas Search Index configuration is defined and managed using a JSON-based definition. The JSON editor supports Undo/Redo actions, Format (auto-formatting JSON), and Copy content.
For general information, refer to MongoDB Search Overview - Atlas - MongoDB Docs.
For more information on Collections and the views of Details, Indexes, and Atlas Search, refer to Collections user guide.
January 22, 2026: Chart widgets | Personal reports available
The personal reports used to be applicable for Table widgets only. Now, you can configure personal reports in the same way as described in Personal Reports for your Chart widgets, too, starting from the User Menu icon and selecting the respective option from the drop-down menu:
Additional parameters can be set up as described in Enabling additional parameters on Chart widgets level section of the Personal Reports guide:
The visualization of the generated report may look like the following tunnel:
For more information about the chart widgets, refer to Chart widgets guide.
January 19, 2026: Data Transformation | Placeholder in JMES Path Query
Now, JMES Path Query supports also non-data source placeholders like insights, filterParams, inputFields. Find more general information in JMESPath documentation.
You can configure your JMES Path Query from the Data Transformation pane. When editing a widget, you can view all available placeholders in the Test Parameters tab. See the example below::
For more information about Data Transformation, refer to the respective Data Transformation section in each widget where available.
January 14, 2026: User APIs | New property naming
API users (technical users) used displayName property for their description. A new description property has been introduced to hold the description for API users. During this refactoring the internalName property was renamed to username, because it represents the Bosch IoT Insights wide unique username.
The name property was removed, because it was confusing which name was meant.
Breaking changes:
- Create API user endpoint, does not accept
displayNameanymore, now the property is nameddescription - Filtering for audit log and other user referenced can't be done by description of the API users, but by their
username/displayName.
Deprecated usages:
- User Management API to get users:
- Replaced
nameproperty withdisplayName - Replaced
internalNameproperty withusername - New property
descriptioncontains now what was indisplayNamefor API users
- Replaced
- Placeholders or references should be updated:
insights.user.internalNametoinsights.user.username - Placeholders or references should be updated:
insights.user.nametoinsights.user.displayName
Find more information in Users how-to guide.
January 13, 2026: Table widget | 'Clickable row' functionality extended to support multi action buttons
Regarding the Hyperlink/Action button options of the 'Clickable row' functionality, the drop-down list also displays all defined hyperlink or action buttons:
When clicking anywhere on a table's row, the selected action or hyperlink will be triggered or opened. The mouse cursor will indicate if a row is clickable. If other columns of the table also contain action buttons or hyperlinks, these can be clicked directly in the table. Clickable rows are highlighted by default upon mouse hover.
More information about Table widget is provided in Configuring the table settings user guide.














