Hi @Manasi29 -When you submit a dialog, the properties entered into the dialog will be saved to that particular component using a POST call to the specific component path on the page. You can observe this in the Network tab of your browser Dev tools.Additionally, all clientlibs that have been marked...

Hi @nithindasyam - The path in your error is '/libs/cq/flow', and if you navigate to that particular path in AEM you would find that it belongs to the type 'granite:InternalArea', which by definition from Adobe docs can't be used directly.Internal (granite:InternalArea) - Defines a node as internal....

Hi @Robert-Harper -If you want to save the email in the AEM DAM - 1. Can create a custom servlet that accepts an email message and its attachments as input and upload into DAM programmatically. The email and attachments can be uploaded to DAM individually and a reference can be established by saving...

Hi @kevingtan - Have you verified if the tag 'articles:drama' is published and/or is available in the publisher?

Hi @mrudul - What are the values that you are trying to read from the environment variables? Do they vary per AEM's environment like DEV, QA, Stage and Prod? If yes, any reason why runmodes don't fit into your requirement? Thanks,Fani

Hi @webdev91 - Your resource mapping configurations might be removing the /content from your src path.It looks like you have been testing this on language-masters copy of the page and for this to work you also need rules to support pointing /language-masters to its respective /content/~/language-mas...

@SantoshSai - Not necessarily. We encountered similar issues on non-SPA projects as well and fixed them by removing or correcting the file.

Hi @Pseuplex - Looks like you have a transient workflow running that is throwing an exception during an email send, and they don't leave a footprint to purge the running workflow instances.You can proceed by looking for the transient workflows available in your instance, start them one by one and ve...

Hi @SyamKowshik - This is a known issue due to the presence of a repoinit config file in the project deployed, resulting in a repository initialization error causing HTTP 503 on AEMs. To fix this, either remove the Repoinit file from the configs if not using or replace it with a org.apache.sling.jcr...

Hi @webdev91 - For determining the content structure, it is recommended to also factor in the end site urls. So to better assist you, please share the expected urls for India and US sites? Else, to simply start with you can use something like below and map/modify it against other factors like End si...