Device Management Issues Resolved
The following issues were resolved for the management of devices in the 2021 R1 release.
| • | Trailing or Leading Spaces in Feature Names No Longer Failing Device Series Updates |
| • | Device Permissions Now Properly Enforced Based on Its Account |
| • | Now Only Electronic Software Delivery License Required for Availability of Downloads Tab for Devices |
| • | Initial Attempt to Self-Register a Device No Longer Failing |
| • | Configuration to Allow or Disallow Registration of Unknown Devices Now Working Properly |
| • | Unknown Device Registration Now Succeeds on First Attempt |
| • | Return of Devices Successful with or without Destination Devices |
| • | Device No Longer Created with Licenses from Two Different Accounts |
| • | Device Searches No Longer Failing |
| • | Improved Loading Time for Devices Page |
| • | Search and Filter Issue for Device Updates Resolved |
Trailing or Leading Spaces in Feature Names No Longer Failing Device Series Updates
Previously, when producers attempted to update a device series for FlexNet Embedded, any trailing or leading spaces around a feature name prevented the series from being updated. Starting in this release, trailing or leading spaces around feature names are ignored during the update process.
Device Permissions Now Properly Enforced Based on Its Account
Previously, a user who belonged to multiple accounts—one or more of which had full device-management permissions—would have full device-management permissions on devices that belonged to any of these accounts, even those accounts in which the user had no or limited device-management permissions.
A new configuration option in the Producer Portal, System > Configure > End-User Portal Setup > Devices Page > Enforce device management permission across accounts, now enforces device management permissions across all accounts in the End-User Portal. When the option is selected, all devices are listed on the Devices page (as in previous release), no matter the account with which a given device is associated. However, when a device link is clicked, the capabilities available on the Device Details page are based on the specific account to which the device belongs. Consequently, if a user belongs to multiple accounts, the user’s device-management permissions are now determined on an account-by-account basis, depending on the account with which the currently selected device is associated. If a user lacks permissions to return or generate licenses, but can otherwise edit a device, these specific restrictions are also enforced strictly for each account.
By default, this option is unselected so that the previous behavior remains in effect.
Now Only Electronic Software Delivery License Required for Availability of Downloads Tab for Devices
The Downloads tab is visible on the Device Details page for a standalone device in the End-User Portal as long as the end user has an Electronic Software Delivery license (and the Administrator has set the appropriate System Configuration options for the End-User Portal). Previously, the visibility of this tab was erroneously dependent on an Updates and Insights license as well.
Initial Attempt to Self-Register a Device No Longer Failing
Previously, when an unknown device attempted to register using an activation ID for an entitlement owned by only a partner account, the first capability request failed with the message: “The activation ID was denied.” Consequently, the device was not able to self-register. However, a subsequent request would then succeed, and the device was ultimately registered.
This issue has been resolved so that device registration succeeds with the first registration request.
Configuration to Allow or Disallow Registration of Unknown Devices Now Working Properly
The Allow Adding Unknown Hosts and Allow Server Without Activation IDs system configuration settings are now working correctly to ensure that unknown standalone and server devices can be properly registered or disallowed registration depending on this configuration. Additionally, appropriate error messages are now displayed when registration is denied.
Unknown Device Registration Now Succeeds on First Attempt
Previously, the first capability request sent by an unknown device was denied if that device was attempting to self-register with an activation ID for an entitlement owned by a partner account only. The self-registration failed, showing the following error in the capability request: The activation ID was denied. However, a subsequent capability request would succeed.
This issue has been resolved so that device registration succeeds with the initial registration request.
Return of Devices Successful with or without Destination Devices
The Return Device feature now supports the return of devices with or without a destination device ID. Previously, device returns were erroneously requiring a destination device.
Device No Longer Created with Licenses from Two Different Accounts
Previously, when a capability request was sent containing activation IDs for two or more different accounts, a device was created with licenses from all accounts. Now, when such a capability request is sent, it is rejected. However, the request is accepted if it has one or more activation IDs for the same account.
Device Searches No Longer Failing
Previously, if an illegal character was present in the device dictionary, an attempt to view details on the View Device or View Server page for a selected device failed. This issue has been resolved.
Improved Loading Time for Devices Page
Changes have been applied to improve the time required to load the Devices page.
Search and Filter Issue for Device Updates Resolved
The search and filter functionality on the Device Updates tab in the End-User portal is now working properly. Previously, when using this functionality, users received a gateway timeout error.