Hi @Mahesh_Gunaje, AFAIK classic AEM multifield with more than one input field is not possible in the new CF editor. In AEMaaCS you can still use the old CF editor, where it is possible, but that's probably not a good long-term strategy. There are a few extension points available for the new CF edit...

Hi @pm31415,I would very much advise against the approach of storing user-generated data in AEM/JCR. A proper solution for your use-case would be to set up an external database and serverless APIs in AWS/Azure. If you don't have a lot of data and you can clean it up periodically, then it won't be ex...

Hi @SuneethaKo,I suggest you create a dedicated Maven module for each sub-project and include it in a single Git repository. This will enable you to deploy all or just one module. This setup works on both AEM 6.5 and AEMaaCS in case you plan to move to the cloud later. You will need to move some cod...

Hi @dylanmccurry,we actually built a tool for doing exactly that kind of content updates, I will check if we can open source when I find some time.However, in the lack of a proper tool, I would perform such actions using a script. My preference for building reusable scripts is Node.js/JavaScript (bu...

Request for Feature Enhancement (RFE) Summary:Ability to use "granite:class" and "granite:data" in the new CF editorUse-case: We developed a show/hide fields plugin for the new CF editor based on a type selection made in a select field. For this purpose we used the example provivided in the docs: ht...

Thanks @sarav_prakash, based on your answer and my findings so far I will:Put all plugins in a single repo, since they cannot be loaded separately per content fragment model, it doesn't make sense to split themTry to include Typescript and change generated files from JS to TSXWill also open a few fe...

Hi everyone,I started working on a few extensions/plugins for the new CF Editor, such as showing/hiding fields based on a selection, custom color picker field, custom autocomplete field, etc. Following the docs provided here https://developer.adobe.com/uix/docs/services/aem-cf-editor/code-generation...

Hi @manish2v1,I don't think picking one specific sourcetype is supported in the YAML configuration. According to the docs: "The sourcetype field will have one of the following values, depending on the specific log: aemaccess, aemerror, aemrequest, aemdispatcher, aemhttpdaccess, aemhttpderror, aemcdn...

Hi @SarahBo2,in the old CF editor, it is possible with a custom multifield. However, I haven't yet seen a solution for it for the new CF editor. It looks like Adobe is moving away from this approach and suggests creating separate CFs for such use-cases. Good luck,Daniel