Resolved Issues

When updating a cloud-connected entitlement where named user licensing is enabled, if you use the PUT or PATCH API endpoints and set a non-zero value for totalQuantity, the Named User Management tab disappeared from the Sentinel EMS UI, and the activated quantity increased unexpectedly.

The Search Features API endpoint returned an internal error when using comma-separated values in the namespaceId field.

After deleting a test entitlement, the associated customer could not be deleted because the customer’s association with the license grant was not removed as expected.

The available quantity for an entitlement was zero despite having no active activations.

Duplicate activation records were created for the same entitlement.

When a customer logged in to the customer portal, the Activations page did not display Activation Comments under Activation Attributes, unlike when a vendor admin logged in.

Sentinel EMS allowed excluding mandatory features while editing or copying a draft entitlement if the license model was not associated with the feature during product creation.

For the Sentinel Fit enforcement, Sentinel EMS did not save changes to the vendor string value in a feature’s license model during entitlement creation, reverting it to the default value after saving or activation.

The dynamic expression for the customer portal URL configured in the email template did not work when the entitlement was created using the REST API, causing the customer to receive plain text instead of a link in the email.

When an entitlement was saved with the Product Family value set to blank, the system returned an internal error instead of applying the default value.

Updating an entitlement allowed adding features with different license models to the same line item, resulting in mixed license models within a single line item.

When editing a cloud-connected entitlement with named user licensing enabled and a specified number of named users, the license attribute changes were not saved, and the Named User License value was reset to No instead of retaining Yes.

A standard user with customer management roles could not create machine accounts for Default and Sentinel LDK (DEMOMA) market groups.

When editing an entitlement, changing the license model resets the Fingerprint for On-Premises Licenses value from Yes to No, regardless of the entitlement’s state.

The product import returned a success code (201) but failed to create products because the REST API did not recognize the product identifiers.

The JSON user import failed for customers created through the JSON import process but worked correctly for customers created through the Sentinel EMS user interface.

The CSV product import job remained in the “In Progress” status when the input file contained invalid items, rather than completing or failing with an error message.

The Entitlements page in the vendor portal displayed the Partner Name column multiple times.

The custom Sentinel EMS logo did not appear after redirection to the login page when accessing the vendor portal in an incognito browser.

The bulkActivate API endpoint returned an error, with the response contentType incorrectly set to application/xml instead of application/json.

The direct links to Sentinel EMS entities didn't work after the authentication change, returning a 404 error when the redirect URL contained query parameters.

The Configure License Model page in the Sentinel EMS UI showed an incorrect concurrency limit value for the connected license model, displaying Unlimited instead of 1, after saving the entitlement.

When using the Sentinel LDK migration tool, a duplicate entry occurred for the activation entity.

The Update User API returned an error after upgrade due to users having both admin and standard roles during data migration.