Content Fragment Features Update

Avatar

Avatar

varuns69729001

Avatar

varuns69729001

varuns69729001

28-09-2020

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.

AEM content fragments
2 Comments (2 New)
2 Comments

Avatar

Avatar

hamidk92094312

Employee

Avatar

hamidk92094312

Employee

hamidk92094312
Employee

28-09-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".
Status changed to: New

Avatar

Avatar

varuns69729001

Avatar

varuns69729001

varuns69729001

30-09-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.