Version Information

New Features

TSM-6788 New Method for Interval Transformations

This version introduces a new method for transforming time series across intervals: ValidAverage. This method behaves similarly to the Average method, but disregards values with Missing¹⁾ flags.

This feature can be used in:

transforming time series data during queries
defining how data should be stored on a time series
defining how units should behave during interval transformations

1) This feature also introduces a new configuration setting: //HAKOMConfiguration/products/HAKOMFramework/settings/ValidAverageAggregationFlagThreshold

For more information, see

TSM-8138 Delete Time Series Data in a Time Range (Framework API & HTTP API)

The Framework API now lets you delete data of an individual non‑quotation time series either for all timestamps before a given date, within a specified time range, or – if no range is supplied – for the entire time series, while audit and archive data remain untouched. Begin and spontaneous time series treat the range as a left‑closed/right‑open interval, end time series as right‑closed/left‑open, and spontaneous time series additionally insert a 0/Missing entry at the start of the deleted range (and restore the value at the end) so that the resulting curve remains consistent.

Via the HTTP API, you can apply the same deletion logic for one or multiple time series in one request, selecting them by IDs, names, or wildcard name searches, each with its own time range or “until” date; bulk deletion is only available via HTTP. All HTTP endpoints support background (“fire and forget”) execution with detailed logging and optional callbacks per time series to make larger cleanup operations easier to automate and monitor.

TSM-8146 Delete Archived Time Series Data in a Time and Audit Range (Framework API & HTTP API)

The Framework API has been extended so that you can delete archive entries of an individual non‑quotation time series based on flexible filters, without changing the main data or audit tables. You can remove archive data

by data time (all entries before a given timestamp or within a data time range),
by audit time (all entries before a given audit timestamp or within an audit time range), or
by combining data‑time and audit‑time filters in a single request,
with unsupported or ambiguous combinations being rejected to keep archive data consistent.

Via the HTTP API, you can apply the same deletion logic for one or multiple time series in one request, selecting them by IDs, names, or wildcard name searches, each with its own time range or “until” date; bulk deletion is only available via HTTP. All HTTP endpoints support background (“fire and forget”) execution with detailed logging and optional callbacks per time series to make larger cleanup operations easier to automate and monitor.

TSM-8151 Delete Time Series Audit Data and Underlying Archive Data (Framework API & HTTP API)

The Framework API now supports deleting audit entries of an individual non‑quotation time series either for all audit timestamps before a given date, within a specified audit time range, or – if no range is given – for all audit data of that series, while the main data table remains unchanged.

When audit entries are deleted, any associated archive entries belonging to those audit states are removed as well, so that no orphaned archive data remains.

If a quotation time series is passed, the deletion fails because its audit data is required to read quotation values.
If a time series with Audit = false is given, only audit data will be deleted and archive data will be left untouched.

Via the HTTP API, you can apply the same deletion logic for one or multiple time series in one request, selecting them by IDs, names, or wildcard name searches, each with its own time range or “until” date; bulk deletion is only available via HTTP. All HTTP endpoints support background (“fire and forget”) execution with detailed logging and optional callbacks per time series to make larger cleanup operations easier to automate and monitor.

TSM-8161 Delete Quotation and Audit Times for Quotation Time Series (Framework API & HTTP API)

The Framework API for quotation time series has been enhanced so that you can delete quotation data and quotation audit data of a quotation time series by quotation period, by audit period, or by combining both. The new retentionMode can be used to specifiy wether the data should be deleted completly or the last entry in the affected range should be kept

for quotations: delete all quotations in the range, keep only the last exact quotation, or keep the full combined result that would be returned at the last quotation timestamp in non‑exact mode;
for audits per quotation: delete all audit entries in the range, keep only the last exact audit state per quotation, or keep the full set of audit entries that would be returned at the last audit timestamp in non‑exact mode.

The endpoint for deleting one time series as well as the endpoint for the bulk operation previously supported only an until parameter (and no timeseriesSearchName) This legacy behavior remains available when you specify the header api-version=3.11.0, while newer versions use the extended parameters (including QuotationUntil and search‑based selection).

Via the HTTP API, you can apply the same deletion logic for one or multiple time series in one request, selecting them by IDs, names, or wildcard name searches, each with its own time range or “until” date; bulk deletion is only available via HTTP. All HTTP endpoints support background (“fire and forget”) execution with detailed logging and optional callbacks per time series to make larger cleanup operations easier to automate and monitor.

TSM-7047 TSM App: Value of List Attribute Shown Alongside Description

List attributes now display both the description and the assigned value to users. Previously, only the description was visible, making it impossible for users to determine the correct value needed for searches and aggregations. The new display pattern is: <Description> ("Value:") <Value>) - showing "Wert:" for German and "Value:" for English language settings.

TSM-8279 TSM App: Extended Attribute Search (4+ HTTP API)

OR-Attribute-Search is now possible using an “Advanced Attribute Search Dialog“. The TSM App Time Series Search Form has been adjusted to fit the two new buttons.

Fixed Bugs

TSM-7968 WebTSM Services: Errors During API Key Authentication are Not Shown in Logs

When an error occurred during validation of an API key, it was logged with log level “Information”, which is not enabled, by default. These errors are now logged with log level “Error” causing them to show up in logs by default.

TSM-8244 WebTSM Services: Large Callback Messages with Web Hooks Cause No Callback Message to Be Sent

When registering a web hook in the configuration with a large CallbackContent (for example, when using the $REQUEST_CONTENT variable), the WebTSM Service did not send any callback messages and only logged an error. This behavior has been improved: When the content of a callback message becomes too large, an empty callback message is sent to the web hook’s callback address (the error is still logged).

TSM-8299 – Parsing CommentAreaInfo Fails for Worksheet Names With Numbers

When reading data for a time series from Excel, worksheets whose names contain a number could cause an error while parsing the CommentAreaInfo. The parsing logic has been corrected so that such worksheet names are handled properly and time series data can now be read without this error.