- v1.0.0-latest-prod
Boolean fields in content model now have a default value option.
Implemented enhancement to display the Content Model Base URI value alongside its own URI when creating and viewing a Content Item.
Updated Content Field Enum options to be orderable.
Added ENUM type to possible ContentField types.
Refactored Content cache invalidation to use current standards.
Introduced support for Recommendation Engine Services via Content Item fields.
Added validation to prevent deletion of the content model if it has Content Items.
Fix for content cloning where cloned content promotion can leave some of its parts not promoted
Folders are now sorted alphabetically by default.
Fix for deleted content model fields being saved in deprecated JPA field which causes them to still be displayed.
Fixed issue where a cloned Content Item and its fields are in separate Change Summary groups, and so are promoted separately.
Fixed issue where the tracking data change container ID for an embedded cloned Content Item is not the same change container as the parent Content Item.
Fixed issue where Change Summaries for Content Items embedded in a reusable item were being lost.
Fixed issue where cache was not was being invalidated for updated Content Items when configured to do so.
Fixed issue where cache was not was being invalidated for updated child/embedded Content Items when configured to do so.
Fixed issue where a null Content Model URI caused a handling exception in displaying the Content Model Base URI value alongside its own URI in the Content Item form.
Fixed issue where Bulk Requests become much slower when previewing because cache is disabled.
Fixed issue where Content Items load slowly due to hydrating when reading Content Items in folders.
Fixed issue where previewing Bulk Requests return inaccurate results due to caching — fixed by accounting for the presence of a preview token in Content Item hydration.
Fixed issue where Content Item hydration is not returned from calling the paged method.
Fixed issue where Content Model ENUM type fields do not require Labels and cause errors in places of usage where label is expected.