Product Communities

Adobe Experience Platform’s Identity Service — How to Solve the Customer Identity Conundrum by Joseph R. Jones, Priyanka Sharma, Erin Davis, and Jody Arthur Abstract This blog describes how Adobe Experience Platform Identity Service works with identity data to help our customers develop the information-rich profiles they need to engage their customers at a deeper level. Check out the preceding blog about Identity Graph here. Identity is a core concept when it comes to building engaging and relevant customer experiences. Yet many enterprises struggle with building the rich and accurate 360-degree customer profiles necessary to deliver such experiences. The problems associated with establishing identity for enterprises is either they have an unmanageable amount of data or too little data. However, the primary challenge lies in connecting the data they have in a way that creates a meaningful representation of their customers’ identities. At Adobe, we know that fragmented profiles devel

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 c This article outlines the Dispatcher Converter which is part of the initiative by Adobe of developing code refactoring tools to make existing content (code, package structure, indexes, configurations) compatible with AEM as a Cloud Service. This tool converts existing AEM Dispatcher configurations to AEM as a Cloud Service compatible Dispatcher configurations by honoring the changes listed above along with the ones checked by validator script which comes as part of Dispatcher Tools mentioned here. Usage It is recommended to use this tool via the AIO CLI plugin for code refactoring tools which integrates all the code refactoring tools and minimizes

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. Read Full Blog Older versions of Adobe Experience Manag

Using Smart Crop with AEM Assets Dynamic Media by Adobe Docs Abstract Adobe Experience Manager’s Dynamic Media Smart Crop capability includes ->AEM Asset admins can easily create image profiles for Smart Cropping based on device width and height. ->Smart cropping can be performed for an individual asset or can be performed for all assets within a folder. ->Smart Crop Editing Layout can be resized for better visibility. ->AEM Sites’ Dynamic Media component supports Smart Crop. ->Published URL for the Smart Cropped asset is available to be used with 3rd party applications that accept hosted assets. Note: Smart Crop coordinates are aspect ratio-dependent. That is, for the various smart crop settings in an image profile, if the aspect ratio is the same for the added dimensions in the image profile, then the same aspect ratio is sent to Dynamic media. Because of this, the same crop area will be suggested in the Smart Crop Editor. For example, a crop setting of 100x100 and 2

Adobe Experience Platform (AEP) Dictionary by Jimalytics Abstract Adobe Experience Platform (AEP) introduces a lot of new stuff that can be tricky for folks to wrap their head around (including myself). When you look at Adobe’s documentation and presentations, they’re very buttoned up and often use industry jargon. This makes sense – it’s an enterprise selling to enterprises. Unfortunately, that’s not how my brain processes information. To remedy that, I created a term dictionary with words that humans use. For the TL;DR, here’s a quick cheat sheet I whipped up. The intent of this isn’t to replace documentation. Instead, this dictionary is to help us understand jargon and brand-specific terms. After working on this for hours, it’s still horrifically incomplete. I hope to be adding more to this – and as I learn more, create a more fleshed out cheat sheet that will clarify AEP terms. Before we go into the terms, I want to send a shout-out to Eric Matisoff from Adobe for answering all o

Why Choose Adobe Experience Manager (AEM) For Enterprise Knowledge Management by Impelsys Marketing Team Abstract Today’s consumers are digitally savvy, more connected – and more demanding. Businesses need to rethink their digital strategies and focus on delivering customer-centric experiences across various channels. Before we delve into the details, here is a snippet of a discussion with our customer for their business needs — During our Monthly Customer-Business Review, one of our strategic customers enquired about managing the enterprise knowledge and making it available to the users securely. Below mentioned were some of the interesting asks that they were looking for in a solution An Enterprise-grade solution that is capable of providing the following – Built-in Digital Asset Management features Content Management features Availability on the Cloud Powerful Search capabilities Task Management Effective Video Management capabilities Should easily help convert Visual Media Prov

Adobe Experience Manager, the leading headless CMS* by Adobe Abstract Why would you need a headless CMS? IT is looking to address Agility and Flexibility Organisations want to deliver app-like experiences in addition to regular content pages Javascript frameworks like React and Angular have matured Content delivery channels have increased in number and technology has diversified So, IT needs a flexible, decoupled, developer friendly CMS. AEM's Pillars for Headless GraphQL and Content Services power efficient rendering in client applications and robust APIs for content management AEM's Content Fragment Model editor enables you to define content models, relationships and governance via a no-code GUI. Our content fragment editor is an intuitive user interface for creating and managing content. Experience Fragments can be delivered as json objects or plain html while enabling rich personalisation across channels GraphQL Adobe's GraphQL APIs for Content Fragments supports headless use c

Adobe Campaign Insider Monthly Webinar Series Session Topic:  Adobe Campaign integrations with a marketing ecosystem   Recording URL: https://adobe.ly/3O37eQ1    About the Session: Cross-channel marketing solutions like Adobe Campaign should not sit in isolation from other technologies or teams. Unfortunately, data and content often get stuck in disparate systems, impeding a complete understanding of a customer and disrupting cross-channel strategies. Join this session to learn how Adobe Campaign integrates with other Adobe solutions and 3rd party technologies commonly found in a marketing ecosystem.Key takeaways: Understanding use cases enabled by Adobe Campaign Integrations Tips and tricks for integrating Adobe Campaign with other solutions Knowing where to go for help and resources regarding Adobe Campaign Integrations Insight into the Adobe Campaign roadmap Session Speakers: Bruce Swann, Principal Product Marketing Manager, Adobe Scott Segrin,&n

Adobe launches XML Documentation for Adobe Experience Manager as a Cloud Service by Loni stark Abstract The modern workforce is under tremendous strain because of the COVID-19 pandemic. Often with tighter budgets, organizations still need to sustain revenue streams while balancing the need to provide exceptional customer experiences and high engagement for their employees. And while resource availability may be at an all-time low, the volume of support required across industries is at an all-time high. As organizations look to ramp up support initiatives for customers and employees, documentation and content teams are facing an overwhelming demand to create and deliver contextually relevant support content faster. Adobe’s component content management system (CCMS) — XML Documentation for Adobe Experience Manager, is a mission-critical piece in the customer journey puzzle as it provides structured content management capabilities to author, manage and deliver relevant, personalized and

Introduction to Adobe Experience Manager by Netcomlearning Abstract What is Adobe Experience Manager (AEM)? Adobe Experience Manager is a platform for managing, delivering, and organizing emerging themes. Its fundamental goal is to provide consumers with meaningful interactions that will help them create identities, fuel demand, and expand their scope. The user can build tailored content with models and upload it safely in the cloud. Adobe Experience Manager is a product management system that allows you to offer helpful information to your customers across several platforms (web, mobile, app, etc.). Marketers may wish to expand AEM's capabilities to make it easier to build and manage campaigns, monitor marketing platforms, and personalize content. You should use Adobe Campaign, Analytics, Audience Planner, and/or Adobe Goal to do this. Let me go through those techniques in more detail, and then we'll see how Adobe Experience Manager fits in. Integrate the campaign fully inside the

What is Adobe Experience Manager (AEM) Forms? by Bounteous Abstract AEM Forms provide an easy-to-use solution to create, manage, publish, and update complex digital forms while integrating with back-end processes, business rules, and data. Designed to work across both mobile and web, AEM Forms can efficiently be integrated into your work process reducing the challenge of keeping track of a large database of forms and the chance of error. Before I started down this road, I thought it was just another form builder. Well, that’s part of it. But, to simplify it that much does not do this tool justice. Here is a quick run-down of some of the features that make AEM Forms a flexible, secure, and powerful choice: Back-end customization on form-submission Front-end integration with other platforms/websites Dynamic field population/data integration Adobe Sign for capturing a digital signature Automatic saving (for logged in or anonymous users) Custom field validation Form field rules (from si

HOW AEM STREAMLINES MULTI-CHANNEL CONTENT MANAGEMENT by PJ UTSI Abstract We live in a multi-channel world, and in 2021, no one deals with just one eCommerce channel. Even the simplest digital businesses will likely connect with their customers through social media as well as their traditional sales channel. Some businesses are savvy with social media and email newsletters or employ multiple avenues of engagement for their employees and customers via mobile apps. Some retail outlets take advantage of digital signage or multiple marketing based channels. With these different touchpoints in play, content in different formats, sizes, and styles adds up. Naturally, managing this diverse content across all of these channels can get really complex, really fast. Yet, this is not a 'nice-to-have' initiative—it is imperative as it directly relates to an optimized digital customer experience. According to research from PWC, 90% of consumers expect consistent interactions across multiple chann

Building Flexibility and Streamlined Internal Process with Hybrid Headless in Adobe Experience Manager by Steven Carter Abstract Organizations that create a lot of content to be used across sites or different applications can use a hybrid headless approach with Adobe Experience Manager (AEM) to add flexibility without sacrificing content authoring capabilities. If you've done anything with a Content Management System in the past few years, you've likely heard the term "Headless." Headless is used to describe the concept of storing the content within one system and consuming that content for display within another system. The "body" is stored in the CMS while the display or "head" is managed in a different system, leaving the CMS as a "Headless CMS." Going headless can offer several advantages over a traditional CMS setup. A primary advantage is the flexibility afforded when content can be consumed across various channels and disparate display systems. For example, content may be con

Moving Beyond Keywords to Make Visual Search Smarter: How AI Understands Creative Intent by Scott Prevost Abstract Most visual creations start with a search—for images, colors, fonts, and inspiration—but search has always felt disconnected from the creative process. It can be tedious and time-consuming to translate brilliant, imaginative ideas into words. Search terms rarely convey the aesthetics and emotions at the heart of a creative idea – which can make image search become a mind-numbing task when it should be inspiring. That’s why we’re using our artificial intelligence (AI) and machine learning technology, Adobe Sensei, to fundamentally change the nature of search and help make creative visions a reality. What AI-powered search can do, and what it means for creativity With deep learning, we’re training our search algorithms to better understand images to recognize objects—like cars, cats, humans, or even the Eiffel Tower—as well as colors, composition, style, and mood. Then, w

Adobe launches Adobe Experience Manager Screens as a Cloud Service by Shelby Britton Abstract As a result of the global pandemic and the resulting lockdowns, brands have spent the past year reimagining customer engagement in physical spaces. While in-store experiences may be changing, customer-obsessed brands see this as an opportunity to improve experiences by connecting online and offline channels, providing a consistent, personalized experience from web to mobile and all the way through to digital signage in physical spaces. At Adobe, enabling brands to provide a seamless customer journey across all channels has been the guiding vision for Adobe Experience Manager Screens. We’re accomplishing this by expanding Adobe’s best-in-class omnichannel content management capabilities to physical spaces. This purpose-built digital signage capability within Adobe Experience Manager is now offered as a cloud native service. Always up to date, the new Adobe Experience Manager Screens as a Clou

Memory still matters!RAM sticks are cheap and plentiful, and it’s been over a decade since everyday users needed to worry about memory usage on their desktop or laptop. Yet that’s not the case on the server side. There’s still a pretty low ceiling for per-process/per-tenant RAM allocation in traditional systems[1] and for SaaS apps that don’t explicitly charge you for memory usage. A leaky or hungry process — remember, even one line of code can be hungry if it’s executed 100,000 times in rapid succession, let alone simultaneously — can still put the hurt on a server. Let’s examine, with memory in mind, this strange snippet of Velocity from a recent Marketo Nation post: #set( $total = "abcdef" ) #set( $stringLength = $total.length() ) #set( $totala = $total.substring(0,$stringLength) ) ## some stuff using $totala instead of $total... The person who posted it didn’t write it: it was pasted from somewhere, so I’m not calling them out specifically. They didn’t even know what it was suppo

A heads up that tomorrow ‚Äì Tuesday, July 27 ‚Äì we'll be hosting a User Group on the topic of Workfront System Maintenance. Register here. This session will be a little different from previous User Groups and instead of a presentation, we’ll have an interactive panel discussion. @Skye Hansen‚ and @William English‚, System Admins at T-Mobile, and Shawn Loutensock and @Ryan Eaton‚, who manage Workfront's own instance of Workfront, will share their experience on everything from setting up a new instance, to regular maintenance, clean-up opportunities, and more. We'll leave plenty of time for group discussion for you to ask questions and discuss ideas about your own system maintenance processes. Hope you can join us! Workfront User Group - Workfront System Maintenance Tuesday, July 27, 2021 8:00am Pacific / 4:00pm UK Duration: 90-minutes RSVP here: https://adobe.ly/3cO1h9x

Join us for our next Adobe Campaign Community Q&A Coffee Break, on Thursday, July 22nd, 2021 @ 8am PT   Register here for this Adobe Campaign Community Q&A Coffee Break.   We'll be joined by Scott Segrin aka @scotts44930614, Principal Enterprise 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:  Adobe Campaign Integrations - Adobe Campaign + Experience Cloud Solutions, Adobe campaign & Adobe Experience Platform, and other 3rd party solutions   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

Learn how to generate a descriptive analysis report from a workflow  through this interactive how-to video tutorial on: Generate a Descriptive Analysis Report   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, then kindly submit them here.

Sling Model by Techinnovia Abstract Objectives After reading this article, you should have an Understand of Sling Models Benefits of Sling Models Understand how to use Sling Models in an HTL template Development Goals Sling Models are available since AEM 6.0 but can also be installed in CQ 5.6.1. Main advantages of using Sling Models are Reusability You can write your code based on design patterns. If you use Sling Models you can remove all business logic from JSP and do not scriplets. Maintenance It’s easier to test Sling Models, because they are Java classes and can be covered with unit test. Also, it’s easier to add logging. Scalability Costs for introducing of new developers are lower And development is faster. What is Sling Models? – Old Approach public class OldModel { private String title; private String decription; public String getTitle(){ ... } public void setTitle(String title){ ... } public String getDescription(){ ... } public void setDescription(String description

AEM Cloud Service - Show Asset References in Delete Dialog by Sreekanth Choudry Nalabotu Abstract Goal Adobe Experience Manager 2021.7.5607.20210705T063041Z-210600 Show Asset references in Delete alert box before proceeding with deletion.... Solution Create a clientlib /apps/eaem-asset-delete-refs/clientlibs/delete-cf-show-refs with categories=dam.gui.actions.coral and dependencies=eaem.lodash and the following code.. (function ($, $document) { "use strict"; var _ = window._; $document.on("foundation-contentloaded", function(e) { var deleteActivator = ".cq-damadmin-admin-actions-delete-activator"; $document.off("click", deleteActivator).on("click", deleteActivator, function(e) { e.preventDefault(); e.stopPropagation(); showReferences.call(this); }); }); function showReferences(){ var selectedItems = $(".foundation-selections-item"), paths = []; selectedItems.each(function() { paths.push($(this).get(0).getAttribute("data-foundation-collection-item-id")); }); var AssetReference

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

Unpacking July 2021 Release: Adobe Document Services by Ben Vanderberg Abstract Video: https://youtu.be/zHR3j30xQyY While many of you may be unpacking some of the updates we released in June, we have some significant new updates for Adobe Document Generation in our July release we are excited to share. These updates provide easier ways for you to play around with Adobe Document Generation, get started, as well as helpful tools for Adobe Sign users. NEW: Adobe Document Generation playground site Been interested in Adobe Document Generation but haven’t had time to download the SDK and give it a try? No worries. There is now a demo site you can give it a try. The website allows you to: See how Adobe Document Generation works with pre-created templates and JSON data. Upload your own Word documents and JSON data to test out the templates you have created without installing the SDK on your computer. Download sample templates and code so that you can more easily learn to use, tag, and test

AEM SPA editor - FAQ by Niek Raaijmakers Abstract Answering the most commonly asked questions about the SPA editor Today I am going to answer some FAQ that I get a lot from customers, that are not addressed in the latest post / archetype updates. Disclaimer: As the solution gets updated frequently, these answers might become outdated. Are Content Fragments supported? As of today just recently, for react yes, for angular not yet. (PR is pending) Check the PR for react here and for Angular here to see how it's used. Note: this is for the spa editor only because it depends on the component-mapping. Are Experience Fragments supported? As of today just recently, yes. They require you to overload a resource type from the spa-core project, and to provide 3 HTL files. No more Java hacking required. This is baked into the latest AEM archetype release now, so you don't need to worry about it if you use this as a base. Otherwise, you can generate a project and see how it's done there with m

Archetype update 28: SPA editor by Niek Raaijmakers Abstract At Adobe, we just released some updates to the AEM archetype. This includes some important updates for the react / angular frontend-module: Experience Fragment support provided OOTB (demo provided) Code splitting / lazy loading demo provided Navigation Component with routing provided in Header XF Server Side Rendering bootstrap provided Express + IO runtime for React Express for Angular These were topics that caused our customers that were implementing the solution to spend a lot of time on setting up. And most of them required this. Personally I got bombarded with questions on how to tackle this. Then the customers would implement these solutions on their private repositories. Now with these changes, our customers won't need to ask these questions; they will be armed with a working solution from the start without any effort. That's why I am really excited that this release is shipped successfully! You can start out with