Skip to main content

Filter by idea status

10000+ Ideas

LaurentLam
LaurentLamLevel 5

Ability to handle OOTB, attachments as external ressources.New

description Today we can send attachments to recipients using standard ACC functionality:Attaching files | Adobe CampaignHaving an OOTB functionality that would upload automatically files configured as attachments to a public ressource and create automatically the links(ex: https://<%= external.attachment[0] %> to access them would be a great feature This OOTB functionality is important at different level:1- sending attachments in emails is tricky for deliverability purpose: depending of the attachment size, the nature of the attachment, the ISP of the recipient, the amount of emails... It can badly affect your different ISP reputation.2- it affects your throughput as more an email is heavy, more the MTA takes time to process it... If you add the point 1, it can slow down your entire platform sendings during hours (retry feature)3- the ecological footprint created when downloading a file through HTTP is smaller than sending this file through SMTP (email). For companies that actually calculate their footprint, it could be a great functionnality... Apple already automatically had this kind of functionality: recipients are asked to download the fileI would like the functionality work this way:in the same menu as attachment we would turn on the functionality and be able to parameter for each "attachment" the security level:1- normal: link appears without specific token2- securized: a token in the generated link is automatically added based on broadlogId & deliveryId in order to avoid someone else to access it. the link wouldn't be displayed on the mirror page and the purge delay of the ressource deleted after 3 days The files on public ressources would be automatically deleted after delivery public ressources purge delay is over Actually we can develop a such type of functionnality and implement it on customer site but it shouldn't be the case for something that has been recommended for years by Neolane / Adobe 

Shashi_Mulugu
Shashi_MuluguNew Participant

Localized Reference for Experience FragmentInvestigating

Request for Feature Enhancement (RFE) Summary: Localized Reference for Experience Fragment Use-case: We are using AEM 6.4.8/6.5.8 and using experience fragments component in our page templates for header and footer implementations similar to WKND sites. In template, we add experience fragment component with "/content/experience-fragments/us/header" as fragment path and when we create pages in /content/<project>/us/page, we are able to see the US Header.   Now we created language copy of the experience fragment to "/content/experience-fragments/fr/header", and now created page under "/content/<project>/fr/page", due to Localization implementations in experience fragment core component, automatically FR header is picked up on the FR page. Current/Experienced Behavior: Now US Team, changed something in US header and planned to publish sometime next week. parallelly FR team changed some page content and when trying to publish FR page, it is showing US Header as outdated as part of References publish.. which is weird. Improved/Expected Behavior: the localization implementations done in core component experience-fragments model (com.adobe.cq.wcm.core.components.internal.models.v1.ExperienceFragmentImpl" also to be done for "com.adobe.cq.xf.impl.ExperienceFragmentsReferenceProvider" so check only for localized references. Environment Details (AEM version/service pack, any other specifics if applicable): https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/reference-for-experience-fragment-not-working-as-expected/m-p/405575#M28658   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):