Known Issues
The following describes known issues in the current FlexNet Operations release.
SWM-4175: Invalid Characters Causing Issue in Devices Search
When a search is carried out on the Devices page and a device name contains an invalid character, the Devices page does not load as expected.
The following control characters are not allowed in device names:
^B ^D ^E ^G ^N ^O ^P ^Q ^R ^S ^T ^U ^W ^X ^Y ^[ ^\ ^]
FNO-68308: Parameter “lastModifiedDate” Does Not Consider Timezone
The search parameter lastModifiedDate that is available for the /manageDevice/2.0/devices REST API only considers timezone information in GMT (as in the default request format) included in the search request. The response to a request that includes timezone information in a timezone other than GMT returns “Success” without including relevant device details.
Requests that do not include a timezone return the device information as expected.
SWM-10701: Search Functionality in End-User Portal Erroneously Displays Download Link
In the End-User Portal, users who should be denied access to a file based on their geographical location are able to display the download link for a restricted file when searching for the file name (using the Search function with the Files option on the Download Search page). However, users are not able to download the restricted file.
SWM-6755: Attempts to Export All Entitlements From End-User Portal Unsuccessful
An attempt by a producer user to export all entitlements from the End-User Portal can fail.
SWM-8779: Feature Names With “SERVER” Truncated in Trusted Storage
Feature names containing the string “SERVER” are truncated when the features are activated in trusted storage.
FNO-66018: Errors in UI Updated for Download Package Selection Across Multiple Pages
In 2021.09, the Download Packages window was updated to allow package selection across multiple pages. The following errors currently exist for the updated UI.
| • | Incorrect error message for EULA license on Review & Resolve page |
| • | Search string not properly clearing |
| • | No option to return to full (unfiltered) Download Package list when “failed validation” message displays |
| • | Failed validation error displayed for search results |
| • | Pagination control fields not showing correct information |
| • | Inappropriate message displayed for already downloaded packages |
Incorrect error message for EULA license on Review & Resolve page
When you attempt to download packages that fail validation, the following message is displayed: “Some of the selected packages failed validation. You need to review and resolve the validation errors.” Then, on the Failed Packages window that is displayed if you click the “review and resolve” link in the message, the error for an unaccepted EULA incorrectly shows the following:
“EULA has not been accepted. To accept EULA, click on the Download package ID.”
Instead of “click on the Download Package ID”, the message should instruct the user to “...click ‘I Agree’”.
Search string not properly clearing
After you filter the package list on the Download Packages window, the message “Results for Download package name: <name>” is appropriately displayed. However, if you then click the Clear link at the end of message, the search string used to filter the package list remains, the list remains filtered (even if you move to the next page), and the “Results for the Download package name...” message is still displayed. You must manually delete the search string and click Search to clear the filter.
No option to return to full (unfiltered) Download Package list when “failed validation” message displays
If the “failed validation” message is displayed after you attempt to download packages from a filtered list on the Download Packages window, no mechanism exists to clear the filter to display all packages. You must manually delete the search field contents and click Search.
Failed validation error displayed for search results
After searching for and attempting to download a package containing an unaccepted EULA, the expected message “Some of the selected packages failed validation...” is displayed on the Download Packages window. However, if you then search for a package that does not contain an EULA (but do not attempt to download the package), you received the “failed validation” message instead of the correct message describing the filter results: “Results for Download package name: <name>”.
Pagination control fields not showing correct information
The pagination control fields on the Download Packages window are not displaying the correct totals for a filtered list of packages.
Inappropriate message displayed for already downloaded packages
When you select an entitlement line item whose packages have already been downloaded, the Download Packages window is displayed with incorrect message “Files sent for download. Please monitor the download manager pop up”. The message should be removed altogether or displayed only as package files are being sent to the Download Manager (before the actual Download Manager window is displayed).
SWM-7952: Not All Applicable Download Links Available on “List Downloads” Page in End-User Portal
When end-users are logged in with an activation ID for an entitlement line item that is associated with multiple products, the Downloads page (accessed from Downloads > List Downloads) in the End-User Portal does not always show links to all applicable product downloads.
SWM-7786: SHA2 Checksum Value of Previous File Shown
If a user has provided a file’s expected SHA2 checksum value for an upload and the file image is subsequently deleted, the Upload File page, when opened again, might show the SHA2 checksum value of the previously loaded file image.
FNO-65909: Download Files Not Visible For Self-registered And Trial Users
Download files might not be visible in the End-User Portal for self-registered users and those users registered through the “Try Before You Buy” registration.
FNO-61266: Translation Issues with Localization
Per a previous enhancement in 2020 R3 to add more language support for End-User Portal localization, certain strings—such as alerts and validation messages—are not being translated properly when localization is in effect. These issues will be addressed in an upcoming release.
FNO-60845: Size Limitation For License Models
The JSON definition of a license model and the definition’s internal representation are both stored in the FlexNet Operations database. Neither the JSON definition nor its internal representation can exceed 8000 bytes in length.