@vkarthick  Add below dependencies in all pom.xml file (Version can be any your preffered one)<dependency> <groupId>com.itextpdf</groupId> <artifactId>itextpdf</artifactId> <version>5.5.13</version></dependency>And also embed the depedency as below  <embedded> <groupId>com.itextpdf</grou...

@SupportMember  Hope below links help you https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/pagination-using-content-fragment-list-component/m-p/361226 but how every you can use GraphQL API for use with Content Fragments https://experienceleague.adobe.com/docs/experience-mana...

Need more details on the API @Hote1970  what is this API for and what is the expectation 

@Vani1012  Can you please explain the usercase properly. But for review the content "Preview" should be suffient. But it all depends on the usecase 

Hi @chandrakanthim  Can you check below URL.  https://experienceleague.adobe.com/docs/experience-manager-learn/forms/handling-af-form-submissions/sending-email-on-adaptive-form-submission.html?lang=en 

@vkarthick From the error we see clearly that while building the project it is taking "classic" profile which is not supported in AEMaaCS. So make sure you delete it from the maven pom.xml file. And in first place i am not sure why 'classic' will be created as part of the latest archetypeVersion. Yo...

@vkarthick  Are you getting any error when you try including static templates in /apps/ ? 

@fulongt37334138  Once refer to the below URL's. You will get some idea  https://experienceleague.adobe.com/docs/experience-manager-learn/assets/deployment/multitenancy-concurrent-article-understand.html?lang=en https://www.comwrap.com/en/blog/multi-tenancy-with-adobe-cloud-manager.html 

@fulongt37334138  No from my knowledge.  But a way where you can use separate environments for the repo's you can. But you can not have 2 repo's in 1 environment. 

@fulongt37334138 It is not recommended to have multiple repo in adobe cloud. Rather you can have one single repo and have multiple tenants in the single repo. We are currently using the same structure. Below will be the structure Tenant 1Tenant 2DispatcherParent pom.xml