@muskan_mala - This is not an error. The execution is outputting default message. It is the same message even I am getting while I am starting my AEM instance - ref. [1]   Is your instance running up after a few minute or so? It generally opens up at localhost followed by port number (default is 450...

@Omkar_Phadtare - I don't think it is a good practise to move the default workspace of XF or Forms. In case of AEM Screens, most likely changing the workspace from /content/screens to something else won't work because AEM channels are coupled with screen player (application) and there would be paths...

@sriram_1 - Is there any specific error you are facing while programmatically accessing AEMaaCS using Service Credentials? Also, where exactly the error is seen?   1. Calling AEM Cloud for JWT? or 2. Calling AEM Cloud for access token using JWT?   Please check this link as well on how to connect usi...

We have single AEM Cloud Program and we have a requirement to have 2 projects (multi-brand) with site-a and site-b. Both the sites would have some common components, services and few distinct as well. Since AEM Cloud deployment is a docker image based, what is the recommended approach where differen...

@Prashardan - If this sitemap components are not supposed to be migrated to AEMaaCS then it can be ignored from the report. If they are supposed to be migrated, then these needs to be mordernized using Touch UI dialog. https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/...

@SupportMember - I had used SPA editor in my previous project. You can refer this document for more details. Also there is a WKND SPA project which you can use to play around SPA editor - https://experienceleague.adobe.com/docs/experience-manager-learn/sites/spa-editor/spa-editor-framework-feature-v...

@rajmishra10 - Could you please list the details of this problem along with DM component path?

@mmouraam - Please check your context hub configurations and segments. This generally occurs if some of the pre-requisites are missing.Once the context hub configurations and segments are created, you need to enable them from page properties, after which you will see them appear in page.Please refer...

@KittisakNontabu - https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/overview/introduction.html