Resolved Issues

Editing a completed entitlement using the PATCH method to add a feature with an SAOT license model resulted in an internal error after associating a license model and saving the entitlement.

Sentinel EMS did not allow the ampersand (&) character in the CC Email fields when creating entitlements.

The date format defaulted to MM/DD/YYYY instead of following regional settings and the browser locale.

The Search License Sessions and Delete License Sessions REST API were not accessible when logging in as a customer using an end user's email.

When configuring license models in an entitlement, the start date and expiration date were not editable for Sentinel LDK products containing Specify at Order Time (SAOT) license models.

The Associated Memory tab displayed different names for the same memory segment on different pages.

The Search Activation API returned a null value for the activatee when logged in as a customer's administrator user, instead of returning all activatees associated with the customer.

On the Edit Channel Partner page, modifying a channel partner user's name twice in the same session was not possible.

On the Edit Channel Partner page, editing a channel partner user from the second page incorrectly opened the edit page for the first user.

The bulk entitlement upload using the REST API failed if the request JSON contained invalid entries, such as an incorrect enforcement name or a missing allowActivationBy key-value pair.

Editing a Sentinel LDK product was not possible if the IsFixed parameter was set to 0 and the product was marked as completed.

The license revocation failed for certain activations when concurrent API requests caused a mismatch in activation quantity.

A product marked for end-of-life was visible while creating a test entitlement.

The earliestStartDate and latestEndDate activation attributes for custom license generators were not set correctly according to the feature’s license attributes.

An appropriate error message was required when a vendor user without a role attempted to log in to Sentinel EMS with SSO enabled.

The end user received multiple activation emails instead of a single email for connected license models.

An internal error occurred when importing products due to an incorrectly formatted import file.

The attempt to renew, rehost, or revoke an activation failed for entitlements with products set to never expire.

A license string was not expected to be available for download for entitlements created for Services enforcement.

Sentinel EMS did not support concurrent requests for the same fingerprint or product when revoking activations.

For legacy cloud-connected license models, the PATCH License Session call returned success for closed line items instead of indicating they were unavailable.

The data export reports did not display the custom attribute value when the same custom attribute was associated with multiple entities.

With the Connected (Cloud LM) mode, an error occurred when updating entitlements with the vendor info attribute set to use a dynamic expression, indicating that the specified expression was either invalid or evaluated to an empty value.

An error occurred during revocation because the entitlement update process did not save the changes to the default license model correctly.

Activation failed for variants if their names included an apostrophe character.

Editing an entitlement resulted in an error when a lease product was added to an entitlement that already included a Connected (Cloud LM) product.

The product import job was displayed as "In Progress" instead of "Completed with Errors" when column headers contained special characters.

The license certificate email displayed an incorrect activation count for versionless products.

The Search Features API endpoint returned an unexpected response when the namespaceName search parameter contained an incorrect value.

The entitlement update using REST API failed with an error indicating that the specified feature must be associated with a product.

Entitlement creation failed if the commonLicenseAttribute was set to a blank value in the API request.

A rate limiting issue was encountered when configuring multiple license models simultaneously during entitlement creation or editing.

The Add Product page of the Sentinel EMS vendor portal did not allow change in the default license model due to a pagination issue.

The response of the Delete API endpoints contained an incorrect content-type.

For Connected (Cloud LM) model, when modifying a completed entitlement and providing LICENSED_USER_ACCOUNT_LIMIT in the input, if the LICENSED_USER_ACCOUNT value was not set, the LICENSED_USER_ACCOUNT_LIMIT was incorrectly set to zero.

An unnecessary delete option was displayed on the Edit Product page of the Sentinel EMS vendor portal.

Sentinel keys were not returned on the Customer Keys tab during activation, when the customer name contained the '+' character.

Creating entitlements with batch entitlement failed when the batch quantity was greater than 1 and a Sentinel LDK product was included.

The customer reports did not return the expected data after migration.

The Sentinel EMS vendor portal did not display Japanese strings correctly, including feature names, product names, and vendor users.

The Configure License Model page did not display the remote desktop field for unlocked products.

Sentinel EMS did not change the state of a migrated product to End of Life if the product was associated with the Time Period license model and the number of days was specified as SAOT (Specify at Order Time) before migration.

After a product containing dynamic memory files was associated with an entitlement, the dynamic memory text from a previous page remained visible when editing the product in the Sentinel EMS Vendor Portal.

The license model list was not visible when configuring features in an entitlement if the product contained SAOT (Specify at Order Time) license models.

For Sentinel LDK Wrapper, a user with the order taker role was unable to create entitlements.

For Sentinel LDK Wrapper, product creation returned an error when adding features with SAOT (Specify at Order Time) license models.

The Upload C2V field displayed an incorrect file name when activating Sentinel LDK products.

The character é in migrated products was not visible on the Sentinel Keys page and ACC after activation.

The Configure License Model dialog box was not displayed at the entitlement level if a product with a feature was associated before associating a product with only memory.

Searching for a specific activation using the EID search parameter returned an error.

Entitlement activations remained in a single state during the simultaneous activation of entitlements created with the Connected (Cloud LM) mode.