Hello @satish_puli ,   Thank you for raising the query. For better assistance from the Forms community, please post it here:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-forms/ct-p/adobe-experience-manager-forms-community Hope this helps, and you receive the appropriate g...

Hello @bhushanKare ,   I hope you are doing well!   Given your description (“50+ sites, multi‑theme, multi‑region, API heavy, Angular is the standard”) the answer is: Use AEM as a headless CMS for the core application surfaces, and keep the classic AEM Sites stack in reserve for brand/marketing exp...

Hello @Mailyn_TMo ,   If the solution helped you, please mark it as correct. Otherwise, let me know if you need any further assistance     

Hi @mancillaignAdobe ,   Just saw you posted the query in : https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-forms/aem-forms-core-components-wizard-breaks-the-authoring-ui/td-p/787822Marking the answer as correct.Happy to help 

Hello @salvoo76993234 ,   Thankyou for sharing. As per new process, from now for submitting feature requests, users can now suggest enhancements, such as cross-program content migration, through the Experience League Ideas platform [1]. Product Team will  surely go through and see If they can consid...

Hello @Mailyn_TMo ,   Yes, this is possible. The tiles on the AEM start screen (Sites, Projects, Tools, etc.) are shown/hidden based on Read permissions on their root paths. To show only Assets, remove Read access from all other console paths and keep it only on DAM: --------------------------------...

Hello @mancillaignAdobe ,   If the direction helped you. Kindly mark the answer as correct 

Hello @mancillaignAdobe , It would be better if you could post your query on the Adobe Experience Manager Forms community: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-forms/ct-p/adobe-experience-manager-forms-community   This will help you gain better visibility and mor...

Hello @EduardoMa9 ,   Could you please mark the answer as correct If It helped you.

Hello @Magicr ,   You actually ran into a limitation of the CF Model editor, not something you can “fix” with a config tweak.   - In content fragment models only the top-level field is supported as required (via the Field required checkbox). The editor / validation logic is not built to handle requi...