Update metadata to support ability to build content zone rules that target the user’s cart
Add a JSON payload form to Content Model
Fixed an issue where the Content Item update form metadata was missing a preview path template.
Fixed content rules targeting Cart Item Names and Cart Offer Codes
Fixed key duplication error when a field with same name is added in the inherited Profile first, then the Parent Profile.
Fixed error in similar case but when Content Fields have different names.
ContentFields
are stored as a collection on the ContentModel domain and so are overridden all together: When one ContentField
is added at the Application level, the whole collection is overridden, so any new fields added at the Tenant level will not be present on the ContentModel
at the Application level. This caused a UI error because no matching ContentField
was found for a FieldData
since the new Field was added at the Tenant level after an override was made at the Application level.
The fix is to simply hide the FieldData
if it has no matching ContentField
in the Admin UI.
This is a temporary measure to simply get users around the error.
See DefautlContentItemHydrationService#handleMissingContentFields
to override behavior