Content Fragments: Multifield support | Community
Skip to main content
R
rogier-oudshoorn
Level 1
October 10, 2023
Investigating

Content Fragments: Multifield support

  • October 10, 2023
  • 2 replies
  • 645 views
Request for Feature Enhancement (RFE) Summary: Add multifield support to content fragments
Use-case: Sometimes, using nested content fragments just makes no sense to editors. Our case: making a cooking recipy. We'd like to break down the recipy into steps necessary to make a meal component (such as: mashed potatoes) including ingredients, and we have no need of reuse. If we'd split off the fragments into a seperate fragment, life for content editors becomes a lot more difficult - it's much easier for them to fill in everything inside of a single fragment view.
Current/Experienced Behavior: No multifield is available in content fragments
Improved/Expected Behavior: We have multifield available in content fragments, including the option to configure them in the model editor
Environment Details (AEM version/service pack, any other specifics if applicable): All versions (but we're on 6.5 on-prem)
Customer-name/Organization name: AmeXio (system integrator)
Screenshot (if applicable):  
Code package (if applicable):  

 

    2 replies

    H
    henryk87
    October 10, 2023

    It's strange anyway, that multifields are there in ClassicUI dialogs, in TouchUI dialogs, but not in AEM Assets properties(?) and not in the content fragment editor.

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    October 12, 2023

    @rogier-oudshoorn 

    Thanks for proposing this idea
     
    This has been reported to the engineering under the internal reference SITES-16566. 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.
    Kautuk Sahni
    Terms & ConditionsAccessibility statement

    Loading footer...