Investigating
Allow nested folder browsing in AEM Content Fragment Model console
| Request for Feature Enhancement (RFE) Summary: | Enhance the Content Fragment Models (CFM) console to support folder navigation and organization of models within nested folder structures. |
| Use-case: | Authors and developers often need to organize multiple Content Fragment Models logically (e.g., by business domain, content type, or project) under nested folders within the configuration structure. Supporting folder navigation in the CFM console would help teams manage large sets of models more efficiently and maintain a cleaner, more intuitive structure aligned with their business taxonomy. |
| Current/Experienced Behavior: | Although it is possible to create nested folders for models using CRXDE or the repository directly, the CFM console UI currently displays only the models located within the root configuration folder. Users cannot navigate into subfolders, which results in all models being listed together without hierarchical grouping. |
| Improved/Expected Behavior: | The Content Fragment Models console should allow navigation through nested folder structures under the configuration path. This enhancement would let users browse, create, and manage models within organized subfolders, improving model discoverability and aligning with how other AEM consoles (like Assets or Sites) handle hierarchical structures. |
| Environment Details (AEM version/service pack, any other specifics if applicable): | Reproducible on AEM 6.5 and AEMasCS |
| Customer-name/Organization name: | |
| Screenshot (if applicable): | |
| Code package (if applicable): |