Entitlement Management Issues Resolved in 2022.02

The following issues were resolved for entitlement management in the 2022.02 release.

Advanced Search of Accounts by Custom Attributes No Longer Failing During Bulk Upgrade Setup

In previous releases, during the configuration of an entitlement Bulk Upgrade operation, attempts to use a custom attribute as a criterion to perform an Advanced Search on accounts would fail with an application error. This issue is now fixed so that using a custom attribute to search accounts no longer fails during the Bulk Upgrade setup.

Note that a related known issue still existed in 2022.02 when setting up a Bulk Renewal operation. This has been fixed in 2022.03 (see Resolved Issue with Advanced Search Using Custom Attributes in Bulk Renewal).

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 2022.01 and earlier, 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.