@dsomya  Yes the export would give an error with auto-created IDs for deliveries and workflows. Though if you change it to some different format, export should work fine. What is the new ID provided? Please share the package export logs.You can try making changes to the elements in export elements a...

This looks like some syntax error in content (missing open or close tag). You can click on <> to see source and check the syntax. Does it go away if you remove the advanced condition?

Okay I overlooked your question and interpreted it for recipient's name. I would have suggested to create a control type topology rule similar to 'Check Subject' rule (var strSender = emailContent.senderName.source;strSender.startsWith("abc");) but unfortunately there's no provision to edit existing...

Screenshot would definitely help to understand the issue better, you might not be able to add it while adding the comment but you can edit the comment and then add it. You might want to look at the source in the designer and try removing the extra code from there

@ramon_bisswanger - Got it, I left the selection as "Using Reconciliation Criteria". Changing it to "Directly using Targeting Dimension" works."

@michellelowsl  I would suggest to do that filtering in the 'Target' section of the delivery itself using General > Profile (attributes). Same can be achieved in the Query activity if using a workflow.  

@AndrewKriz  I don't think the 'client' dimension is available oob and there isn't any straightforward way to implement a custom dimension. There's a possibility for you to capture the email client information at the user profile level and then have that available in reports. Refer this link: https:...

@adobecq-venkat  You would also have to export that dependency under <export-package> section of the pom.xmlA similar issue with a different 3rd party jar/ bundle inclusion is mentioned here: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-maven-build-cannot-resolve-dep...

@binoypIt is possible that the assets have not been indexed and so will not be available in asset finder. Please try running reindex on damAssetLucene either through Tools > Operations > Diagnosis > Index Manager > damAssetLucene or through crxde search for damAssetLucene node under oak:index and se...

@ravi_shankerj14  To be able to allow a new html attribute in richtext sourceedit, whitelisting it in the xssprotection config should make it work. It works for me when I tried it in WKND pages with new attribute added in /apps/cq/xssprotection/config.xmlFew things to try at your end:1. Try adding j...