Entitlement Management Issues Resolved in 2024.10
The following issues were resolved for entitlement management in the 2024.10 release:
| • | Corrected Wording of Warning Message When Removing Users |
| • | Controlling Behavior When Transferring Entitlements With New Activation ID and Entitlement ID |
| • | Bulk Operations Email Now Includes Entitlement Line Item Custom Attribute Information |
| • | Configuration Option “Show Line Items with Zero Copies by Default” Now Working as Expected |
| • | Transferring Entitlements with Linked Maintenance to New Account |
| • | Changing a Line Item’s Start Date No Longer Updates Its Expiration Date |
| • | Offline License Return Requiring Confirmation |
| • | Resolved Error in License Model Creation Process |
Corrected Wording of Warning Message When Removing Users
When removing an end customer or channel partner from an entitlement, the Producer Portal now displays an appropriate prompt, Do you want to remove the selected account(s)?.
Controlling Behavior When Transferring Entitlements With New Activation ID and Entitlement ID
When transferring an entitlement containing a line item where some line item copies have already been activated and specifying that a new entitlement ID and activation ID are generated, the new account will receive the entitlement with the full amount of line item copies. However, the copies that have previously been activated are still mapped to the previous device and can be used to generate licenses.
To avoid such a scenario, this release introduces a new element to the EntitlementOrderService SOAP web service, called returnRemainingLineItems, and a new configuration option Transfer entitlement with remaining quantity only (under System > Configure > FlexNet Operations > General Options), which help producers control the behavior when transferring entitlements with a new entitlement ID and activation ID to another account.
If the configuration option Transfer entitlement with remaining quantity only is selected, transferring the entitlement with a new entitlement and activation ID will transfer only the number of undeployed line items.
The returnRemainingLineItems setting is used during the transfer of entitlements using SOAP services when the configuration option Transfer entitlement with remaining quantity only is selected. If the configuration is unselected, the returnRemainingLineItems setting has no impact on the transfer process.
| • | When returnRemainingLineItems is enabled (true): During an entitlement transfer, if some line items are already deployed, the remaining undeployed line items will be transferred to the target entitlement. |
Example: Suppose entitlement E1 with activation AC1 has a quantity of 100, and 20 line items have been deployed. If returnRemainingLineItems is enabled, the remaining 80 undeployed line items will be transferred to the target entitlement.
| • | When returnRemainingLineItems is disabled (false): During an entitlement transfer, if some line items are already deployed, an error message will be returned, indicating that the entitlement cannot be transferred because certain line items are already deployed. |
Example: Suppose entitlement E1 with activation AC1 has a quantity of 100, and 20 line items have been deployed. If returnRemainingLineItems is disabled, an error message will be returned as part of the response.
By default, returnRemainingLineItems is set to false.
Bulk Operations Email Now Includes Entitlement Line Item Custom Attribute Information
Entitlement line items that are associated with custom attributes are now displayed as expected in bulk operation notification emails.
Configuration Option “Show Line Items with Zero Copies by Default” Now Working as Expected
In previous releases, the End-User Portal displayed line items with zero copies remaining on the Activatable Items and the Manage Entitlements pages even if the configuration option Show Line Items with Zero Copies by Default was unselected, meaning that such line items should be hidden. This has now been resolved, and the option, if unselected, hides line items that have zero copies remaining.
Transferring Entitlements with Linked Maintenance to New Account
Previously, when transferring an entitlement with a linked maintenance to another account, the linked maintenance was not transferred. Only the entitlement line items for the entitlement were transferred to the new account. This could cause the Product Version Upgrade job to fail.
To address this, release 2024.10 introduces a new configuration Transfer maintenance line items from other entitlements (under System > Configure > FlexNet Operations > General Options). If selected, when transferring an entitlement to another account, any maintenance line items are also transferred, if these maintenance line items are linked to a line item belonging to the entitlement being transferred. If the linked maintenance line item is linked to a different entitlement (that is, not the entitlement that is being transferred), the transfer is not performed and an error message is displayed.
By default, the configuration option is unselected (meaning that only the entitlement line items for the entitlement are transferred to the new account).
Changing a Line Item’s Start Date No Longer Updates Its Expiration Date
When updating a line item’s start date in the Change Start/Expiration Date widget, the line item’s expiration date is no longer erroneously also updated.
Offline License Return Requiring Confirmation
In previous releases, if the configuration option Skip Confirmation or Skip Confirmation for Producer (under System > Configure > Embedded Devices > License Generation) was not selected, the system erroneously did not require confirmation for reducing the number of copies via an offline activation request. The capability response included the following parameter:
{
"confirmationRequestNeeded" : false
}
This issue was addressed in the 2024.10 release. Now, when the option Skip Confirmation or Skip Confirmation for Producer is unselected, and an offline activation file for reducing license counts is uploaded to FlexNet Operations, the capability response that is subsequently generated and loaded into the local license server will show the following:
{
"confirmationRequestNeeded" : true
}
Resolved Error in License Model Creation Process
During license model creation, the setting “Is this a counted model” is now working as expected. This means that if it is set to Yes, a counted license model is created. Previously, even if “Is this a counted model” was set to Yes, the created license model erroneously was uncounted.
Also, the field isCounted in the getLicenseModelIdentifier operation of the ProductPackagingService web service now shows the correct value.