Device Management Issues Resolved
The following issue with device management was resolved in the 2025 R1 release.
Replacing Control Characters in Device Names
(Cases 02845338, 02845338; SWM-21484, SWM-22488)
This resolved issue is a continuation of the issue Devices Page Now Loading Correctly When Device Name Includes Invalid Control Characters that was addressed in the 2023 R1 release. For more information, see the FlexNet Operations 2023 R1 On-Premises Release Notes that are available on the Revenera Product Documentation site.
Previously, when a device was created using a capability request and the “Device ID” or “Alias” field contained a control character, the Devices page did not load as expected. As part of the initial fix, made in the 2023 R1 release, control characters in the “Device ID” or “Alias” field were replaced with an empty string (for example, the device name Test^BName was saved as TestName).
The behavior is controlled by the configuration option Retain Non-Printing Characters in Device ID and Alias (located under System > Configure > Embedded Devices > Host Options), introduced in 2023 R1.
As an unintended consequence of this change, if an invalid character was used in the “Device ID” or “Alias” field and subsequently replaced by an empty string by FlexNet Operations, the license was not processed by the FlexNet Embedded toolkit.
To fix this, in the 2025 R1 release, all control characters are replaced with their respective hexadecimal values if the configuration option Retain Non-Printing Characters in Device ID and Alias is unselected (the default setting). For example, the device name Test^BName will be saved as TestName.
Here is a list of the control characters that will be replaced with a hexadecimal string if Retain Non-Printing Characters in Device ID and Alias is unselected:
^B, ^D, ^E, ^G, ^N, ^O, ^P, ^Q, ^R, ^S, ^T, ^U, ^W, ^X, ^Y, ^[, ^\, ^], ^F, ^C, ^^, ^A, ^V, ^_
The following table shows examples of control characters and their referenced hexadecimal values:
|
Control Character in Caret Notation |
Symbol Code |
Hexadecimal Code |
|
^F |
ACK("\u0006" ( CTRL+F )) |
 |
|
^C |
ETX("\u0003"(CTRL+C)) |
 |
|
^^ |
RS("\u001e" ( CTRL+~ )) |
 |
|
^A |
SOH("\u0001" ( CTRL+A )) |
 |
|
^V |
SYN("\u0016 " ( CTRL+V )) |
 |
|
^_ |
US("\u001f "( CTRL+? )) |
 |
Changed Behavior of Configuration Option Controlling the Character Replacement
The 2023 R1 release introduced the configuration option Retain Non-Printing Characters in Device ID and Alias (located under System > Configure > Embedded Devices > Host Options). Note the following changes in behavior since the 2023 R1 release:
| • | When Retain Non-Printing Characters in Device ID and Alias is selected: Any control characters in the “Device ID” or “Alias” field are retained when the device is created. This behavior is the same in 2023 R1 through 2025 R1. Customers should note that in this case, if the “Device ID” or “Alias” field contains an invalid character, the Devices page will not load correctly. |
| • | When Retain Non-Printing Characters in Device ID and Alias is unselected: |
| • | Behavior in 2023 R1 and 2024 R1: Control characters in the “Device ID” or “Alias” field are replaced with an empty string. |
| • | Behavior in 2025 R1: Control characters in the “Device ID” or “Alias” field are replaced with their respective hexadecimal values. |
Note that by default, Retain Non-Printing Characters in Device ID and Alias is unselected.