@aem-enthu27  1) Use below link to understand rewrite rule basics :httpd.apache.org/docs/2.4/rewrite/intro.html 2) Dispatcher debugging :blogs.perficient.com/2017/10/12/mastering-aem-dispatcher-part-1-debugging-the-dispatcher/ 3) Dispatcher configuration :experienceleague.adobe.com/docs/experience-m...

@santhoshm687661 Please click on three dots , you must be getting that option :  Thanks,Pallavi Shukla

Can you provide request/access logs - are you getting any 403 ? Moreover is there anything you might need to whitelist in the Referrer filer settings? https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-configure-apache-sling-referrer-filter-to-mitigate-the/m-p/299707

Use below page to find out the associated client of Adobe under various categorieshttps://solutionpartners.adobe.com/s/directory/?solution=campaign

Are you able to whitelist your servlet path in publishers.

@rohitk81560102 wrote:Does AEM as a cloud service support static templates (use cases where due to some limitations where it is not possible to migrate static templates to editable templates).Static Template design information that is stored in /apps can’t be edited via UI.It is recommended that you...

are you supplying the correct dialog path to the tool? Can you please give the screenshot. I didnt find such issue with this version.

Its a known bug - just delete the node manually once which is throwing error, reintall the package and you would be good It is happening  because the tool node type should be unstructured.

I think you can use 1.0.0  aem modernization tool version which works perfectly fine with 6.5.11 aem version if dialog conversion is the end goal.https://github.com/adobe/aem-modernize-tools/tree/aem-modernize-tools-1.0.0 

hi @Mshajiahmed We are using 6.5.11 and we downloaded modernization tool from software downloads. It is working perfectly fine for us for all conversions including dialog too.Please let me know whats error you are getting when you try using dialog conversion.