I faced similar problem in my experience and I had to implement custom logic that I described above. Of course I had to cover all scenarios that are in OOTB logic.Unfortunately, I didn't find any place to extend this logic in more fancy way.If you find it, please share it with us. 

Hi @mahi765183, You can find OOTB logic in the com.day.cq.workflow.impl.email.EMailNotificationService. Unfortunately, there is no room to implement any additional factory or builder that can pre-process email creation. However, there is another trade-off in your case: you can disable all notificati...

I would add that these movements can be stored in the asset metadata as movements multi-value property. So, no need to worry about permissions under var for the service. 

Hi @wizard04wsu, Adobe CQ Form Mail Servlet handles the Mail Action type of Form Container (see implementation in the com.day.cq.wcm.foundation.forms.impl.MailServlet).  Based on its implementation, it can send 2 types of emails:Multi-part email when attachments more than 1: org.apache.commons.mail....

Hi @nkoppul1, To find more appropriate solution we need to know more requirements about MSM support, dynamic components, integration with 3rd parties etc. Based on provided info I can suggest few options:Option #1 - site root is a pageYou are going to have N brands that will reuse same components (w...

Hi @djohn98390536, if you are interesting in the AEM Unit test, you can use my code below. However, I would suggest you to refactor your piece of code firstly, because it could lead to NullPointerException.Refactored code (ResourceResolver#getResource, Resource#adaptTo can return null):import org.ap...