Entitlement Management Issues Resolved in 2024.06
The following issues were resolved for entitlement management in the 2024.06 release.
• | Invalid Characters in Entitlement Emails |
• | Entitlement Updates Now Reflected in Transactions History |
• | Increased Length of Custom Attribute Names for Entitlements |
• | Large Bulk Upgrade Jobs No Longer Failing |
Invalid Characters in Entitlement Emails
In some scenarios, Entitlement emails could contain invalid characters. These appeared 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 or line item description included line breaks.
This issue no longer occurs when sending entitlement emails from the Producer Portal. The [[DESCRIPTION]] merge tag will render the content with line breaks as expected. There will be no invalid characters, and the description will have a multi-line display.
Note:When an entitlement email was sent using web services, the invalid characters can still be observed. This issue has been addressed in the 2024.07 release (see Resolved Issue with Invalid Characters in Entitlement Emails Sent Using Web Services).
Entitlement Updates Now Reflected in Transactions History
Previously, transactions related to entitlements were not captured and therefore not included in the entitlement’s transaction history. This has now been resolved; entitlement updates and transactions related to entitlements are included in the transaction history.
Note:The transaction history for entitlements can be displayed in the following ways:
• | Click Entitlements > List Entitlements by Order. Search for an entitlement and click the entitlement ID. On the Create an Entitlement page, click View Transaction. The Search Transactions: Results page opens and displays the results. |
• | Click System > Transaction History. Under the search criteria, choose Entity Type Entitlement. Enter your search criteria and click Search. The Search Transactions: Results page opens and displays the results. |
Increased Length of Custom Attribute Names for Entitlements
Custom attribute names for entity type Entitlement that are more than 30 characters in length can now be saved. Previously, saving or modifying an entitlement custom attribute whose name exceeded 30 characters failed.
Note:A known issue existed for custom attributes of type Boolean. This has been resolved in the 2024.07 release (see Deselecting Boolean Entitlement Custom Attributes With Names Containing More Than 30 Characters ).
Large Bulk Upgrade Jobs No Longer Failing
Bulk upgrade jobs that contain more than 2200 line items are no longer failing with the error “Transaction failure exception”.
Note:This fix applies only to the upgrade process. A known issue exists for auto-fulfillment of line items during the upgrade (see SWM-15171: Auto-Fulfill Failing During Large Bulk Upgrade Jobs).