We are not able to cancel inheritance of certain parts of a content fragment. This makes our authors' output three times slower on content fragments. And it increases the risk of human error/inconsistency significantly.
Use-case:
A multilingual setup where Content Fragments are used in Assets. These Content Fragments each have a Blueprint (en) and have Live Copies, for each language we use (e.g.: nl, fr, de). And each Blueprint Content Fragment, consequently each Live Copy, contains language-specific content and language-agnostic content.
Current/Experienced Behavior:
Creating Live Copies with synchronization works fine. However, upon synchronization, the Blueprint Content Fragment overwrites the Live Copies entirely. This problem makes the synchronization of Content Fragments with both language specific and language-agnostic content obsolete. The synchronization can only be used safely for the initial creation of the Live Copies. As soon as an Author puts language-specific content in a Live Copy, synchronization (intended for language agnostic content) is no longer possible, because the synchronization will overwrite the language-specific content with content from the Blueprint.
The inability to use synchronization on Content Fragments with both language-specific and language-agnostic content is large. It essentially means Authors need to repeat the same change in the Blueprint and each Live Copy individually.
Improved/Expected Behavior:
Ability to cancel the inheritance on each field inside a Content Fragment. When an Author does a roll out of the Blueprint Content Fragment, the fields with canceled inheritance (language-specific fields, such as descriptions or titles) are not overwritten.
Environment Details (AEM version/service pack, any other specifics if applicable):
This request has been raised to the product team via the Jira SITES-3741. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.
