Adobe Experience Manager Sites

AEM Cloud Service - Sample JUnit Test using AEMContext by Sreekanth Choudry Nalabotu Abstract Goal Create a simple JUnit for testing a Sling Model class. Unit test checks if the model class function returns content in JCR as-is... Create Sling Model apps.experienceaem.assets.core.models.FreeFormModel package apps.experienceaem.assets.core.models; import com.adobe.cq.export.json.ExporterConstants; import org.apache.commons.lang3.StringUtils; import org.apache.sling.api.resource.Resource; import org.apache.sling.models.annotations.Default; import org.apache.sling.models.annotations.DefaultInjectionStrategy; import org.apache.sling.models.annotations.Exporter; import org.apache.sling.models.annotations.Model; import org.apache.sling.models.annotations.injectorspecific.ValueMapValue; @Model( adaptables = Resource.class, defaultInjectionStrategy = DefaultInjectionStrategy.OPTIONAL) @Exporter(name = ExporterConstants.SLING_MODEL_EXPORTER_NAME, extensions = ExporterConstants.SLING_MODEL_

Building AEM components with Sling models by Exadel Abstract Generally, contemporary AEM components are based on AEM Sling models. The pattern that allows you to use Sling models in AEM is called injection. We create fields, attach Sling injector annotations to them, add getters and, thus, receive data-filled objects. Many developers can hardly imagine how diversified the range of injectors and corresponding AEM annotations is. You can come across the standard Sling annotations. More annotations are added in the well-known ACS AEM Commons package. In addition, you can create your own custom injectors with AEM annotations. Concerning which injector annotations to use, you might think that @Inject annotation is the remedy for all injection cases since multiple tutorials tell you so. But, that’s not quite true, and, using @Inject, in particular, is less favorable. You can find evidence in the code provided by Adobe Consulting Services, or in this article offering a deep dive into Sling

Hi Team     I have a requirement in which the authors should not be able to delete the page , but they should be able to create versions of the page. As per my research , delete permission and versioning is tightly coupled. Is there any way ? I have a workaround which is mentioned here https://aemexperience.wordpress.com/2020/03/07/aem-permission-tricks-remove-delete-access-without-impacting-move/ . But other than this , is there any other way ? What is does privileges do ? I tried giving privilege as jcr:versionManagement .What does jcr:versionManagement actually do ? Can we give that only if the user has delete permission on the node ? TIA Veena ✌

How to identify a user last logged in into AEM , In the given scenario AEM is connected with LDAP or IDP and the users are synced into AEMMy POVEven if the users are authenticated in LDAP or IDP crx token will be created in AEM .So can we try to get a valid crx token time as the last login time?Please share which API can help to achieve this?

One of the ways a content fragment can be consumed outside AEM is assets api.However when getting content fragment via assets api, if there is a content reference field (image/video) then the json export has /content/dam path for that Image/video.When using scene7 this should be ideally scene7 url.Any thoughts on how this can be achieved? 

There is no sample/reference for usage of fragment in GraphQL query with respect to Content Fragments Schema in the official docs - https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/headless/graphql-api/sample-queries.html?lang=en I was able to arrive at this query by examining the Docs section in GraphiQL local IDE that the result of Query testList is TestModelResults. Hence created fragment out of the same.  fragment on TestModel (the one you did) will be able to output the OOTB/standard variables like _path/_typename not the custom/dynamic ones(headline)

We would like to customize the POST servlet response in case of the invalid servlet response, how can we customize this? OOTB response for the invalid servlet (/bin/testpost/rest) is likeHow can we customize invalid POST servlet Response<html><head><title>Error while processing /bin/testpost/rest</title></head><body><h1>Error while processing /bin/testpost/rest</h1><table><tbody><tr><td>Status</td><td><div id="Status">500</div></td></tr><tr><td>Message</td><td><div id="Message">org.apache.sling.api.resource.PersistenceException: Unable to create node at/bin/testpost</div></td></tr><tr><td>Location</td><td>/bin/testpost/rest</td></tr><tr><td>Parent Location</td><td>/bin/testpost</td></tr><tr><td>Path</td><td><div id="Path">/bin/testp

HiI need to create a new RTE plugin which can pull the custom font-icons under admin screen etc/acs-commons/lists similar tohttp://localhost:4502/miscadmin#/etc/acs-commons/lists/font-awesome-icons List should show the preview of icons like it does at regular dialog level. At least a drop-down list like stylesPlease let me know the better approach or any proven reference developments on itTIA

I have a requirement like two images in a dialog should return the unique alt text with respective there descritption Went for core component there is only one image using there while doing the custom component I'm not able to return or show the unique after changing the file reference of the two images  Please provide me any reference to achieve this approach  

Hello all,I have created a content fragment model and enable the graphql endpoint for the same & a react component to fetch data. This setup is working fine.Now I wanted to use the same component  for a different site, but the problem is graphql fetching the data from all content fragment created using the same model.My question isCan I create different endpoints for different structure using the same content frag model. for exampleendpoint1 fetch data from /content/site1 onlyendpoint2 fetch data from /content/site2 onlybut both use a same content fragment model.@kautuk_sahni Any suggestions or alternatives are welcome.

Social Login with LinkedIn - Adobe Experience Manager (AEM) by Albins blog Abstract Social Login with LinkedIn - Adobe Experience Manager (AEM) Social login is the ability to present the option for a site visitor to sign in with their social accounts like Facebook, Twitter, LinkedIn and etc. AEM supports OOTB Facebook and Twitter Social logins but LinkedIn login is not supported OOTB and need to build custom Provider to support the log in flow for websites. AEM internally uses the scribejava module to support the Social login flows, scribejava supports multiple providers and both OAuth 1.0 and OAuth 2.0 protocols. The scribe version shipped with AEM won’t support the LinkedIn OAuth 2.0 authentication flow but OAuth 1.0 is supported. This tutorial explains the steps and the customization required to support the LinkedIn social login in AEM as Cloud version, the same should work with minimal change for other AEM versions. PREREQUISITES 1.LinkedIn Developer Account 2.AEM as Cloud Publ

I have a CTA component. I need to show 2 separate instances of CTA in a component. The component dialog has 2 tabs - Primary CTA and Secondary CTA. The blue is showing 2 instance but both are referring to the same content. What am I doing wrong? cq_dialog.xml <primarycta jcr:primaryType="nt:unstructured" jcr:title="Primary CTA" sling:resourceType="granite/ui/components/coral/foundation/container" margin="{Boolean}true" name="./primarycta"> <items jcr:primaryType="nt:unstructured"> <columns jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/fixedcolumns" margin="{Boolean}true"> <items jcr:primaryType="nt:unstructured"> <include jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/include" path="/apps/eb/components/content/cta/cq:dialog/content/items/tabs/items/properties/it

Hello, I was reading the embed core component documentation and it mentions that all script and style elements as well as all on* and style attributes will be removed from the output. I was wondering what the best way to include styles would then be.  I was checking for the style option on the component but it doesn't seem to be available or to be as dynamic as we hoped for (based on the documentation)

Abstract of Adobe Summit 2022-A Magnificent Experience by NextRow Digital Abstract With the ever-evolving marketing dynamics, it is very important for marketers and businesses to be up to date with the latest trends and advancements in marketing strategies, technologies, and practices. Adobe Summit 2022 concluded successfully recently. The summit had over 200 informative sessions covering a wide array of topics including the latest trends, practices, developments in marketing and advertising technologies as well as success stories. Well-known personalities from various fields of work were featured as keynote speakers at the event. Fun and Engaging Keynote Session In the opening keynote session, Shantanu Narayen shared insights on customer engagement and personalization at scale. As changing customer expectations are taking a significant place in business conservation, it becomes imperative to know how businesses should engage with customers, deliver digital experiences and personaliz

Building a Project in AEM 6.5 with React Integration by Chiran Kumar, Embitel Abstract React is the most favorite programming language amongst front-end developers ever since its release in 2015. Adobe Experience Manager (AEM), one of the sought-after Content Management Solutions (CMS), is preferred by most companies across the globe. Imagine the kind of impact it is going to make when both are combined; they will surely bring incredible changes in websites and mobile applications. Not many know that installing AEM on local and integrating React for the front- end is pretty simple. Now even AEM as a cloud service has react as inbuilt program into its archetype as part of Adobe’s best practices known to its Headless CMS architecture. Introduction AEM has multiple options for defining headless endpoints and delivering its content as JSON. Building a React JS app in a pure Headless scenario. JavaScript Object Notation (JSON) is strictly a text-based format used to represent structure

What Makes Adobe Experience Manager (AEM) the Preferred CMS Tool for Enterprise Users by Swati Saini Abstract Customer experiences are key to business success, which is why businesses are always on the lookout for ways to enhance their user experiences. Leveraging digital content sources like documents, images, infographics, videos, and apps is an effective way to do this, leading to stronger brand-customer relationships. However, delivering relevant and personalized content to users at each stage and across multiple channels requires robust and multifaceted digital solutions. This is where AEM (Adobe Experience Manager) comes into the picture. In this blog post, we will discuss in detail what AEM is and why it is a preferred CMS platform for businesses that are ever-evolving and ever-expanding. Ready? Let’s get started! What is Adobe Experience Manager? AEM is a content management system offered by AEC (Adobe Experience Cloud). This tool enables easy and dynamic digital asset

Enhancing Asset Management Capabilities with Adobe Digital Asset Management by Swati Saini Abstract Digital assets are indispensable valuables for every business. And as the business grows, the volume of these assets also scales, making it harder for you to manage them well. From siloed asset storage to poor version control and digital rights limitations, there are multiple challenges that businesses have to deal with for their digital assets management. In fact, according to a report[ii], marketers spend over 60% of their time retrieving information or restructuring lost assets. Using a Digital Asset Management (DAM) system might be the best solution to organize and manage your assets as it can help you: – Organize Content in One System – Monitor Content Effectiveness – Integrate MarTech Stack – Consolidate Redundant Tools – Ensure Brand Consistency In this blog post, we’ll discuss the DAM in Adobe Experience Manager (AEM) and how the Digital Asset Management (DAM) system in AEM

What are Custom HTML Elements? | How to use Custom HTML Elements in AEM? by Albin Issac Abstract In this post, let us explore what Custom HTML Elements are and how to use Custom HTML Elements in AEM. Custom Elements allow web developers to define new types of HTML elements.Once a custom element is defined, we can use it on par with built-in HTML elements. Some of the important features are enabled by Custom HTML elements. Define new HTML/DOM elements Create elements that extend from other elements Logically bundle together custom functionality into a single tag Extend the API of existing DOM elements Web Components uses Custom HTML Elements as one of the building blocks to enable reusable custom elements(Components). Rules on creating custom elements: The name of a custom element must contain a dash (-). So , and are valid names. You can’t register the same tag more than once. Attempting to do so will throw a DOMException Custom elements cannot be self-closing(), Always write a closi

Hello,This may seem like a bit of a silly question, but is there any way to use Target Server side alongside AEM? I would not think it is possible since I am not sure where one could "hook" the usual server-side logic (calls to Target's Delivery api), but not sure if I am missing something?

Hi All, We have a servlet endpoint that returns assets that contain a metadata property product_id_1. We have created a custom index called damAssetLucene-7-custom-7 that includes this property. We have recently added about 60,000 assets from Scene7 into AEM prod author instance with product_id_1 property populated. Ever since our servlet is erroring out with http 503 response. When I look at the logs, I do not see any error messages but I do see the below warning message:08.04.2022 15:42:57.814 [cm-xxxxxxxxxx-aem-author-64c9b549b6-l5tqf] *WARN* [99.64.83.187 [1649432402844] GET /bin/xxxxxxx/getProductImages HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.search.spi.query.FulltextIndex$FulltextPathCursor Index-Traversed 40000 nodes with filter Filter(query=select [jcr:path], [jcr:score], * from [dam:Asset] as a where [jcr:content/metadata/product_id_1] is not null and isdescendantnode(a, '/content/dam') /* xpath: /jcr:root/content/dam//element(*, dam:Asset)[(jcr:content/metadata

Hi, We are trying to use editable templates to represent a structure similar to the following: Container A    Container B        Container C    Container B *         Container C * At the different levels in the hierarchy we want. to set a policy to allow a particular set of components consistently. For example: * At container A level just a container is allowed* At container B level, a container and breadcrumb is allowed* At container C level, the carousel is allowed It is important to note (and where our problem lies) that the number of Container B and Container C items is flexible, there could be be number of these containers.The policies work as expected until we get to the second instance of Container B marked with an asterisk. For this component (and container C below it) we see that the policy of the root container (Container A) is applied. Note that this is a dummy example so that it c

@dmanibabu if I am getting your question correctly, you are consuming a asset in AEM Site/s and you want localized asset title without making any change in asset path(in DAM). If that is the case one option is customized image component for dc:title field.  In image model you should be able to customize dc:title based on local. such as - 1. add a custom field - local = "localstring"2. get the custom field in image model and accordingly localize the dc:title string. Need a custom component of two images in a dialog ... - Adobe Experience League Community - 448099

Cloud Manager FAQs by Adobe Abstract This document provides answers to the most frequently-asked questions about Cloud Manager in AEM as a Cloud Service. Is it possible to use Java 11 with Cloud Manager builds? Yes. You will need to add the maven-toolchains-plugin with proper settings for Java 11. The process is documented here. For example, see the wknd project sample project code. My build fails with an error about maven-scr-plugin after switching from Java 8 to Java 11. What can I do? Your AEM Cloud Manager build may fail when attempting to switch the build from Java 8 to 11. If you encounter the following error, then you need to remove maven-scr-plugin and convert all OSGi annotations to OSGi R6 annotations. [main] [ERROR] Failed to execute goal org.apache.felix:maven-scr-plugin:1.26.4:scr (generate-scr-scrdescriptor) on project helloworld.core: /build_root/build/testsite/src/main/java/com/adobe/HelloWorldServiceImpl.java : Unable to load compiled class: com.adobe.HelloWorldS

A modern web experience on Adobe Experience Manager with WorkBox by Kalyanaraman & Salvatore Abstract If you are a technical lead or digital marketing analyst interested in providing a modern Web experience to your Adobe Experience Manager (AEM) web application and have been looking for your options in doing so, then you have come to the right article. This will cover what Progressive Web Apps (PWA) are and what you need to create a PWA in AEM leveraging the WorkBox library through configuration, without coding. Why PWA? # Progressive Web Apps leverage what the modern web can do. They are installable on your device, load quickly, with subsequent visits loading instantly. They respond to input quickly. They work well on an unreliable connection or when offline. PWAs use modern APIs to provide an engaging app-like experience with an optional full screen UI, background updating, and offline access to data. From web app to Progressive Web App. To enhance a web app into a Progressive

Ingesting Data from Adobe Experience Manager (AEM) for Search & Discovery by Algolia Abstract Businesses spend a lot of time and resources developing content that can support the sale of a product, promote their brand and thought leadership, educate their users, or answer frequently asked questions. It is essential that they can organize their content to provide the most relevant information to a given persona. While this can end up being a manual process for marketers and digital publishers, smarter search and discovery platforms like Algolia can make this easier and drive stronger engagement. Algolia is an API-first solution that easily integrates with both monolithic and headless platforms, including Adobe’s popular CMS, Adobe Experience Manager (AEM). As we’ve seen more and more Adobe customers use Algolia on top of AEM to manage and surface their content, we wanted to discuss the three ways they connect these two systems: through APIs, partner-built integrations, and the Alg