Resolved Issues

When importing an entitlement from a JSON file, the createdBy field was incorrectly set to a random numeric value instead of retaining the original value from the file.

When editing a vendor user, an error occurred because the internal search used a like filter, which led to incorrect results when similar user data existed in the system.

The Search Activations API returned incorrect customer data in the response when the customer associated with an entitlement was changed after activation.

After upgrading to version 6.1, the availability (health check) API endpoint did not accept basic authentication with an empty password, resulting in a 401 Unauthorized error.

The PATCH API calls, such as updating a customer with comments, did not record the comments in transaction log.

User could not be deleted after an associated activation was revoked.

Using the Generate Report API for a usage report with EID login credentials and the EID as the password returned a 403 Unauthorized error.

During the import of a CSV file for Download entities, custom attribute values were not populated. If the attribute had no default value, it was omitted entirely. If a default value was set, the import ignored the CSV value and applied the default.

On clicking Send Email on the entitlement certificate, the email was not sent if the associated product contained a feature with a license model that included an expiration date, and the license attributes specified a start date.

The prefix ‘service-account’ was added to the client ID during client credentials authentication, causing the createdBy field to exceed the 50-character limit.

On the Channel Partners page, email search results with emails having leading white spaces in the search input did not appear at the top in the Associated Users tab.

On creating a copy of a product with activation method set to 'Full', the activation method was incorrectly changed to 'Define in Entitlement'.

The Entitlements page displayed incorrect activated quantities.

An incorrect message was shown when Sentinel EMS failed to connect to Self Service.

The entitlement creation failed after configuring a feature by changing the Apply License mode to 'Overwrite'.

On using a custom attribute defined for an entitlement with Data Type set to ‘List’ and the character ‘&’ in Default Value, the default value and duplicate entries did not appear correctly.

Updating an entitlement with a closed line item for the Flexible License Model resulted in an error.

Removed the Default Interval between Start Dates and End Dates property from the Admin Console.

On the Email Templates page, attempts to update an email template intermittently failed.

For Sentinel LDK, some cloud features were missing on the client machine.

Adding features to an existing product failed if the product already had at least seven features. The operation triggered an error and the license model for features on the second page was incorrectly changed.

Slow query response was be observed while activating some entitlements.

Editing an entitlement associated with the Connected license model failed along with the display of an incorrect error message.

An incorrect value appeared instead of the correct Boolean value for the Enabled field in the data export report for a custom entity.

The response of the Search Custom Entity Records API endpoint showed inconsistency in the structure of the attribute field, appearing either as a single object or as an array of objects, depending on the presence of single or multiple attribute objects, respectively.