Entitlement Management Issues Resolved

When performing an advanced search on entitlement counts in the FlexNet Operations Producer Portal, the local time zone of the user performing the search is taken into consideration. However, in the previous release, this was different when an entitlement search was performed using Web Services, where the user’s local time zone was not considered. As a result, entitlement search result would differ depending on the search method.

To produce search results that are consistent with those reported through the Producer Portal, customers using Web Services can now use the search parameter lastModifiedDate. This ensures that the user’s time zone is taken into consideration.

Resolved Issue with Entitlement Line Item Creation for Self-Registered Users

Previously, a stack overflow error could be observed when an entitlement line item was created and if the entitlement was associated with a self-registered user. This has now been resolved.

Incorrect Date Conversion for Custom Attributes

An issue could be observed in the FlexNet Operations Producer Portal where custom attributes of type date were converted incorrectly to an earlier date upon saving the associated entitlement or product. This issue only occurred in deployments hosted in AWS.

This has now been resolved.

Line Item’s Last Modified Time No Longer Fails to Update

In the previous release, when a license was removed from a device, the corresponding line item's last modified time was not updated. This issue no longer occurs.

Removal/Unlinking Older Maintenance Line Items from an Entitlement Line Now Possible

Previously, when multiple maintenance line items were linked to a single entitlement line, removing older maintenance line items was not possible without removing the more recent maintenance line items. This issue has now been fixed. Older maintenance line items can be removed/unlinked from the entitlement line.

Disparity Between Mapped License Quantities for the Same “Last Modified” Date

Previously, when users mapped licenses to a device, the last modified timestamp on a line item was updated before the update to the mapped-license quantity was applied. As a result, customers who pulled data from FlexNet Operations (for example, using the getActivatableItemsQuery SOAP method) before the mapped-license quantity was updated would see a stale quantity value corresponding to the last modified date in the response. However, users would then observe the correct mapped-license quantity for that same date in the FlexNet Operations portals.

Now the last modified time on the line item is updated after the change to the mapped license quantity.

Issue with Mapping Over 2100 Activation IDs Addressed

In the previous release, attempts to map more than about 2,100 activation IDs at once to a device would result in an error. This error has now been fixed so that such mappings should complete successfully.

However, users should still apply caution when mapping extremely large numbers of activation IDs in one step. If the number of activation IDs is large, processing can be very slow; and, if the number of IDs is large enough, a timeout can still occur.

Hence, the general recommendation is not to map extremely large numbers of activation IDs in one step. Use an alternate process instead.

All Lines for New Entitlement Now Listed Whether or Not They Define Values for New Custom Attributes

In the previous release, when a new custom attribute was configured to display as a column on the List Entitlements page in the Producer and End-User portals, an issue could occur when new line items were added to an entitlement. Only those new line items that defined a value for the attribute were displayed on the List Entitlements page and in line-item lists on other pages in both portals. New line items that left the attribute blank were not listed.

This issue is now resolved so that all new line items for an entitlement are displayed, whether or not the custom attribute for a given line item has been set. (A prerequisite for this fix is that the custom attribute must allow only text, date, or number values.)

Note that, to ensure that existing entitlement line items are visible once a new custom attribute is enabled, users need to do either of the following:

•

Make sure the custom attribute for each existing line item has a value set.

•

For those line items that have a null value for the custom attribute, programmatically update the attribute with a dummy value, such as “N/A”.

Information in New Product or Entitlement No Longer Overwriting Information in Other Opened Products and Entitlements

In the previous release, when a producer created and saved a new product or entitlement while an existing product or entitlement was currently open in the same browser session, the information in the new product or entitlement could overwrite information in the corresponding existing entity (as seen when the existing entity was refreshed). The same problem was seen on Bulk Entitlement, Test Entitlement, and Test Bulk Entitlement pages. This issue has now been resolved.

Export of All Entitlements From End-User Portal Now Successful

An attempt by a producer user to export all entitlements from the End-User Portal was failing in previous releases. This issue should no longer occur.

“Email Template variation” Field No Longer Resetting Itself During Entitlement Creation

Email Template variation field is no longer resetting itself back to the default Select value whenever users attempt to add channel partners during the entitlement creation process.

Attempts to Transfer an Entitlement Count Back to Its Original Entitlement No Longer Failing

In the previous release, an attempt to transfer a license count for an entitlement line item under certain conditions could fail with the following error message: “The number of copies cannot be set to a number less than the fulfilled amount n.” The error was occurring (both in the Producer and End-User portals and for the transferLineItem Web Services method) even though the count being transferred was currently not fulfilled or mapped to any device. This issue is now resolved.

New Checks in Place to Prevent Concurrent Transfer and Mapping Operations Against the Same Entitlement Line Item

In the previous release, users were allowed to run a license-mapping operation against an entitlement line item while a license transfer was currently in progress against this same line item. The concurrent operations could result in corrupted license counts.

Now, during the transfer of an entitlement line to a different account or entitlement (through either the Producer or End-User Portal or the transferLineItems SOAP request), users are prohibited from mapping/unmapping licenses from the line item to/from a device.

If users attempt to perform a mapping operation during a license transfer that involves the same line item, the following message is displayed in the UI: “A license transfer is in progress for the activation Id <activationId>. Please wait until this has completed.” Additionally, the line item currently being transferred will be unavailable for mapping operations until the transfer is completed.

Changes to Line Items Now Shown on License Server

Previously, in some cases when a line item was updated (for example, to extend an expiration date), the changes to the line item were not displaying on the relevant license server. The situations that caused this issue have now been resolved.

Entitlement Management Issues Resolved

FlexNet Operations 2022 R1 On Premises Release Notes

July 2022