Product Communities

Are you using the Akamai hosting option for your Launch libraries? If the answer is yes, then this post is for you!We have been working with Akamai to implement cache control headers on DTM and Launch libraries. This functionality is now in production for both Adobe and Akamai. This means that all production libraries hosted on Akamai will now have a cache request of 60 min included in the header. However, this still a request and is up to the browser to respect the request.Previously, we were not setting the cache control request, so browsers would make their own caching decisions, which lead to unexpected results occasionally.If you are using Launch, there may be action required to fully deploy this feature. Your production library will have a request of 60 min without any action on your part. However, development and staging libraries for Launch will need to have either "-development" or "-staging" in their filename. If they do not, their cache control will be set to 60 min instead

If you weren't able to attend the Experience Makers The Skill Exchange event earlier this month, don't worry, all of the sessions are now on demand within Experience League! Check out both the developer track and the marketer/web producer track here: https://experienceleague.adobe.com/docs/skill-exchange-events/events/overview.html?lang=en Developer Track - Multi Tenancy - Core Components/Style Systems - Extending AEM Headless with App Builder - Experience Makers Spotlight!    Marketer/Web Producer Track - The Power of Reusability - Driving Business Value with Content Personalization  - Maximizing Your AEM Implementation 

May 2022 release details: https://nation.marketo.com/t5/product-documents/filtering-email-bot-activity-feature-may-2022-release/ta-p/324860   With a focus to address bot's impact on Email engagement, in 2021 we have launched our first version of filtering email bot activities. We have seen that this version of the solution is capturing an average of 2 Million bot activities per week for nearly 1000 Marketo customers. The impact is 3% of all email clicks and opens logged, while the industry average is ranging from 15% to 30%.   We got feedback from a lot of customers and from the Marketo community. We have categorized the feedback into the following themes:   Themes Description More Transparency The current version identifies the bot and doesn't log activities identified as bots. Almost every customer and community expressed they would like to log the activities and do their own analysis More Robust filtering The current version completely relies on

Hi All,I am working on a requirement where in I need to create custom email-templates and these will be used to create email pages in AEM and later it will be synced to Adobe campaign and from there emails will be sent to several people.When I verified the adobe documentation @ https://docs.adobe.com/docs/en/aem/6-1/administer/integration/marketing-cloud/campaign/best-practices-for-email-templates.html says as below:There are currently seven components available for use inside campaign templates( under path /libs/mcm/campaign).These components are optimized for mail content; that is, they adhere to the best practices outlined in this document. Using other out-of-the-box components will usually violate these rules.I created custom components by using the best practices explained in the documentation. I also used some of the OTB components on the email-component page. I packaged everything which includes. content-email-page custom components and templates and installed on n another machi

Hi,I am trying to find the query to extract all the pages which has two components in it. I wrote the query to extract a single component but having trouble to write the query to pull the pages which has both components.Any help would be appreciated.Thanks.

In AEM 6.5 when trying to send an email from the workflow to a fake SMTP server, the workflow is pointing towards the wrong email template... It should send the email from the following templates, /libs/settings/workflow/notification/email/default/en.txt but it is picking up some random template.  Can someone help me in how to fix this ?

  Sorry if this has been addressed but I'm not finding results I am looking for.  Many of the property views are not working in my local instance. When I check the error.log, I am seeing a lot of IOExceptions being thrown due to   File "/libs/foundation/global.jsp" not found When I go into CRX/DE and navigate to this node, the file is there. I'm not sure if there is an indexing issue or what. This is causing a lot of pain points because I cannot use some of the Touch UI pages to view information about pages and assets but have to pick  through CRX/DE to look directly at the node structures to find the information.   Is there a resolution to this without having to rebuild my local instance? This always ends up costing me about a day due to reloading packages of hot fixes, content, assets, and rebuilding all of the code.

Sometimes when we're trying to wrap our heads around a concept or idea, a detailed example and/or visualization can be immensely helpful. In the case of attribution reporting with Marketo Measure (fka Bizible), it can be a reporting mindset shift so I wanted to share an example that I've been using lately.    For our example, let's say that Riah is in the market for a Moped Scooter and her buying journey goes like this:    1.  Riah searches organically on Google to see options. She finds a company, Magical Mopeds, and clicks through to the site to learn more but doesn’t fill out a form or purchase 2.  A few days later, Riah is still researching and sees a Paid Search ad for Magical Mopeds and then fills out a form to access a guide for selecting the best Moped type 3.  A week later, Riah receives an email from Magical Mopeds and clicks through to the website to make a purchase    This journey might be overly simplified but for example purpos

Welcome to the 1st edition of the Adobe Campaign Community Lens! Adobe Campaign Community Lens is like your community bulletin board highlighting the latest updates from the Adobe Campaign Community in one place. In this edition, we are sharing updates from June and July 2022, including, the most viewed Adobe Campaign content on Experience League, as well as the latest product releases, upcoming and past learning opportunities, and a lot more!   Adobe Campaign Community Lens 🚀LATEST RELEASES🚀 Learn about all the new capabilities, upgrades, improvements, and fixes that were included in the latest release for Adobe Campaign: Adobe Campaign Classic v7 Release: [Release Update | Campaign Classic V7] Release 7.3.1 - Build 9352_July 2022 Adobe Campaign Standard Release: [Release Update] Release 22.2 - June 2022 Control Panel Release: [New]: Control Panel support for ACC v7 Hybrid deployment model.   📅EVENTS AND OPPORTUNITIES📅 Explore the new Adobe

Hi Team,Anybody please help on this below issue. if i execute the below query it is executing in CRX but in code level it is getting this below error. at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624) [org.apache.felix.http.jetty:4.1.4]at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) [org.apache.felix.http.jetty:4.1.4]at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1435) [org.apache.felix.http.jetty:4.1.4]at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) [org.apache.felix.http.jetty:4.1.4]at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:501) [org.apache.felix.http.jetty:4.1.4]at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594) [org.apache.felix.http.jetty:4.1.4]at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) [org.apache.felix.http.jetty:4.1.4]at org.eclip

【目的】ページに埋め込んだはずのリンクのURLがレンダリングされていないとき、XSS Protection機能によってURLがブロックされている可能性があります。XSS Protection機能はコンテンツをフィルタリングし、無効なURLをブロックします。本記事ではブロックされたURLの確認方法をご紹介します。   XSS Protectionhttps://experienceleague.adobe.com/docs/experience-manager-65/developing/introduction/security.html?lang=ja   【環境】AEM 6.5   【対応方法】 Webコンソール／Sling／XSS Protection へアクセスします。(またはhttp://localhost:4502/system/console/xssprotectionへアクセスします。) StatusタブのBlocked URLsの以下の項目よりブロックされたURLが確認できます。URL: ブロックされたURLTimes Blocked: ブロックされた回数                     ＜留意事項＞・上記は以下記事の抄訳/翻訳となります。KB記事タイトル(英語). Adobe Experience Manager: How to check URLs blocked by XSS Protection, August 22, 2022, https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-20407.html, (参照 2022-08-22).・本記事にいただいたコメントへの返信はお約束できません。あらかじめご了承ください。

Hello AEM Community! Just wanted to share a really exciting webinar happening tomorrow! City National Bank will be discussing how integrating an intelligent digital asset management (DAM) system with Adobe Workfront streamlines content orchestration at scale and does so across all of your digital channels!    LIVE WEBINAR DATE: Thursday, August 25, 2022LIVE WEBINAR TIME: 10:00 AM PST | 1:00 PM EST   Register for free now: https://engage.adobe.com/WFAssetsCNBWBR-Registration.html 

Use this thread to ask any questions related to the Set up SMS Set up SMS for Adobe Campaign course on Experience League.  Experts are monitoring this thread to ensure your questions are answered.

Let’s say you want to immediately switch to lightbox mode (using the Forms 2.0 native lightbox() feature) when a specific form is ready.   You’d think there’d be zero difference between Approach #1: MktoForms2.whenReady(function(mktoForm){ if(mktoForm.getId() == 1234) MktoForms2.lightbox(mktoForm).show(); } }); MktoForms2.loadForm("//pages.example.com", "410-ABC-673", 1234);   And Approach #2: MktoForms2.loadForm("//pages.example.com", "410-ABC-673", 1234, function(mktoForm){ MktoForms2.lightbox(mktoForm).show(); });   Both snippets load the form and fire a callback when it’s ready.   In #1, the callback function technically runs when any form becomes ready, but the lightbox is conditioned on the form ID. (For a page with only one form, that condition wouldn’t be necessary.)   In #2, the callback runs only when form 1234 is ready, since it’s part of that form’s  loadForm() call.   All other things

I have worked in Marketo Measure (Bizible) since 2018. I will say when I first started using the tool, the thing that helped me the most in learning what the tool was capable of was diving into the reports and building the custom reports that were installed with the managed package.     Many clients will start with the Bizible 101 reports, which is a good place to start, but many are still confused with how to optimize those reports based on not having the background on the report type.      So, I have created a quick guide to what kind of custom reports are added to your SFDC when you install the managed package.   My hope is that this guide will help all users to better understand the data available based on each report type. Here is the Marketo Measure Taxonomy, as this will be helpful in understanding how these custom reports join the specific objects: https://experienceleague.adobe.com/docs/marketo-measure/using/configuration-and-setup/

Details Adobe Experience Manager as a Cloud Service Release Overview Video 2022.7.0. This highlights of the latest features and innovations for the July 2022 release for Assets, Assets Essentials, Sites, Forms and Cloud Foundation.   Assets: Asset Essentials: Reporting Forms: Scribble Signature Keyboard Input Support Sites: Experience Cloud Setup Automation CIF – WKND Adventure Demo Site CIF – Support for Magento 2.4.4 CIF – Enhancements to Core Components CIF – Product Enrichment for AEM Pages Modernization of SPA Editor React SDK Web-optimized Image Delivery Cloud Foundation: Unified Shell Support (prerelease) Bulk Channel Assignment Release Overview Video Seed Q&A Please use this thread to ask the question related to this release. See all the Previous Releases here and Current Release Notes here.

Hello AEM Assets Community! Just wanted to share a really exciting webinar happening tomorrow! City National Bank will be discussing how integrating an intelligent digital asset management (DAM) system with Adobe Workfront streamlines content orchestration at scale and does so across all of your digital channels!    LIVE WEBINAR DATE: Thursday, August 25, 2022LIVE WEBINAR TIME: 10:00 AM PST | 1:00 PM EST   Register for free now: https://engage.adobe.com/WFAssetsCNBWBR-Registration.html 

Use this thread to ask any questions related to the Experience League LIVE session titled, "Ask the experts: Useful extensions in Tags (Launch) to help super charge the Web SDK." Experts are monitoring this thread to ensure your questions are answered. Thanks and we hope to hear from you!

A colleague of mine put together a nice summary of how cloning and sharing works across workspaces, which I thought might be a useful guide to share.What Assets Can I Share Across Workspaces?You can share these items across workspaces:Email Templates (found in Design Studio)Landing Page Templates (found in Design Studio)Models (found in Lead Database)Smart Campaigns (found in Marketing Activities...but we really recommend not having standalone smart campaigns)Smart Lists (found in Lead Database)Segmentations (found in Lead Database)Snippets (found in Design Studio)How Do I Share Assets?Determine what you want to be shared (e.g. Landing Page Templates)Right click and select New FolderName the folder you plan to shareMove the assets you want to share to the folderRight-click the folder and select Share FolderSelect the workspace(s) you want to share the folder with. Click Save.The dialog displays the workspaces you have permissions to view.The originating folder displays in the Lead Data

Author: Brian Hawkins One of our customers here at MiaProva is expanding their testing efforts and use of Adobe Target well beyond their www and mobile site. They are bringing Adobe Target to their Email Platform, and we are helping them do so. The magic that is making this possible is Adobe Target’s Delivery API. You have to call Adobe Target before emails get sent because you can’t put mboxes or Adobe Target server calls in email. The Delivery API does precisely this. It calls Adobe Target with data, just as a client-side mbox does on the site, and it gets a response based on any Activities and Audiences configured in Adobe Target. Host Groups The challenge this organization is dealing with was permissions within Adobe Target. The team developing this incredible capability for email testing with Adobe Target didn’t have the necessary Approver rights. Given they were new to Target and this organization has hundreds of live activities in place, handing out Approver rights was

Proof is set up to be military time - can it be updated or allow the agency the capabilities to update per their time zone?

How to Schedule the Activation and Deactivation of Pages in AEM by Mohan Giradkar Abstract Introduction to AEM Adobe Experience Manager is a content management system tool developed by Adobe. A content management system tool is used for website authoring, collaboration, and administration which ultimately helps to create, edit and publish the content. Using the AEM tool, creating websites, mobile apps, or forms is simple. AEM is a business content management system (CMS) that optimizes authoring and content management. Basics of AEM The author instance, publish instance, and dispatcher form the core of the entire AEM configuration according to the AEM architecture. Author In simple terms, an Author instance is where users create and edit the content, which can be published when the activation is performed. The author allows for complete authoring, component configuration, uploading, modification, deletion, and related tasks. Activation is done for content that needs to be live or

What are your AEM Hosting Options? by Peter Nash Abstract The early years of Adobe Experience Manager (AEM) development had a lot of customers asking, “how am I supposed to host this site?” The challenges to find a solid and secure system to host an AEM site were quite large. Adobe had a real problem on its hands because often, the infrastructure that was independently set up by customers was insufficient to the task or was done so by people who weren’t skilled enough in the system to be able to correctly do it. This caused a lot of heartburn for those organizations that made large investments in license fees and implementation costs. Thankfully, the years of maturity and ownership by Adobe have simplified the ways to properly host an AEM site. Today, there are 3 basic ways to host an AEM environment: Self Hosted, Adobe Managed Services, and AEM as a Cloud Service. Let’s quickly break down each one. Self-Hosted — This typically means that the organization is completely responsible f

How to upgrade to Adobe Experience Manager 6.5 by Nitin Seth Abstract The AEM version 6.5 is a feature-packed upgrade from Adobe. Here’s a step-by-step upgrade process that has been followed and curated to successfully upgrade many of our enterprise customers to AEM 6.5. Performing an in-place upgrade to AEM 6.5v This post talks about the upgrade procedure for the AEM 6.5. Section Pre-Upgrade In Place Upgrade Code Base Upgrade Post Upgrade Pre-Upgrade Scenario: Before executing your upgrade, there are several steps that you must follow. Please also visit Adobe’s official page for Upgrading Code and Customizations and Pre-Upgrade Maintenance Tasks for more information. Subsequently, make sure that your system meets the requirements for the new version of AEM. Please verify how Pattern Detector can help you estimate the complexity of your upgrade and also see the Upgrade Scope and Requirements section of Planning Your Upgrade for more information. Pre-upgrade checks and tasks Foll

AEM 6.5.12.0 - Extend RTE Link Plugin Command to add Icon / Info text specifying doc type by Sreekanth Choudry Nalabotu Abstract Goal Extend the RTE Link Command (/libs/clientlibs/granite/coralui2/optional/rte/js/core/commands/link.js) to automatically add html specifying document type (eg. PDF, Word etc.) Solution Create clientlib /apps/eaem-rte-anchor-link-html/clientlib with categories=[cq.authoring.dialog.all], add the following code.. (function ($, $document) { const RICH_TEXT_EDITABLE_SELECTOR = ".cq-RichText-editable", DATA_RTE_INSTANCE = "rteinstance"; $document.on("foundation-contentloaded", function(e){ const $richTextDiv = $(e.target).find(RICH_TEXT_EDITABLE_SELECTOR); $richTextDiv.each(function() { $(this).on("editing-start", function() { const $this = $(this), rte = $this.data(DATA_RTE_INSTANCE), ek = rte.editorKernel; extendLinkCommand(ek.registeredCommands._link); }) }); }); function extendLinkCommand(_linkCmd){ const origAddLinkToDomFn = _linkCmd.addLinkToDom; _