Hi @fulongt37334138 , You can have multiple repositories in Cloud Manager Git.https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/managing-code/cloud-manager-repositories.html?lang=en  The real trick here is the deployment, with every Clo...

Hi @rohand59035224 , Page diff comparison will only work for the components which have valid cq:editConfig nodes. Can you check if it's missing in your case? We've fixed the documentation in past and It's also mentioned here:-https://experienceleague.adobe.com/docs/experience-manager-65/developing/i...

Hi @Sean-McK , If they don't have a Nexus repo, you can take the following approach.Make the project as a submodule of this parent project either by adding the whole module or using the git submodule, this way the dependencies will be built and shipped with the deployment.As a workaround, You can co...

Hi @Sb2512 , If you know the property field where you need to search then you can form your query like this SELECT * FROM [nt:base] AS s WHERE ISDESCENDANTNODE([<path>]) and s.[jcr:title] like '%97%\%' Hope this helps! Regards,Nitesh

Hi @varaprasadande1  As it's related to AEM Forms, For better answers please post this question to the AEM Forms community.https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-forms/ct-p/adobe-experience-manager-forms-community Regards,Nitesh

Hi @Abhishekty , Currently, drag and drop is not supported. There is something on the roadmap, but currently, there are no timelines for it. In Franklin projects, there are two ways how you can use AEM Assets or other existing digital asset management solutions,(a) by referencing assets by URL into ...

Hi @nandan123 ,   Looks like you are trying to inject an OSGi service into the sling model. You need to use @OSGiService annotation instead of @Reference.   Check the documentation here:- https://sling.apache.org/documentation/bundles/models.html  https://sling.apache.org/apidocs/sling8/org/apache/s...

  I see, then there are two options:   1.) Change /welcome.html to something else (if possible) 2.) Since it's a reserved path for the AEM Cloud application, that's why it doesn't get logged. I would advise you to open a support ticket so that engineering can assist you with that.

Hi @jpwtt ,   It's the default rewrite to block access to /welcome which used to be home for the classic UI home screen of AEM. Since AEM cloud doesn't support it, that's why you see this error.   You can add a rewrite rule in your apache configuration to rewrite /welcome -> /content/<yourapplicatio...

Hi @Himanshu_Jain ,   AFAIK, docker is the recommended way, as it takes out all the manual tasks we had to perform with the old approach.   In this case, you can try the older approach of setting up the webserver/dispatcher locally, I haven't seen such use cases for cloud customers very often, which...