Hi @varun790 Please elaborate more about the usecase.However, If you mean to use mbox of target based on clicking of a button, You can call delivery API from the backend to get mbox JSON response and accordingly show UI.Regards,Arpit Varshney
Hey @sanketd27011989 Have you made sure to set this variable before calling send() method?You can see the snippet here for your reference: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/messagegatewayservice/m-p/252196 Regards,Arpit Varshney
Hey @sanketd27011989 In the screenshot, I don't see any email in the field "From address". Have you tried putting some email there and triggering your functionality? I think that email would pick in your "From" in the email. Regards,Arpit Varshney
Hi @Dinu_Arya Is the loggedin user has appropriate permission to create dam assets. Can you try using admin account and check? Also, please check error logs and share if you see any error? Regards,Arpit Varshney
Hi @Dinu_Arya Can you add the below code after assetMgr.createAsset() method:resourceResolver.commit();This will persist your changes.You can see the adobe documentation here: https://www.adobe.io/experience-manager/reference-materials/6-5/javadoc/org/apache/sling/api/resource/ResourceResolver.html...
Hi @aem-explorer Please go through the blog https://helpx.adobe.com/in/experience-manager/6-3/sites/developing/using/extending-msm.html to get better understanding of creating custom rollout config, You can try creating custom rollout config as suggested by @arunpatidar and add targetActivate as s...
Hi @Sachindey11 If you are working on your local machine and have created a sling servlet to make post request to local AEM Server , you may be getting 403 Error Code : ForbiddenThis issue is due to CSRF Filter blocking POST Requests.You can unblock this via OSGi Configuration. You shouldn't be doin...
Hi @keshav_goud It seems to be a workflow launcher that has been triggered after modification.But before assuming anything, please set your log level as debug in your local and try to replicate the mentioned scenario and validate the logs if you find anything useful. Regards,Arpit
Hi @ClintLundmark We must configure the production environment with -nosamplecontent run mode which by default disable the bundles and the idea behind that if they are disabled then the AEM user can't see any hierarchy in the crx/de console which makes sense for production environment so that nobod...