Product Communities

Composable Headless: Bounteous Releases AEM Integration for Vue Storefront by Paul Rohrbeck Abstract Successful organizations are asking business units to collaborate on the design of customer experiences with their marketing and technology teams. According to Gartner, this need for greater flexibility is leading digital-forward companies to employ composable strategies to simplify and accelerate building experiences. In this way, they can scale the delivery of current and future business experiences. Vue Storefront is a front-end platform for headless commerce that's been gaining popularity over the last few years. It has been a popular choice for the delivery of responsive web PWAs within a composable architecture. It already has a lot of integrations with commerce platforms and headless content management systems but one that's been missing, until now, is Adobe Experience Manager (AEM). With our deep knowledge of AEM and commerce, it was a natural fit for us to create the integrat

A Day In The Life Of An AEM Developer With Travis Estell by Avionos Abstract Being passionate about high-quality solutions and delivering measurable results makes our AEM Developers key players in providing innovative digital experiences for our customers. Our Adobe Experience Manager (AEM) Developers provide high quality code solutions to meet digital commerce and marketing client needs in the implementation, enhancement, and support phase of project-based technology implementations. Hear from Travis Estell on his role as Lead AEM Developer: Give me a brief background on your career, where you’re from, and your favorite way to spend your time outside of work. I’m Travis Estell, a Lead AEM Developer who is based in Cincinnati, Ohio. Outside of work I like traveling, photography, and playing music. Why did you want to work as an AEM developer? I learned the basics of HTML and CSS on my own while I was in middle school and became known as the go-to guy for building websites. Since the

Life is full of risks. So are technology projects. If you ever saw the Ben Stiller movie Along Came Polly (maybe binge-watching movies during the pandemic), you got to meet Rueben Feffer, a man who assesses risk for a living using a risk management software program.In some ways, I can relate to the movie’s risk management character. As some of you know, when I worked at Omniture, one of my roles was helping customers fix broken analytics implementations. As I performed this role, I observed many key risk points associated with digital analytics implementations. As I have mentioned in past blog posts, many digital analytics implementations fail or underperform for various reasons, including consequential decisions made or approaches taken at these key risk points. Whether you work for an organization managing your digital analytics implementation or at an agency that helps clients with analytics implementations, understanding the key places that lead analytics programs

Hello Adobe Analytics API User,This is a final reminder that the following Adobe Analytics API services are scheduled to be deprecated on August 18, 2021. 1.3 Analytics APIs 1.4 SOAP Analytics APIs Legacy OAuth Authentication (OAuth and JWT) If you haven’t already, we highly recommend that you consider moving off of these versions as soon as possible to avoid any disruption or risk losing access to workflows that may be based on these services. You can refer to Legacy API EOL FAQ to understand how this might impact you and for guidance on how to proceed. Please review your own API use and Adobe Analytics integrations to determine the services impacted. No action is required if your company does not directly or indirectly employ any of the services listed above.Please note that you can migrate your API integrations to the 1.4 Analytics REST APIs and/or the 2.0 Analytics APIs and Legacy OAuth accounts to an Adobe I/O Analytics integration account, which can be used to access bot

Have you ever wondered about the best dashboard layout to use when reporting to your executives? Or which style charts to use when presenting data around volume of requests being submitted to your teams? Join us TOMORROW (Tuesday, August 10) at 8:00am Pacific / 4:00pm UK for a 90-minute networking session where we'll talk about how to tell a great story with your data through dashboards and data visualizations. RSVP here. We'll be joined by @Matt Thomas‚, Sr. Product Manager at Adobe Workfront who will share strategic foundations for creating effective dashboards, from understanding your audience to what you want them to take away from your reports. We also have THREE customers joining us who have featured reports in the Adobe Workfront Reporting Cookbook. They'll each share a bit of context to the reports and answer any questions you might have. The reports we'll review are: Open Tasks By Assignment | @Kathy McLaughlin‚, Mayo Clinic‚Contracts Pending Approval | @Alis

Everytime after the deploying project bundle jdbc pool osgi config need to be resaved manually, or else I am getting the error at DataSourcePool.getDataSource("testConn")unable to find the datasource with name "testConn", oracle bundle and my project bundles are active, how to make it pick automatically,DataSourcePool.getDataSource("testConn") will be called everytime when the code attempts connecting to oracle Config Name: com.day.commons.datasource.jdbcpool.JdbcPoolService-archival.config Have tried to get the dataSource on every query exection, but still facing same import java.sql.Connection; import java.sql.PreparedStatement; import java.sql.ResultSet; import java.sql.SQLException; import javax.sql.DataSource; import org.osgi.service.component.annotations.Activate; import org.osgi.service.component.annotations.Component; import org.osgi.service.component.annotations.Modified; import org.osgi.service.component.annotations.Reference; import org.slf4j.Logger; im

**Video re-uploaded in June 2024     Now that you have a strategy for your nurture launch, you'll want to build in an efficient way to leverage existing or new content and apply localization or personalization. However, you may be struggling with where to start. Join Adobe Marketo Engage Champions @julz_james & @amanda_thomas6 as they show you how to build a behavioral-based nurture during this live hands-on workshop. They'll show you what content to use based upon your buyer's journey and more.   During the workshop you'll learn: How to leverage a content library to use within a nurture How to build nested nurtures to enable behavior-based personalization How to localize your sends and content within a nurture Looking for additional resources? Slides: Behavioral-based advanced nurtures Blog: Creating an Adaptable, Scalable Nurture Program Template in Marketo Webinar: Creating a Scalable Buyer's Journey Using Engagement Programs & Dynamic Conte

When i open any AEM project site page it resulting a blank page view, i had checked the view as published for the page then it shows me an error like this org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: Compilation errors in org/apache/sling/scripting/sightly/apps/core/wcm/components/container/v1/container/container_html.java: Line 43, column 1900 : com.adobe.cq.wcm.core.components.models.LayoutContainer cannot be resolved to a type.Then i removed the existing project setup from my local and created the new project setup again then i build the solution and it is success but still the page is blank .I checked into bundles then i got to know that this below package is missing. The below screenshot is taken when i manually tried to installed the package into bundles and on doing this i got to see some errors in this package. How to automatically gets installed this package into bundles? The c

Invalidate the CDN cache for Dynamic Media Using URLs by Bimmi Soi Abstract Dynamic Media assets are cached by the CDN (Content Delivery Network) for fast delivery to your customers. However, when you make updates to those assets, you want those changes to take effect immediately on your website. Purging or invalidating the CDN cache lets you quickly update assets that are delivered by Dynamic Media. Instead of waiting for the cache to expire using a TTL (Time To Live) value (default is ten hours), you can send a request from within Dynamic Media to have the cache expire within minutes. To invalidate your CDN cached content for Dynamic Media assets: Go to the image you have updated and click on the url button On click of url, a popup will show up with the Dynamic media url for that specific variation. Copy this url and navigate to Tools > Assets > CDN Invalidation. Click on CDN Invalidation Manually add or paste full URL paths to Dynamic Media assets which you copied earlier

Hello All, I am using AEM 6.5.8 communities and in a regular component looking to get logged in user's community groups which they are part of. I am looking at https://helpx.adobe.com/experience-manager/6-5/sites/developing/using/reference-materials/javadoc/com/adobe/cq/social/members/api/CommunityMemberUserProfile.html#getMemberOfGroups--  and looks like I can use getMembersOfGroups() to get the (Community only) groups the user is a member of. If I am using an HTL component and Model, how can I invoke the CommunityMemberUserProfile interface with the logged in user's perspective? @kautuk_sahni any Adobe AEM communities dev/expert that can be tagged here? I can't find any that helped in communities regards before.

AEM as a Cloud Service — Dispatcher Converter Tool by Dinesh Chaudhary Abstract Overview With Adobe Experience Manager (AEM) being available as a Cloud Service, there are a few notable changes on how Apache & Dispatcher configurations can be structured so that they can be deployed on the cloud. Below is an important if not exhaustive change list for dispatcher configurations on AEMaaCS. Some Apache directives may not be used (for example Listen or LogLevel) Only some pieces of the Dispatcher configuration can be put in include files and their naming is important. For example, filter rules that you want to reuse across different hosts must be put in a file called filters/filters.any. There is an extra validation to disallow filter rules written using /glob to prevent security issues. All virtual host sections should refer to port 80. Statement in virtual host section that refers to any port other than 80 will not get processed. This article outlines the Dispatcher Converter whic

Register/Map Custom AEM I/O Events by Kelvin Xu Abstract After setting up AEM I/O events following this, you will get the following AEM events mapped to I/O events OOTB and you can immediately hook them up with your I/O actions or webhooks. What if you want to map more AEM event types into I/O events such as asset_published or asset_metadata_updated? Here are the high-level steps. In general, what it takes is just to find the underlying OSGi event and map to a new I/O event code through a custom com.day.cq.dam.eventproxy.service.mapping.OsgiXdmEventMappingConfigurationImpl factory config. Let's take asset_published and asset_metadata_updated events as examples. asset_published Publish an asset and go to /system/console/events to find the event that can be uniquely identified by the event topic, path, and type. something like below, Use event topic, path, and type to define a custom OSGi config com.day.cq.dam.eventproxy.service.mapping.OsgiXdmEventMappingConfigurationImpl-asset_publi

Adobe I/O-Powered AEMaaCS Assets Export Implemented in Real-Time or Batch Mode by Kelvin Xu Abstract AEMaaCS Assets offers a cloud-native digital assets management solution, which is scalable, reliable, and hassle-free. It’s never been a better time for enterprises to adopt such a solution as their centralized DAM system. To share or distribute assets (or their renditions), AEMaaCS provides multiple ways such as asset link share, asset selector, brand portal, etc. But still, there are common use cases where assets (or renditions) just need to be exported to external cloud storage like Azure blob store, S3 bucket, SFTP, etc. (for other systems to further consume) or directly into 3rd party systems like Marketo, Adobe Campaign, PIM, etc. as long as they provide secured asset ingestion endpoints. Traditionally in AEM 6.x, this usually can be accomplished by “publishing” assets into downstream systems (within a workflow or something) via a custom replication agent. This won’t work in AE

A brief overview of AEM by Aditi Verma Abstract Welcome to my blog series on AEM. I am Aditi and I am a full-stack software developer. I am going to share with you why must someone use Adobe Experience Manager (AEM) for web application development and what to expect. Let us first understand what is AEM - Adobe Experience Manager (AEM) is a content management system used to build and manage content on the website dynamically. It was built to enable companies with lesser development capabilities, to be able to manage their websites even after the core development team has rolled off. It is easier to manage content as well as assets using AEM. It does require one-time development to develop custom components and integrate them with backend services or third-party tools. Once that is done, non-technical authors can simply create templates and pages reusing the custom components. What are some of the AEM capabilities - AEM comes with two instances — Author and Publish. Complete website d

Adobe Experience Manager GraphQL API: Easy, Efficient Content Delivery by Danny Gordon, Technical Marketing Engineer, Abstract The digital landscape is ever-evolving, continuously bringing new and exciting customer touchpoints into existence. Delivering personalized experiences across these touchpoints at scale is challenging — but with its API-first headless content management capabilities, Adobe Experience Manager makes it easy and efficient. “Headless” refers to a content management system that includes a robust set of authoring tools and a suite of APIs to deliver content in a channel-neutral format. Developers use the APIs to request content and then render it in their application, such as a website, single-page application, or mobile app. Think of the presentation layer (the digital experience users interact with) as the “head.” By decoupling the head from the content, the same content can be reused in multiple different experiences across channels. The headless design pattern

Older versions of Adobe Experience Manager, CQ, and CRX by Adobe Docs Abstract Older versions of Experience Manager documentation The versions of Experience Manager, CQ and CRX listed on this page are End of Life and no longer officially sold by Adobe. Our last versions of official documentation for these older versions are available for your self-help needs. We recommend you upgrade to the latest version (which currently is Experience Manager 6.5). NOTE To know when an Experience Manager version will reach end of core support, see products and technical support periods and search AEM. Before you install Before you download the package, determine who will consume the content. This decision will determine how it is deployed: Developers can install locally for quick reference. For broader organizational documentation needs, it is recommended the package is deployed on an internally accessible, non-production AEM Author instance. NOTE Users must be logged into the Experience Manager i

AEM Project Archetype by Adobe Docs Abstract The AEM Project Archetype is a Maven template that creates a minimal, best-practices-based Adobe Experience Manager (AEM) project as a starting point for your website. TIP The latest AEM Project Archetype can be found on GitHub. Resources Archetype Documentation (this document): Overview of the archetype architecture and its different modules. ->Using the Archetype: further details on using the archetype and the modules available ->ui.frontend: How to use the front end build module The following tutorials are based off this archetype: ->WKND Site: Learn how to start a fresh new website. ->WKND Single Page App: Learn how to build a React or Angular webapp that is fully authorable in AEM. Features Best Practice: Bootstrap your site with all of Adobe’s latest recommended practices. Low-Code: Edit your templates, create content, deploy your CSS, and your site is ready for go-live. Cloud-Ready: If desired, use AEM as a Cloud Serv

Page Templates - Editable by Adobe Docs Abstract Editable templates have been introduced to: Allow specialized authors to create and edit templates. Such specialized authors are called template authors Template authors must be members of the template-authors group. Provide templates that retain a dynamic connection to any pages created from them. This ensures that any changes to the template are reflected in the pages themselves. Make the page component more generic so the core page component can be used without customization. With editable templates, the pieces that make a page are isolated within components. You can configure the necessary combinations of components in a UI, thereby eliminating the need for a new page component to be developed for each page variation. NOTE Static templates are also available. This document: Gives an overview of creating editable templates For details see Creating Page Templates Describes the admin/developer tasks required to create editable

The Forms 2.0 Checkbox type works straightforwardly: if it’s checked, it sends the string “yes” to Marketo, and if it’s unchecked, it sends the string “no”. If the corresponding Marketo field is a Boolean, the “yes” is saved as true, and the “no” is saved as false.[1] This behavior is desired almost all the time. You might have wanted it 100% of the time you’ve worked in Marketo. But working across a range of clients, I get to see site-specific cases, and sometimes... for pretty good reasons... you want the opposite. That is, sometimes you want a ’box to send “no” if it’s checked and “yes” if it’s unchecked. This is typically due to the way the question (i.e. label) is phrased — when it’s deliberately avoiding the negative/discouraging/technical tone of the underlying logic. Take, for example, the Boolean field isMinorDependent labeled as “I’m 18 or over” on the form:     If the c

Join us for our next Adobe Campaign Community Q&A Coffee Break, on Thursday, August 5th, 2021 @ 12pm IST   Register here for this Adobe Campaign Community Q&A Coffee Break.   We'll be joined by Vipul Raghav aka @vraghav, Principal Technical Support Consultant for Adobe Campaign, who will be signed in here to the Adobe Campaign Community to chat directly with you on this thread to take your Adobe Campaign questions pertaining to his areas of expertise:  Running and Operating Adobe Campaign - Workflow optimization Monitoring best practices Delivery channels like Email, Push, SMS Message Center REQUIREMENTS TO PARTICIPATE  Must be signed in to the Community during the 1-hour period  Must post a Question about Adobe Campaign Coffee Break topic on this thread Think of this as the Adobe Campaign Community equivalent of an AMA, (“Ask Me Anything”), and bring your best speed-typing game INSTRUCT

**This video was re-uploaded in July 2024   In this video you'll learn from Adobe Marketo Engage Champion Courtney Tobe how to track and report on the ROI and revenue impact of your Adobe Marketo Engage programs.   This is a quick tip from our On-Demand Webinar: Beyond the Basics: Marketo Reporting.    

Issue/Query:Why does XML Add on v3.8 not support DITA 1.3 base element topic/div? For a migrated HTML document, the target topic .dita does not have any <div> tags.AEM Instance:AEM 6.5 + SP7 + SP8 + XML Add On v3.8Issue Description:Followed the steps from Migrate XHTML documents section of the document Installation and Configuration Guide The .dita file that gets created after the import is stripped off of any and every <div> tags. Confirmed from the h2d.xsl that this is indeed the case.<!-- divs: if we can base transform on a class, do so. --><!-- generic divs will fall through with no associated transform --><xsl:template match="div"><xsl:template match="div"> <xsl:apply-templates select="*|text()|comment()"/></xsl:template>  Is there a planned/available hotfix to fix this issue?@divrajsingh  

Fatigue management controls frequency and quantity of messaging to avoid over-solicitation of recipients and is often applied using a typology rule. Check out these interactive video tutorials on how to implement fatigue management in Adobe Campaign by using typology rules: Manage fatigue using typology rules using filters: Manage fatigue using predefined filters   In case you have any questions after watching this video, please feel free to post them below or reach out through the community Q and A section. In case you have any ideas and/or suggestions regarding the Campaign product or these video tutorials, then kindly submit them here.

Invalidate the CDN cache for Dynamic Media Using URLsDynamic Media assets are cached by the CDN (Content Delivery Network) for fast delivery to your customers. However, when you make updates to those assets, you want those changes to take effect immediately on your website. Purging or invalidating the CDN cache lets you quickly update assets that are delivered by Dynamic Media. Instead of waiting for the cache to expire using a TTL (Time To Live) value (default is ten hours), you can send a request from within Dynamic Media to have the cache expire within minutes.  Read Full Blog Invalidate the CDN cache for Dynamic Media Using URLs Q&APlease use this thread to ask the related questions.  

Is there a way to get a components content exposed to 3rd party app without using Content fragments or Experience Fragments. i.e I want my component contents json exposed.Is it possible.