Device Management Issues Resolved in 2024.08

The following issue with device management was resolved in the 2023.08 release.

Additional Control Characters Considered by Configuration Option “Retain Non-Printing Characters in Device ID and Alias”

Before the 2023.05 release, when a device was created using a capability request and the “Device ID” or “Alias” field contained an invalid control character, the Devices page did not load as expected. To resolve the issue, the configuration option Retain Non-Printing Characters in Device ID and Alias (located under System > Configure > Embedded Devices > Host Options) was introduced. When this option is unselected (the default setting), invalid characters in the “Device ID” or “Alias” field are replaced with an empty string (for example, the device name Test^FName is saved as TestName). As a result, the Devices page loads without errors.

In the 2024.08 release, more control characters have been added to the list of invalid control characters that will be replaced with an empty string if the configuration option Retain Non-Printing Characters in Device ID and Alias is unselected. The full list is below, with the added characters highlighted.

^B, ^D, ^E, ^G, ^N, ^O, ^P, ^Q, ^R, ^S, ^T, ^U, ^W, ^X, ^Y, ^[, ^\, ^], ^F, ^C, ^^, ^A, ^V, ^_

As a side effect, when an invalid character is used in the “Device ID” or “Alias” field and subsequently removed by FlexNet Operations, the license will not be processed by the FlexNet Embedded toolkit. Revenera aims to address this issue in a future release of the FlexNet Embedded toolkit. In general, invalid control characters should not be used when creating a device using a capability request:

Note:This resolved issue is a continuation of the issue “Devices Page Now Loading Correctly When Device Name Includes Invalid Control Characters” that was resolved in the 2023.05 release. For more information, see the FlexNet Operations 2023 Release Notes that are available on the Revenera Product Documentation site.