Content Fragment Features Update | Community
Skip to main content
V
varuns69729001
September 28, 2020
Accepted

Content Fragment Features Update

  • September 28, 2020
  • 3 replies
  • 1371 views

Content Fragments are now used widely in AEM project majorly in headless and hybrid model.

 

But still there are some features that can be added in content fragment that can make it more valuable:

1) Use of Multifield. Currently the multifield works fine when there is one level of child but for some cases we require multlevel multi field that does not work fine as it works in the component level.

2) Live Copy Inheritance in Content Fragment is not supported.

3) Asset level versioning shows the version number , it should also show the date of version so this will help to track the exact revision as well.

4) Dialog level clientlibs instead of override dam.cq one for dialog level events.

    3 replies

    H
    Adobe Employee
    Hamid1350Adobe Employee
    Adobe Employee
    September 28, 2020

    Hi @varuns69729001 

    Thanks for submitting the Request for Feature Enhancements (RFE). To start I would suggest to divide each request in an individual RFE requests since each request needs to be discussed and pursued separately. So we can keep this RFE for the 1st item in the list.

    Ref: when there is one level of child but for some cases we require multi-level multi field that does not work fine.

    1. Can you clarify how it is not working as expected when using nested multifield in Content Fragment ? e.g. any error, rendering issue, ...etc.
    2. Clarify what components/resourceType is being used for text/dialog/multifield
    3. Please elaborate more to help us understand the "expected behavior" and the "experienced behavior".
    V
    varuns69729001Author
    September 30, 2020

    Hi hamidk92094312,

     

    1) When we use nested multifield, it doesn't load in the dialog. 

    2) Resource Type :granite/ui/components/coral/foundation/form/multifield is used

    3) Expected behavior should be that multifield should work in same manner as it is working in the component.

    H
    Adobe Employee
    Hamid1350Adobe Employee
    Adobe Employee
    December 25, 2020

    Hi @varuns69729001 

    There is an existing request for the same improvement. 

    Ref: CQ-4309204 ... Creating a new nested fragment doesn't update the structure same issue for multi-field. This is scheduled to be part of an Epic release i.e. CQ-4310349, in the first quarter of 2021.

    Terms & ConditionsAccessibility statement

    Loading footer...