Product Communities

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

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.

List of New AEM Articles   [AEM Forms CS] Use the PDF Services API with AEM Forms - Course  [Commerce] - Enrich product data with associated AEM content  [Forms CS]Fill and sign AEM Forms using Adobe Sign - Course  [AEM CS] AEM Maven Project Structure - Technical Video  [AEM CS] OSGi Services - Basics - Technical Video  [AEM CS] OSGi Services - OSGi Component Lifecycle - Technical Video  [AEM CS] OSGi Services - OSGi Configurations - Part 1 - Technical Video  [AEM CS] OSGi Services - OSGi Configurations - Part 2 - Technical Video  How to set the Oak login token session expiration - Technical Video  How to force a recompilation of all Sling scripts jsps, java, and sightly - Technical Video  How to enable asset download report - Technical Video  How to troubleshoot issues related to Jetty configuration in AEM - Technical Video  How to troubleshoot performance related issues in AEM - Technic

Hi All,I am using AEM6.4 and I have editable template in my application.Everything is working fine with editable template.Now I need to create multilingual pages.Currently I have English page, now I need to create Chinese page for the same.I am authoring header and footer on base-template in English.Please let me know what is the best approach to translate base-template in Chinese.Regards,

Join us for our next Adobe Campaign Community Q&A Coffee Break, on Thursday, August 5th, 2021 @ 8am PT   Register here for this Adobe Campaign Community Q&A Coffee Break.   We'll be joined by Juergen Naeckel aka @juergenna, Principal Technical Architect 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:  Leveling up with Adobe Campaign - Simple to complex workflows Personalization Email design best practices Monitoring and reporting 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 INSTRUCTIONS Click the b

Hi All, I have a requirement where author can provide the alt text on dialog field or when the checkbox is clicked, alt text will be the image title.I am able to set everything fine, but i also want to show the dropped image title on the dialog field. Is there any way to show the image title on dialog field other than making a ajax call through JS (I cannot do it as it is blocked). Also whenever different image is dragged and dropped, I have to show its corresponding image title as alt text. Thanks,Santhosh

I was going through this article https://helpx.adobe.com/analytics/kb/sending-image-requests-emails.html to track email opens for our campaigns using image requests. I'm having difficulty in creating an image request for the following pagehttps://www.vitas.com/resources/end-of-life-care?cmpid=c2356. We are planning to do an email campaign to direct our users to this page and I'm interested to know the number of emails opened. Can anyone please help me to create a hardcoded image request so that I need to see the number of email opens in Email Open rate report of our global report suite.

Adobe Campaign enables you to design and host various landing pages on its server including online surveys, preference centers, and unsubscribe pages. Learn how to navigate Adobe Campaign’s web application editor by creating a preference center  through this how-to video tutorial on: Configure Landing Pages   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.

Enrich product data with associated AEM content by Adobe Docs Abstract Learn how marketers can enrich product data with associated content from Adobe Experience Manager. Content, like assets and Experience Fragments in AEM can be associated with commerce products. Once associated, these content types can be dynamically inserted on to a placeholder within a product page or category page. This opens up a wide range of possibilities for marketers to target specific product page with additional content like images and video. AEM CIF Core Components provides content authors the ability to create additional category and product pages. These pages can be enriched with additional marketing content and configured to target specific categories and products. The following video walks through the setup of this feature. Read Full Blog Enrich product data with associated AEM content Q&A Please use this thread to ask the related questions.

Develop an Asset Compute metadata worker by Adobe Docs Abstract Develop an Asset Compute metadata worker Custom Asset Compute workers can produce XMP (XML) data that is sent back to AEM and stored as metadata on an asset. Common use cases include: 1. Integrations with 3rd party systems, such as a PIM (Product Information Management system), where additional metadata must be retrieved and stored on the asset 2. Integrations with Adobe services, such as Content and Commerce AI to augment asset metadata with additional machine learning attributes 3. Deriving metadata about the asset from its binary and storing it as asset metadata in AEM as a Cloud Service In this tutorial we’ll create an Asset Compute metadata worker that derives the most commonly used colors in an image asset, and writes the names of the colors back to the asset’s metadata in AEM. While the worker itself is basic, this tutorial uses it to explore how Asset Compute workers can be used to write back metadata to assets

Content Fragment Enhancements in AEM as a Cloud Service by Bryan Williams, Lead Architect Abstract One of the great things about AEMaaCS (AEM as a Cloud Service) has to be the fact that new features by Adobe can, for the most part, be rolled out fast and painlessly. One of my personal favorite features that has come in useful for many client requirements is the ability to store structured data in AEM Content Fragments. Structured Content Fragments were introduced in AEM 6.4 and allow an author to define a data schema, known as a Content Fragment Model, using a tool in the Touch UI and then create assets in the DAM that are based on one of these models to hold the desired data. This is part of Adobe's headless CMS initiative. A simple usage of this feature might be if you want to store addresses of various retail stores for your business. You would first create a Content Fragment Model with the various text fields for Address 1, Address 2, City, State, etc., and then start creating Co

Building mobile extensions by Adobe Docs Abstract To support customer-specific features, and allow for the greatest flexibility, Adobe Experience Platform Mobile SDK provides an interface that allows customers to integrate with the Mobile Core at a much lower level. This interface allows customers to define extensions, which are similar in capabilities to the extensions that Launch has written for Adobe's internal services. The Mobile Core allows all extensions to access the events and data being sent through the Experience Platform SDK. Extensions allow customers to extend the Experience Platform SDKs with their own code. This includes listening for and dispatching events, reading the shared state of any registered extension, and sharing the state of the current extension. The application can use the extension to monitor for information that Adobe does not expose by default. It can also use the extension to modify Experience Platform SDK internal operations. For example, the applicat

Overview of asset ingestion and processing with asset microservices by Adobe Docs Abstract Adobe Experience Manager as a Cloud Service provides a cloud-native method to leverage Experience Manager applications and capabilities. One of the key elements of this new architecture is asset ingestion and processing, powered by asset microservices. Asset microservices provide a scalable and resilient processing of assets using cloud services. Adobe manages the cloud services for optimal handling of different asset types and processing options. The key benefits of cloud-native asset microservices are: 1. Scalable architecture that allows for seamless processing for resource-intensive operations. 2. Efficient indexing and text extractions that does not impact the performance of your Experience Manager environments. 3. Minimize the need for workflows to handle asset processing in the Experience Manager environment. This frees up resources, minimizes load on Experience Manager, and provides sca

3rd-Party GraphQL integration with AEM Commerce and CIF on Adobe I/O Runtime by Adobe Docs Abstract Working on 3rd-party integration requires that you are absolutely familiar with the following pre-requisites. GraphQL: how schemas are defined, what resolvers are and how to write resolvers GraphQL basics: https://graphql.org/learn/ GraphQL schema: https://graphql.org/learn/schema/ GraphQL resolvers: https://graphql.org/learn/execution/ Adobe I/O Runtime: how to write, deploy, and get the logs of actions Read the developer documentation Check the public developer forum Make sure you also get used to schema introspection, and how to write and test GraphQL queries GraphQL introspection: https://graphql.org/learn/introspection/ Tools: install the ChromeiQL/GraphiQL extension for the Chrome browser Get familiar with the Magento GraphQL schema and the types of queries you can make Magento GraphQL documentation: https://devdocs.magento.com/guides/v2.4/graphql/index.html You can also read our

AEM | How to add osgiconfig in archetype 26 and above !? by Veena Vikraman Abstract #AEMGyaan Time . For latest archetype supporting 6.5 , the OSGI Configs structure has been changed a bit. If you check your code base in AEM , you will see a node called osgiconfig under /apps/ No alt text provided for this image All your OSGI configurations are going to be added to this node and will be picked up from here . As you might be aware , we should not be adding any OSGI Conifgurations directly to the Felix Console. It should always be added via config node of your project. Now when using AEM archetype 26 and above ( which is mainly targeted for 6.5 and above) , the way the code and content is organized is bit different mvn archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=26 Once you create a project with these archetype and check your code base , you will see quite a lot of folder separations. In addition to the ui.ap