Version Information
New Features
TSM-6676 TSMApp - Opening Time Series With Parameters When Accessing an HTTP Connection
It is now possible to open quotation-, audit- and formular time series with their respective parameters when accessing the time series through an HTTP Connection. The feature now functions in the same way as when directly accessing time series through a database connection.
TSM-6352 WebTSM Services - Calculation Endpoints: Added Support for Unit Conversion
The WebTSM Services calculation endpoints now support two new parameters:
unit
Sets the unit in which data should be returned. If the unit differs from the respective time series native unit, a conversion to this unit will be attempted.calculationUnit
Sets the unit for the result of the calculation. If theunitparameter is different, a conversion will be applied from thecalculationUnitto theunit.
As a result of this new feature, correct unit conversion for ad hoc formulas in the TSM app is guaranteed when connecting to WebTSM.
TSM-6503 TSM App - Timestamps Added to Reporting Functions
The TSM App reporting functions now feature a new parameter: showDates. If true, a precise timestamp is also provided for each data entry in a seperate column. More on reporting functions can be found here.
TSM-6679 TSM App: Deleting Time Series From an HTTP Connection
The TSM App now supports deleting time series definitions when accessing an HTTP connection just the same as when accessing a database directly.
TSM-6674 TSM App: Enabling the Use of Ad-Hoc Formulas When Accessing an HTTP Connection
The TSM App supports loading time series data based on an ad-hoc function (rather than a stored time series) directly from its main window. Previously only available when accessing a database directly, this feature is now also enabled for when accessing an HTTP connection.
TSM-6796 WebTSM Services: Added New Endpoint For Exchange Time Series
A new endpoint has been created in the WebTSM Services. This endpoint returns the names of all time series that can be used in unit conversions. The new endpoint can be accessed at:
GET <BaseUrl>/<repository>/exchangetimeseriesnamesTSM-6680 TSM App: Creating and Editing Time Series Over an HTTP Connection
It is now possible to create and edit time series with the TSM app when using an HTTP connection to WebTSM services.
TSM-6682 TSM App: Assigning Attributes to Time Series Over an HTTP Connection
It is now possible to assign attributes to time series and to edit attribute assignment values with the TSM app when using an HTTP connection to WebTSM services. This applies to all attribute types except “list” - they can only be assigned, when using a database connection.
Fixed Bugs
TSM-6754 TSM App: Attributes Are Not Saved Correctly After Manipulating Them Through Time Slices
After manipulating a node attribute in the time slices window and then changing the node of said attribute the second change would not be saved correctly. This bug has been fixed.
TSM-6686 TSM App: Error When Referencing a Time Series With “/” in Unit Name
When referencing a time series whose unit contains a “/” in its name (e.g “EUR/MWH”) in an ad-hoc formular an error message would appear. This has been fixed and it is now possible to use said time series in this way.
TSM-6241 TSM App: Incorrect Save Prompt Caused for Spontaneous Time Series With No Interval
When editing spontaneous time series without interval created with WebTSM Services, the TSM app incorrectly prompted to save when switching between windows, even if there were no actual changes to save. This has now been fixed so that switching windows should no longer trigger unnecessary save prompts
TSM-6450 WebTSM Services: Incorrect Date When Aggregating To The Last Value In The Range
When reading data using WebTSM Services with the aggregation type “LastValueInRange”, the date of the last data entry was displayed instead of the first. This has been fixed so that the affected time series are now compatible with other time series.
TSM-6461 Error When Reading Data of Formula Time Series With Enabled Caching
After upgrading to newer TSM versions, errors may occur with formula time series and enabled caching, for example: “Method not found.” This error has been fixed.
TSM-6607 Password Encryption Console: Non ASCII Characters Generate Different Passwords Then TSM Products
TSM products only support ASCII characters for passwords. If a password contains a non-ASCII character, this character is replaced by a question mark. This behavior differs from that in the Password Encryption Console and therefore there are differences. The Password Encryption Console has now been adapted to the TSM products.
TSM-6677 Error When Aggregating Time Series With Time Slots
When time series were aggregated on an attribute and the time series had multiple time slots for the attribute, the results were incorrect. This error has been fixed.
Additionally it is important to note, that internally, attribute based aggregations (including thos based on the TSAA function) can be performed in two ways. One of these is performance-optimized, but requires that all time series share the same unit, interval and time zone. If either of those is different, the performance-optimized aggregation will be incorrect. In order to use the slower but in these cases more suitable method, one of the following three must be true:
a unit must be specified for the aggregation
a time zone must be specified for the aggregation
MaxDegreeOfParallelism must be equal to 1
TSM-6753 TSM App: Intermittent Error When Accessing Data From an HTTP Connection
Due to an issue with concurrent data processing, the application sometimes reported an error when retrieving time series data from an HTTP data source. The issue has been resolved.
TSM-6733 TSM App: Intermittent Error When Loading Reporting Functions in PowerTSM Plus
An intermittent error occurred when attempting to load a reporting function immediately after starting PowerTSM Plus, particularly during longer loading times. The issue has been resolved.
TSM-6702 TSM App: Incorrect Display of Node Attributes
When editing time slices of an attribute assignment and the attribute was of type “Node” the time slices where displayed incorrectly. This has been fixed.
TSM-6701 Incorrect Aggregation Type for Unit EUR
When initializing a database, the predefined units had an entry for Euro (EUR) with its aggregation type set to average (AVG). While there are some use cases where this does make sense, the most common use cases expect currencies to be aggregated using the sum function. This release modifies the initial database setup so that the EUR currency uses summation by default. Note that existing databases are not changed to ensure that the behavior does not change for existing time series.
TSM-6691 TSM App: Missing German Translations in Time Slice Editing UI
The user interface for editing attribute time slices had several buttons with captions that were not properly translated, causing them to show up in english even when the TSM Apps UI was set to German.
TSM-6685 WebTSM Services: Timeouts When Deleting Archived Time Series Data
When deleting the archived data of previously deleted time series using the DELETE /repositories/{repository}/deletedtimeseries endpoint, the request sometimes ran into timeouts. This has been fixed for the DELETE /repositories/{repository}/deletedtimeseries endpoint. Note that some other endpoints may be affected too. This is being tracked in TSM-6721 which is currently scheduled to be fixed with release 3.10.6.
In addition, there is now improved logging of the deletion progress, so issues can be tracked down more easily in the future.
TSM-6636 WebTSM Services: Incorrect Array in the OpenAPI Specification
The OpenAPI specification used to show, that the body of post requests to the /repositories/{repository}/timeseriescollections/data endpoint needs to contain an array of TimeSeriesDataCollectionBulkArray items. The TimeSeriesDataCollectionBulkArray itself is an array of TimeSeriesDataCollectionBulkItem items, so this resulted in a nested array of TimeSeriesDataCollectionBulkItem items. The problem has been resolved and the specification now correctly shows the request body as requiring an item of type TimeSeriesDataCollectionBulkArray in the request body. This affects client code automatically generated based on the specification.