Resolved Issues
Release: 6.0
The following issues are resolved in the Sentinel EMS 6.0 release:
Ref. # | Description |
---|---|
SM-171004 |
Vendor users could not view transaction logs for an entitlement that included a product with multiple features and custom attributes in the vendor portal. Audit logs did not accurately capture data when modifications were made to configure license model attributes or include/exclude specific features. |
SM-171767 | After migrating from Sentinel LDK-EMS to Sentinel EMS, vendor users assigned with Super User and Batch Code Admin roles encountered logout and permissions denial when attempting to edit an existing product. |
SM-169385 | A Sentinel LDK entitlement was not activated after excluding a feature in which license model was set to 'Define in Entitlement'. |
SM-168601 | When updating an activation using the push key method for Services enforcement, the license certificate received by emails started with extra empty lines after using the Reprint option. |
SM-168699 |
The Import feature failed to import downloads due to typos in the headers of the input file. |
SM-170713 | Performance issues were encountered when editing or saving list-type custom attributes. |
SM-170698 | After migrating from Sentinel LDK-EMS to Sentinel EMS, memory values were not correctly overwritten. Only a few characters were replaced instead of the complete overwrite. |
SM-169182 | An error occurred if the total sum of the text length and offset of the default memory exceeds 12 bytes. |
SM-168865 |
For versionless products, if the entitlement state was not included in the request payload, the total quantity was not updated. |
SM-168418 | When creating an entitlement with the 'Copy From Line Item' option enabled, on setting the line item date to one day, the date was set to two days. |
SM-168280 | For flexible license models, the GET and SEARCH calls returned a different list of license model attributes. |
SM-168196 | During migration, the product state was not updated to End of Life. |
SM-168157 | An error occurred when modifying a role if the role name contained the slash (/) character. |
SM-168071 | The Generate button disappeared when generating reports. |
SM-167792 | The PUT call failed to update cloud-connected entitlements due to an incorrect date format. |
SM-167723 |
When creating or updating an entitlement in the vendor portal, line items' dates in the 'Associated Products page / Product Suites' pane, were displayed incorrectly on switching from the first page to the next page. |
SM-167668 | The entitlement update failed if the entitlement contained products with expired features. |
SM-167335 | Activation through the customer portal did not save the custom attribute values for Sentinel LDK entitlements. |
SM-167287 | An error occurred in updating the external ID when migrating products from Sentinel LDK-EMS to Sentinel EMS. |
SM-166723 | The Add Product Key API endpoint did not allow adding a product if the EID was in draft, disabled or closed state. |
SM-166625 | When creating an entitlement from the vendor portal, the Enforcement Extension section did not reflect product-level modifications for the Flexible license model. |
SM-166624 | In the vendor portal, removing a fingerprint from an entitlement did not remove the correct fingerprint. |
SM-166608 | The VM Detection option was not expected to be visible for Cloud LM deployments in the vendor portal. |
SM-166351 | In the vendor portal, unexpected characters were visible on configuring columns. |
SM-165790 | The vendor portal did not allow configuring the number of named user for cloud-connected license models. |
SM-163545 | The standalone node locked license was treated as a leased license. |
SM-160297 | The system was unable to produce and push for the existing key when updating the expiration date while setting concurrency value to 0 and apply type to Add. |
SM-171154 | In a mixed enforcement case where both Sentinel LDK and third-party exist, an error was encountered while viewing products of a third-party entitlement having single-attribute license model. |
SM-170822 | The Provisioning Associations page failed to retrieve details of a product in which external ID value was specified. |
SM-172104 |
When creating an entitlement with REST API, unexpected custom attributes were added to the product key. |
SM-171724 | The vendor portal did not function as expected when saving an updated channel partner with a large number of channel partner users. |