Adobe Experience Manager

  Have you heard of AEM User Groups?  Newly launched in October 2021, AEM User Groups are customer-led meet ups intended to help users succeed with using AEM. Whether you are a developer, Sites enthusiast, or Assets expert, we invite you to explore the list of chapters available and join the one that best suits your needs.Don't see an existing chapter that is relevant for you? Use this form to start a new chapter and learn more about the perks of leading a user group.    RSVP TODAY for the first kick-off meeting, "Optimizing AEM Forms using Fragments and HTML5" on January 19th. Bring your questions and your curiosity and get ready for an interesting discussion!   

Experience Manager and Magento are seamlessly integrated using the Commerce Integration Framework (CIF). CIF enables AEM to access a Magento instance and bind the catalog data via GraphQL. It also allows AEM Authors to use Product and Category Pickers and a read-only Product Console to browse through product and category data fetched on-demand from Magento. In addition, CIF provides an out-of-the-box storefront that can accelerate commerce projects.ArchitectureThe overall architecture is as follows:AEM Venia Reference Store-frontThe AEM Venia reference storefront is a modern production-ready reference storefront showcasing a basic B2C commerce journey. It can be used to kickstart commerce projects and accelerate projects using AEM, CIF, and Magento. It demonstrates best practices for integrating AEM and Magento and shows how to use the Commerce Core Components. It also provides pre-sales with a reference site to demo the integration between AEM and Magento.The project is open source an

Hello all, trying to build my project and getting below error in my OSGi... (Project created by archetype 23) org.apache.sling.api.servlets,version=[2.3,3) -- Cannot be resolved I have this dependency added in my POM<dependency>    <groupId>org.apache.sling</groupId>    <artifactId>org.apache.sling.api</artifactId>  <version>2.3.0</version>    <scope>provided</scope></dependency> Tried all versions https://repo.adobe.com/nexus/content/groups/public/org/apache/sling/org.apache.sling.api/ but no luck. What am I missing? Error in logs:14.03.2020 22:36:12.200 *ERROR* [qtp1524159769-1650] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unable to resolve akamdashapi.core [585](R 585.1): missing requirement [akamdashapi.core [585](R 585.1)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.api.servlets)(

The AEM Assets implementation guide is a one stop shop for all your AEM Asset implementation needs.  From how to get started to final configurations – our guides aim to help you at every step of your AEM Assets implementation journey. Some handy links below:1)      Discovery and Requirements: A handy checklist that ensures you have all answers from your stakeholders before embarking on an implementation. https://adobe.ly/2umsfML 2)      Architecture & Design: A step-by-step guide to content modeling, application architecture​​, and Creative/Marketing Cloud integrations. https://adobe.ly/2skmCm3 3)      Installation and Provisioning: A guide that details out everything you need to know about installation and provisioning for AEM Assets. https://adobe.ly/2tnVoKJ 4)      Configuration and Implementation: A comprehensive guide to address all your queries on security, workflows, and other important AEM Assets implementation features + best practices. https://adobe.ly/2tobapb Hope you fi

Hi All,         I have created sitemap generation using acs common. I wanted to give the TTL for sitemap to caching.Anyone idea how can we so it. Kr,Sanjay

Hi @selvendranr9588 Could you please provide some more informaiton regarding the use case that you want to achieve using these headers from clientside?

AEM 6.5.10 - Lazy Load Image and Smart Crop req=set,json calls in Image Core Component by Sreekanth Choudry Nalabotu Abstract Goal Lazy loading feature in Image Core Component lazy loads the image improving performance, however with Dynamic Media enabled, the respective Smart crop settings for image prefetched using req=set,json calls (eg. https://s7d1.scene7.com/is/image/EAEM/test-zab67579_rgb?req=set,json) during page load may affect performance. Code in this post is for lazy calling req=set,json 1) Create the Image component /apps/eaem-dm-modifiers-smart-crops/components/image with sling:resourceSuperType core/wcm/components/image/v2/image 2) Add clientlib /apps/eaem-dm-modifiers-smart-crops/components/image/clientlib with categories=core.wcm.components.image.v2, file image-override.js with following code... (function() { "use strict"; if(!isPublishedMode()){ return; } const DM_IMAGE = "image"; const EAEM_DM_IMAGE = "eaem-image"; const EAEM_BOUNDING_DIV_CSS = "eaem-boundin

ESI : Rendering Dynamic Content | AEM by engineering.icf Abstract What is ESI ? Edge Side Includes or ESI is a small markup language for edge level dynamic web content assembly. The purpose of ESI is to tackle the problem of web infrastructure scaling. It is an application of edge computing. Static Content vs Dynamic Content ? Let’s assume we have dynamic website having most of the pages are mixture of static and dynamic content. The portion of the page should be un-cacheable and rest of the page should serve from the cache. The question here is, how do you ensure the cache won’t be impacted by having dynamic content on the page. A few possible options are – Option 1 : Load dynamic content Asynchronously (AJAX) Option 2 : Load dynamic content using ESI. I would say both the options are the best, but you should choose based on type of the website and infra considerations . Having said that, let’s talk about the scenarios when to choose what ? Read Full Blog ESI : Rendering Dynamic

AEM Custom Asset Compute Worker to Generate Content Fragments by Vishal Abstract AEM as Cloud Service’s Asset Compute microservices support the development and deployment of custom workers that are used to read, and manipulate binary data of assets stored in AEM, most commonly, to create custom asset renditions. Below steps to develop Custom Asset Compute Worker in Adobe IO and Configure Processing profile in AEM cloud: Local Development Setup Install Node.js 10+ Install Adobe I/O CLI by running command npm install -g @adobe/aio-cli@7.1.0 Install Adobe I/O CLI Asset Compute plugin using command aio plugins:install @adobe/aio-cli-plugin-asset-compute For local debugging please follow steps mentioned in https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/asset-compute/set-up/development-environment.html?lang=en Set Up IO App Follow Steps mentioned in https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/asset-compute/set-up/firefly.

Implementing Interactive Communication in AEM Forms by Suvadeep Dey Abstract This article aims to provide down the steps required to implement Interactive Communication in AEM Forms. This is a very complex process as par various online product documentation. The idea behind this article is to try and simplify the same by taking up a commonly used simple use case. Use cases Interactive Communication is an integral part of any transaction that a user carries out with a website in today’s online world. The transactions could range from online tickets, getting financial documents through an email from financial services firms, travel itinerary from travel portals, etc. The below could be some of the possible use cases where an interactive communication is used: 1. A user submits his/her details on an online form and the system after processing responds back to the user with an email that has an attachment in the shape of a interactive communication. This has both the data entered by the

WKND Tutorial - Project Setup by Adobe Docs Abstract This tutorial covers the creation of a Maven Multi Module Project to manage the code and configurations for an Adobe Experience Manager Site. Prerequisites Review the required tooling and instructions for setting up a local development environment . Ensure that you have a fresh instance of Adobe Experience Manager available locally and that no additional sample/demo packages have been installed (other than required Service Packs). Read Full Blog WKND Tutorial - Project Setup Q&A Please use this thread to ask the related questions.

No text available

I have created  synonym.txt for a index  in one environment  and trying to import to another environment using ensure oak of acs commons.After import i am not able to see synonym.txt . Followed link: https://adobe-consulting-services.github.io/acs-aem-commons/features/ensure-oak-index/index.html Details are :Local Author: After exporting package , i see like this:  synonymn.txt is under filters folder. I created damAssetLunce.xml under my projects apps/oak-index <?xml version="1.0" encoding="UTF-8"?><jcr:root xmlns:oak="http://jackrabbit.apache.org/oak/ns/1.0" xmlns:dam="http://www.day.com/dam/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" xmlns:rep="internal"compatVersion="{Long}2"async="async"jcr:primaryType="oak:Unstructured"type="lucene"><aggregates jcr:primaryType="nt:unstructured"><dam:AssetContent jcr:primaryType="nt:unstructured"><include0jcr:primaryType="nt:unstru

Hello everyone, It's time form me to ask a new question :-):Whenever I create an assert from a pdf file, the following error occurs in error.log: [Thread-72] com.day.cq.dam.core.impl.ui.preview.FolderPreviewUpdaterImpl error while executing folder thumbnail update job: /content/dam/mypath/apdffile.pdfjava.lang.IllegalArgumentException: width or height <= 0at com.day.image.Layer.init(Layer.java:3156) [day-commons-gfx:2.1.48]at com.day.image.Layer.<init>(Layer.java:490) [day-commons-gfx:2.1.48]at com.day.cq.dam.core.impl.ui.preview.FolderPreviewGenerator$FolderPreviewCreator.createPreview(FolderPreviewGenerator.java:292) [com.day.cq.dam.cq-dam-core:5.11.394]at com.day.cq.dam.core.impl.ui.preview.AssetDrivenFolderPreviewGenerator.generate(AssetDrivenFolderPreviewGenerator.java:245) [com.day.cq.dam.cq-dam-core:5.11.394]at com.day.cq.dam.core.impl.ui.preview.FolderPreviewUpdaterImpl.updateFolderThumbnail(FolderPreviewUpdaterImpl.java:151) [com.day.cq.dam.cq-dam-core:5.11.

AEM Workflows : How to Implement Parallel Approvals by ICF Next Engineering Abstract What is Workflow in AEM? Workflows enable you to automate Experience Manager activities. Workflows consist of a series of steps that are executed in a specific order. Each step performs a distinct activity such as activating a page or sending an email message. Workflows can interact with assets in the repository, user accounts, and Experience Manager services. Therefore, workflows can coordinate complicated activities that involve any aspect of Experience Manager. Business Use case The core business use case is, as an author I should be able to add ‘n’ number of reviewers (AEM Users) to the workflow, and every user must approve or deny the request to complete the workflow. Read Full Blog AEM Workflows : How to Implement Parallel Approvals Q&A Please use this thread to ask the related questions.

We are using the AEM Forms HTML5 capability to put a large number of XDP based forms online. Some of the forms contain common bits of text content (like an official brand name, contact email address or phone number) which we want to centrally manage so changes can be updated for all forms in one go.  I had a look around, and saw that data from external sources can be passed into the form using data or dataRef parameters, but this seems very much focussed on binding the data to fields, rather than plain content. Whats the best way to bind external data to content in the form? I have seen this done in pure XDP forms using span elements with xfa:embed 'binding' to floating fields, but this doesn't seem to work in HTML5 forms (perhaps its not supported).  

How to access AEM page timeline through programmatically. Is there any APi available.

Upgraded MacOS to Monterey. Now when using AEM in Chrome (or any other browser), the components list is ghosted - no text, but you can see a hover. If you drag & drop the hover onto a page, it doesn't work. HELP! 

I am working in the Customer Invoice form template where my table(Dynamic) is overflowing even though I have wrapped my table in a sub-form and made the allow page breaks true in the necessary locations. When the data is large, the table is getting started on the second page, making the first-page blank, and on the second page, it is overflowed for the first line item, and for the second line item, everything looks good.I have tried changing the Allow page breaks and Repeat rows, but it doesn't work.Can someone help me with this, please? Please find the below link to access the form and XML data that I used for checking.XDP File XML   Thanks.

Headless Getting Started Guide by Adobe Abstract The Headless Getting Started Guides lay out a simple path for for creating, managing, and delivering experiences using AEM as a Cloud Service in five steps for users who are already familiar with AEM and headless technology. Each guide builds on the previous, so it is recommended to explore them thoroughly and in order. Creating a Configuration Creating a Content Fragment Model Creating an Assets Folder Creating a Content Fragment Accessing and Delivering Content Fragments Audience The tasks described in the Headless Getting Started Guides are necessary for a basic end-to-end demonstration of AEM’s headless capabilities. Anyone with administrator access to a test AEM instance can follow these guides to understand headless delivery in AEM, though someone with developer experience is ideal. Read Full Blog Headless Getting Started Guide Q&A Please use this thread to ask the related questions.

AEM Headless Developer Journey by Adobe Abstract Start here for a guided journey through the powerful and flexible headless features of AEM, their capabilities, and how to leverage them on your first headless development project. This journey provides you with all the AEM Headless Documentation you need to develop your first headless application. Introduction Headless implementation forgoes page and component management as is traditional in full stack solutions and focuses on the creation of channel-neutral, reusable fragments of content and their cross-channel delivery. It is a modern and dynamic development pattern for implementing digital experiences. AEM Documentation Journeys A Documentation Journey ties together many different and perhaps complicated topics and features by providing a narrative that helps the reader, who can be new to AEM, understand and solve a business problem from beginning to end, while assuming minimal prior topic or AEM knowledge. Documentation Journeys

Abstract:Indexing is the key for the queries to perform better. Based on the way Oak indexes the content(behind the scene), indexing modes are defined. Major index types available are Property Index, Lucene Index, Solr Index which works based on the indexing modes. Blog content:http://myaemlearnings.blogspot.com/2020/05/indexing-in-aem-indexing-modes-and.html

Headless Development for AEM Sites as a Cloud Service by Adobe Abstract Learn how AEM as a Cloud Service’s powerful headless capabilities like Content Models, Content Fragments, and the GraphQL API work together to enable you to manage your experiences centrally and serve them across channels. Overview Headless implementation is increasingly becoming important for delivering experiences to your audience is, wherever they are and regardless of channel. Headless implementation forgoes page and component management as is traditional in full stack and hybrid solutions and focuses on the creation of channel-neutral, reusable fragments of content and their cross-channel delivery. It is a modern and dynamic development pattern for implementing web experiences. Comparing Headful and Headless This document focuses on the full headless implementation model of AEM. However headful versus headless need not be a binary choice in AEM. Headless features can be used to manage and deliver your cont

Headful and Headless in AEM by Adobe Abstract Adobe Experience Manager projects can be implemented in both headful and headless models, but the choice isn’t binary. AEM offers the flexibility to exploit the advantages of both models in one project. This document provides and overview of the different models and describes the levels of SPA integration. Overview AEM offers powerful tools to manage both the creation of content and its delivery in one platform. This is a traditional “headful” model of content management, where the content authors and developers work on the same platform to deliver the experiences to the content consumers. AEM can also be used to simply manage content, allowing presentation and delivery of the content to be managed by another platform. This is the “headless” model of content management, where the content authors and developers work on different platforms to deliver experience to the content consumers. But this need not be a binary choice. AEM offers unp