Entitlement Management Issues Resolved in 2024.07
The following issues were resolved for entitlement management in the 2024.07 release.
| • | Product and Line Item Description in Email No Longer Showing “<br>” Instead of Line Breaks |
| • | Resolved Issue with Invalid Characters in Entitlement Emails Sent Using Web Services |
| • | Deselecting Boolean Entitlement Custom Attributes With Names Containing More Than 30 Characters |
| • | Displaying License Issue Date in UTC |
Product and Line Item Description in Email No Longer Showing “<br>” Instead of Line Breaks
When using the Producer Portal for sending an entitlement email for a product with multiple line items, the line items are now presented on separate lines. Previously, they were erroneously presented in a continuous paragraph, where the line breaks were indicated by <br>.
Resolved Issue with Invalid Characters in Entitlement Emails Sent Using Web Services
When entitlement emails are sent using the web service operation emailEntitlement and the product description contains any line breaks, these line breaks are now reflected as expected in the line item description. In previous releases, line breaks could be rendered as invalid characters when the HTML Content section (in the Email Template Content section of the Entitlement Email template) contained the [[DESCRIPTION]] merge tag and if the relevant product description included line breaks.
In the 2024.07 release, line breaks are now reflected as expected in the line item description.
Deselecting Boolean Entitlement Custom Attributes With Names Containing More Than 30 Characters
Previously, during entitlement creation, certain custom attributes could not be deselected once the entitlement had been saved. This issue occurred for custom attributes that matched the following criteria:
| • | Name contains more than 30 characters |
| • | Entity type Entitlement |
| • | Type Boolean |
The issue only occurred when creating and saving an entitlement in the Producer Portal. It did not occur when using web services or the Data Import Template.
This issue has now been resolved.
Displaying License Issue Date in UTC
By default, the issue date that is returned by the /features endpoint is always calculated in Pacific Time. In certain scenarios, this can result in mismatched dates for issued and receivedTime in the /features endpoint response.
To avoid these mismatched dates, this release introduces a new configuration Use UTC timezone for license issue date (under System > Configure > Embedded Devices > Host Options). When the configuration is selected, the issue date of a license is displayed in Coordinated Universal Time (UTC).