@SDusane  Did you find any solution?If you have ACS Commons, then you can try this tool for purging of Workflow instances.https://adobe-consulting-services.github.io/acs-aem-commons/features/workflow-remover/index.html  

I could not replicate the case on my local SDK. Did you raise ticket at Adobe support? @saicharanm35831 

@chandrakanthim If you are using AEM Forms, you can refer below link :https://experienceleague.adobe.com/docs/experience-manager-learn/forms/handling-af-form-submissions/sending-email-on-adaptive-form-submission.html?lang=en Else you can follow similar approach to send mail :https://www.tothenew.com...

@chandrakanthim You can embed package in your project so that it will get deployed with your code.Go to all/pom.xml<embedded> <groupId>GROUP ID</groupId> <artifactId>ARTIFACT ID</artifactId> <type>zip</type> <target>/apps/your-project/container/install</target> <filter>true</filt...

@SDusane  please share during which operation you are getting this error? Is it when you are opening DAM or running a workflow?

Hi @S28853,   No its not supported. Please find below screenshot for reference. You can download the package of older version documents as an AEM package from here https://experienceleague.adobe.com/docs/experience-manager-release-information/aem-release-updates/previous-updates/aem-previous-version...

Hi @Mario248 : Warnings looks valid as nt:folder node is not allowed to have property like jcr:title. Please remove the invalid properties from .content.xml and build would work fine. Please refer this screenshot on how warning is coming if I manually try to add property jcr:title on nt:folder node...

Spell Check plugin helps you detect the spelling mistakes or the word which are not available in dictionary at location : /libs/cq/spellchecker/dictionaries You can create a custom plugin for your requirement by writing servlet that can help adding/updating the existing dictionary. https://www.bou...

Hi @saravana_sgws    Looks like Async APIs are Adobe internal APIs and you can not use same. I used Java Decompiler to check how Async jobs are created. This is the class Adobe has used to extend to write Async Job :  com.adobe.granite.jobs.async.commons.AbstractAsyncJobExecutor But there is not muc...

The error is related to scene7 and Asset's Scene7 ID is not available. Can you please check if this asset is uploaded properly in Scene7? Is there any configuration related to Scene7 which is updated recently. Please check the assets which are getting downloaded are also synced to Scene7.