Entitlement Management Issues Resolved in 2021.12

The following issues were resolved for entitlement management in the 2021.12 release.

All Lines for New Entitlement Now Listed Whether or Not They Define Values for New Custom Attributes

In previous releases, when a new custom attribute was configured to display as a column on the List Entitlements page in the Producer and End-User portals, an issue could occur when new line items were added to an entitlement. Only those new line items that defined a value for the attribute were displayed on the List Entitlements page and in line-item lists on other pages in both portals. New line items that left the attribute blank were not listed.

This issue is now resolved so that all new line items for an entitlement are displayed, whether or not the custom attribute for a given line item has been set. (A prerequisite for this fix is that the custom attribute must allow only text, date, or number values.)

Note that, to ensure that existing entitlement line items are visible once a new custom attribute is enabled, users need to do either of the following:

•

Make sure the custom attribute for each existing line item has a value set.

•

For those line items that have a null value for the custom attribute, programmatically update the attribute with a dummy value, such as “N/A”.

Information in New Product or Entitlement No Longer Overwriting Information in Other Opened Products and Entitlements

In previous releases, when a producer created and saved a new product or entitlement while an existing product or entitlement was currently open in the same browser session, the information in the new product or entitlement could overwrite information in the corresponding existing entity (as seen when the existing entity was refreshed). The same problem was seen on Bulk Entitlement, Test Entitlement, and Test Bulk Entitlement pages. This had been partially fixed in 2021.10, and has now been fully resolved.