Skip to main content
Skip table of contents

Version Information

New Features

TSM-7136 Licensing: Check for Product Version in Event of a Network Error

3.10.6.1

Version 3.10.6.0 introduced some changes to how HAKOM products verify the existence of an active license. Following feedback collected in response to these changes, some additional changes were made in patch 3.10.6.1 that should make working with licenses easier and more transparent. Most noteworthy, the TSM App can automatically fall back to verifying the <ProductVersion> in the local license file in the event of transient PowerTSM Cloud service outages.

TSM-6800 Reading Attribute Values in the Data Template Using the WebTSM Service Connection

3.10.6.0

Previously, attribute values in the data template (rows 2-8) could only be read via DB connections. Now it is also possible to use this feature when connected to a WebTSM service instance.

TSM-6792 Consolidate Versioning of MSCONS Converter with that of HAKOM PowerTSM

3.10.6.0

Up until now, the MSCONS Converter had a separate version number even though it shares its development and release cycle with the rest of the HAKOM PowerTSM product line. Starting with this release, the MSCONS Converter is versioned as part of the product, causing its version to jump from 1.0.2 to 3.10.6.

TSM-6767 TSM App: When Editing Time Slots, Show the Name of the Attribute the User is Currently Editing Time Slots For

3.10.6.0

Before now, the user was not able to see which attribute they were currently editing time slots for. To make things clearer, the window now displays the name of the attribute.

TSM-6590 More Intuitive Placement of Application Insight Configuration Entry

3.10.6.0

Previously, the connection string for enabling logging to Microsoft Application Insights was located in WebTSMServices:ApplicationInsights:ConnectionString in the HAKOM.Config file. Now it can also be placed in WebTSMServices:Logging:ApplicationInsights:ConnectionString as it was considered a more intuitive location being nested inside the “Logging” section. To ensure backwards compatiblity however, the old placement will continue to work as well.

TSM-6596 Changed Dependency of SQL Server Client

3.10.6.0

The driver used to access Microsoft SQL Server databases was migrated from System.Data.SqlClient to Microsoft.Data.SqlClient in order to enable WebTSM Service cloud usage without storing database credentials in configuration files.

TSM-6834 WebTSM Service: Request Header Now Accepts Parameter numberFormat

3.10.6.0

Previously, any invalid values of a formula time series (i.e. the result of a division by zero) would simply be returned as the value 0. As this is mathematically incorrect and leads to unintended results when opening an affected time series with the SetCellEmptyIfValueIsNaN setting in the TSM App configuration file, a new formatting parameter has been introduced in the WebTSM Service: numberFormat. As with most other format related parameters this is added to the Accept header, i.e. Accept: application/json;numberFormat=<value> When this parameter is set to string, all time series data values in the response are formatted as strings, and invalid numbers are displayed in a descriptive way (e.g. infinity, NaN). For more information on how to apply this setting look here.

TSM-6952 Licensing: Check for PowerTSM User or Product Version

3.10.6.0

Up until now, licenses were issued for a specific time period and required frequent renewal. This has been changed so that the validity of a license is now checked by ensuring that the user is an active PowerTSM Cloud user. In situations where this is inpractical (i.e. in deployments that do not have access to the internet), a special license may also be issued which does not require this check. However, this license is then only valid for certain versions of the product.

TSM-6761 API Key Authentication

3.10.6.0

Starting with this version, PowerTSM supports the use of API keys as an authentication method. This is particularly useful for automated processes that need to write or read data via WebTSM services, for example. API keys can be generated and managed via WebTSM services. For more details, see the Operator's Guide → WebTSM Services API → Authentication → API Key Authentication.

Fixed Bugs

TSM-7125 WebTSM Services: Out of Memory When Processing Many Ad-Hoc Formulas Over a Long Period of Time

3.10.6.1

Due to unexpected behavior in a .NET component, memory being allocated during the evaluation of ad-hoc formulas was not released correctly. This caused the WebTSM Service to report a lack of available memory when running for a sufficiently long time (weeks, depending on the frequency of ad-hoc calculations performed). While the underlying issue in the .NET CLR persists, this patch includes a change in how ad-hoc formulas are processed, greatly reducing the likelyhood of the issue

TSM-6838 TSM-App: Incorrect Error Handling When Trying To Save Time Series With a Name That Is Too Long

3.10.6.0

After creating a new time series with a name that is over 450 characters long an error occcured. Now, a pop-up window explains the error and also prevents the user from accidentally deleting the time series when navigating away from the window before saving.

TSM-6828 TSM-APP: Incorrect Sorting of Data by Quotation Date

3.10.6.0

Loading data from an HTTP data source should now return data sorted by the quotation date. This means that the data is returned in descending order, starting with the latest quotation date.

TSM-6827 TSM-App: Incorrect Saving of TimeSpan Attributes When Creating Time Slots

3.10.6.0

Escaping the input box of TimeSpans in an unexpected manner during the creation of time slots has led to unsaved TimeSpan values. The issue behind this bug has now been resolved.

TSM-6826 TSM-App: Unintuitive Input for Multiline Attributes

3.10.6.0

To enter a line break in a multiline attribute the user was forced to press Ctrl+Enter. This is unintuitive and it is now possible to achive the same result using only Enter.

TSM-6823 TSM-App: Displaying Line Breaks for Multiline Text Attributes

3.10.6.0

Importing time series from Excel, which contain multiline text attributes, caused malformatted newline characters. This issue has now been resolved, thus allowing for the correct display of line breaks in the PowerTSM App for multiline text attributes.

TSM-6822 TSM-App: Date Attributes Used With Time Slots Do Not Display Time

3.10.6.0

When editing time slots for a date attribute users could previously only specify a date with no option to define a time. This has now been improved to support the specification of a time as well.

TSM-6784 TSM-App: Unexpected Behavior in Calender Dialog

3.10.6.0

When selecting the date of a Time Slot via the Calendar Pop-Up Window, users were unable to navigate properly. After pressing an arrow key, instead of moving to the next time unit (e.g., next month or day), the calendar would close and automatically select the first available date in that unit. This is no longer the case.

TSM-6837 TSM-App: Settings for Start of Day and Start of Year Not Respected When Data is Read From a HTTP Connection

3.10.6.0

When reading data of a time series which has its "Start of day" and/or "Start of year" properties set to something other than the default, the time ranges loaded into the sheet read were incorrect.

TSM-6818 TSM-App: Conflicts When Creating Time Series and Attributes With Same Name

3.10.6.0

When creating a new attribute, users were previously able to give it the same name as an existing time series, leading to confusion and errors. This has now been fixed, and users will receive a clear error message.

TSM-6820 TSM-App: Report Functions in TSM Plus did not Support Default Values

3.10.6.0

In Excel, certain parameters could be left blank in the Report Functions and a default value was then used for them. TSM Plus had an error in this regard. This error has been fixed.

TSM-6813 TSM App: Search for Root Nodes Not Working

3.10.6.0

When searching for time series based on their assigned tree nodes (i.e., attributes of type 'Node'), selecting a root node did not yield the expected results. This issue has now been resolved, and searches including root nodes work as intended.

TSM-6821 TSM App: Date Attribute Cannot Be Set to Current Date

3.10.6.0

Previously, it was not possible to set a date attribute to the current date. This has now been fixed. The default value for the control has been updated to be empty instead.

TSM-3420 TSM App: Incorrect Behavior When Searching for Attributes Containing an Underscore

3.10.6.0

A bug was fixed that caused unexpected search results when working with attributes that contain an underscore (e.g., “test_attribute”). This has now been resolved and searches work as intended.

TSM-6896 WebTSM Services: No Error Message When Writing Data Before 1970

3.10.6.0

Attempting to write data with a timestamp before 1970 previously failed without an informative error message. This has now been fixed, and users will receive a clear message explaining the issue.

TSM-6937 TSM App: Inconsistent Date Formats in Time Slot Edit Tab (English Language)

3.10.6.0

This issue occurred only when using TSM with the language set to English. When editing time slots for a date attribute, the date format in the "Attribute Value" column followed the German format (DD.MM.YYYY), while the "Slot" column correctly used the English format (MM/DD/YYYY). This unintuitive way of displaying data has been changed, ensuring that now both colums use the correct English format.

TSM-6836 TSM App HTTP Connection: Dates/Times in Quotation Dropdown Displayed in Incorrect Time Zone

3.10.6.0

When choosing a date/time in the quotation dropdown, all entries were displayed in UTC regardless of the time zone in which the time series was saved. The issue has now been resolved, ensuring that timestamps are displayed in the correct time zone.

TSM-6938 HAKOM.Config: The Settings for Caching of Authorization Rules Have Been Moved

3.10.6.0

Due to internal reordering of code, please be advised that the settings <Enabled> and <Expiration> for <Caching>of Authorization has been moved from the <WebTSMServices> section in the HAKOM.Config file to the <Caching> section under //HAKOMConfiguration/products/HAKOMFramework/settings/Authorization. For now, the setting will still be respected if found in its original location, but please be aware that this will be changed in a future release.

TSM-6695 TSM App: Issues With Category Attributes in Time Slots

3.10.6.0

When editing a category attribute in the time slot window it was not possible to set the value to “Not Assigned”. Even when importing a time series with values set to “Not Assigned”, they would be displayed only as “Assigned”. This bug has been fixed so time slot values can be edited and displayed as expected. Additionally, it is no longer possible to edit a category attribute outside of the time slot window because it is not sensible to do so.

TSM-6868 TSM App: SetCellEmptyIfValueIsNaN Configuration Does Not Work With HTTP Connections

3.10.6.0

The setting SetCellEmptyIfValueIsNaN did not display non-numerical values as “NaN” or “Infinity” but as “0” when using an HTTP connection. This was not as expected and was fixed by implementing the ability to return NaN and Infinite values from the WebTSM Services (see new feature: TSM-6834)

TSM-6410 WebTSM Services: Wrong Response Status Code

3.10.6.0

When accessing a restricted endpoint without credentials, the service would in some circumstances respond with a status code 500 (Internal Server Error), instead of the expected 401 (Unauthorized). This has been fixed.

TSM-6721 WebTSM Services: Delete Endpoints Result in Timeouts

3.10.6.0

When trying to delete a time series and associated data a timeout error could be caused it the amount of data deleted was too large. This bug has been fixed.

TSM-7070 TSM App: Long Loading Times With Attributes in Template

3.10.6.0

When performing certain actions on a time series template that requires a large number attributes to be loaded, the PowerTSM app would freeze. This bug has been fixed.

TSM-7104 TSM App: Copying a Time Series Throws an Error

3.10.6.0

When copying a time series that had not yet been assigned any attributes, an error occurred. This bug has been fixed.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.