Adobe Experience Manager Sites

Hello Community.First time here 🙂We have a requirement in which we need to clear dispatcher cache without publishing the page. We tried flush service options but it is not working for us. Looking for solution options to achieve this.Thank you

 In assets UI we have added few custom columns in list view. when we select on any article and then click on export metadata it will export those columns of that article into csv. so we are not able to get the custom columns added into csv.Here are the list of columns in list view.  Here are the list of columns in the exported csv So, its showing only few columns in the exported csv. we want all the custom columns to be added into that csv and also remove unwanted columns while exporting.

Hi,I am facing the problem below.I have a workflow to publish a content on a specific node when it is updated.On the other hand, I have an action on my bundle that has to be executed when this content is activated.I am following this tutorial below. but my class is not been called when workflow is completed. I realized that this class is using some deprecated method.Adobe CQ Help | Creating Replication Event Handlers for Adobe Experience Manager Has someone implemented this on AEM6.4? If so, is there a most current tutorial?My class does not have errors, but does is not working as well.I appreciate any help.Thanks in advance.

AEM Security Best Practices: Awakening to the Need for Better CybersecurityAdobe Experience Manager takes security seriously since Adobe, at large,  is more than aware just how much is at stake. The average cost of a data breach amounts to $4.24 million according to a 2021 IBM report. AEM security best practices are woven into AEM software so that teams can prevent, quickly detect, and eliminate even the slightest deviations.In this article, you’ll learn what contributes to the overall Adobe AEM security, determine what cyber threats any CMS such as AEM can face, and uncover Adobe security best practices.  Placing emphasis on AEM security best practicesAdobe Experience Manager has established partnerships with software development companies, leading researchers, and security research institutions to keep up with the latest vulnerabilities and cyber threats. To put a few on your radar, Adobe collaborates with:Information Systems Security Association (ISSA)Open Web Application

Details Hear from the AEM Product team, and learn about the features and innovations for the latest release of Adobe Experience Manager Assets Essentials, Sites, Screens, Forms, and Cloud Foundation. Prerelease TIP: Learn more about prerelease and how to enable it. Forms Global XCI Support for DOR Generation Invisible reCAPTCHA Form Data Model Connections Production Assets Essentials CCE Pro with Work Management and Assets Essentials Permission Management Public Link Sharing Sites The translatable field in the content model Screens Folder management for displays Default activation schedule for channels Forms Increased Form Conversion Support Cloud Foundation Web-tier Config Pipeline Repository Browser Check-size Guardrails in Content Transfer Tool Release Overview Video Q&A Please use this thread to ask the question related to this release. See all the Previous Releases here and Current Release Notes here.

Running junit in the latest Eclipse (Eclipse IDE for Enterprise Java and Web Developers, version 2022-03 (4.23.0)) fails to adaptTo resource, instead it returns null.Same test in the same workspace just in older Eclispe (Eclipse IDE for Enterprise Java Developers, 2019-03 (4.11.0)) executes test with no problem. final SmallCarousel actual = ctx.request().adaptTo(SmallCarousel.class);"actual" ends up to be null after execution of this line... When debugging in older Eclipse I could see that MockAdapterManagerImpl.getAdapter returns factory for SmallCarousel in a call to, final Map<String, List<AdapterFactoryDescriptor>> factories = getAdapterFactories(adaptable.getClass()); Same Map in new Eclipse doesn't contain factory for SmallCarousel. Thanks

Personalization using AEM Experience Fragments and Adobe Target by Adobe Abstract With the ability to export AEM Experience Fragments into Adobe Target as HTML offers, you can combine the ease-of-use and power of AEM with powerful Automated Intelligence (AI) and Machine Learning (ML) capabilities in Target to test and personalize experiences at scale. AEM brings together all of your content and assets in a central location to fuel your personalization strategy. AEM lets you easily create content for desktops, tablets, and mobile devices in one location without writing code. There is no need to create pages for every device—AEM automatically adjusts each experience using your content. Target lets you deliver personalized experiences at scale based on a combination of rules-based and AI-driven machine learning approaches that incorporate behavioral, contextual, and offline variables. With Target, you can easily set up and run A/B and Multivariate (MVT) activities to determine the best

Possible OSGi Bundle States in AEM by Joey Smith Abstract OSGi is one of the core technologies that Adobe Experience Manager (AEM) is built on. While it is certainly well-documented, a lot of developers have never taken the time to understand the ins and outs of what lies “under the hood” of OSGi for your AEM environment. You don’t have to be an expert in OSGi to be an expert AEM developer or systems engineer. That said, there are times when it can be helpful to understand specific aspects of OSGi. I like to think of it as the difference between knowing how to change your own oil and knowing how to rebuild your own engine; having that deeper degree of understanding can be a powerful tool when things aren’t working how you would normally expect them to. One of the common things you will come across as a developer is the need to understand the state of a bundle. These states describe specific phases of the bundle as it progresses in AEM. Below are the six states that a bundle can h

Extending Page Properties in AEM by Mayur Satav Abstract It is always one of the prime requirements for the projects to extend page properties. It helps to manage metadata and many other functionalities associated with the page.In this blog we will see how to extend page properties. Step1: Open CrxDe and go to your project package. Then select the page component node. You will see sling:resourceSuperType property copy the path associated with that property. This property points to the v2 version of the core page component. Extending Page Properties in AEM By Mayur Satav Step 2: Now paste that core page component path in the node search bar and do not forget to add /apps/ before /core/. Otherwise, it will not navigate you to that component. The complete path should look like this. /apps/core/wcm/components/page/v2/page You can refer below image for clarity. Extending Page Properties in AEM Now if you click on the page component node you will see the sling:resourceSuperType property

AEM Author, Publish & Dispatcher by Sankham MarTech Channel Abstract Video: https://youtu.be/aMMLqryokEo What is AEM Author, Publish & Dispatcher is explained in this video. Also how to debug any issue which we might get in Production instance is also explained. AEM Tutorial PlayList: https://www.youtube.com/playlist?list... 00:00 - Introduction 00:43 - Code Build Process 04:24 - Author to Publish Flow 06:48 - Replication Agents 10:54 - Page Render Flow 15:01 - Apache Rewrite Rules 16:26 - AEM Dispatcher 21:24 - AEM Issue Debugging 14:36 - Page & Templates Summary Read Full Blog AEM Author, Publish & Dispatcher Q&A Please use this thread to ask the related questions.

AEM and Magento Integration Using Commerce Integration Framework(CIF) — Local Setup (Part1) by Albin Issac Abstract The AEM and Magento are integrated using the Commerce Integration Framework (CIF); the CIF framework enables AEM to access magneto commerce instances through GraphQL API. In this post series, let us see how to set up local Magento and AEM platforms and enable the CIF framework in AEM to integrate with Magento to build the storefront in AEM. Let us start with setting up a local Magento instance. I am going to use XAMPP on windows to enable the Magento servers. Install Elastic search: The latest Magento version requires Elasticsearch or OpenSearch for indexing but not support MySQL indexing. Installed elastic search 7.17.3, https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.17.3-windows-x86_64.zip Download and Install XAMPP: As a first step, download and install the XAMPP server, including Apache, PHP, MySQL, and PHP admin. Read Full Blog AEM and

How to Implement Experience Targeting in AEM using ContextHub? by Albin Issac Abstract Content personalization in short means delivering the right content to the right person in real-time. Simple experience targeting scenario, user1 requesting the content through Firefox receives Experience A and user2 requesting the content through Chrome receives Experience B. The experience can be decided based on different rules e.g gender, age location, etc, here we are seeing the simple scenario. The targeting engine is the mechanism that drives the logic for targeted content. You can use either AEM or Adobe Target as the targeting engine, AEM provides a built-in targeting engine that processes page requests and determines the content to display. AEM as a targeting engine only supports Experience Targeting but Adobe Target should be used for A/B testing. In this post, let us see how to use the AEM targeting engine to enable the experience targeting for a web page. Setup ContextHub: ContextHu

Hello All,     We have a requirement, when we upload a pdf(say abc.pdf) to /content/dam/media/ folder, then some custom workflow we developed, creates a structure under /content/dam/media as follows./content/dam/media/<random-unique-name>/1.0/<random-unique-name.pdf>But the moment we drop any asset to /content/dam/* folder, DAM update Asset Workflow triggers and start creating renditions for /content/dam/media/abc.pdf, but by the time it completes, asset is moved to /content/dam/media/<random-unique-name>/1.0/<random-unique-name.pdf> by custom workflow,  So DAM Update Asset workflow is throwing below exceptions.30.08.2018 06:33:23.429 *ERROR* [JobHandler: /etc/workflow/instances/server0/2018-08-29_1/update_asset_118:/content/dam/media/abc.pdf/jcr:content/renditions/original] com.day.cq.dam.core.impl.RenditionMakerImpl Error while generating renditions for asset /content/dam/media/abc.pdfjavax.jcr.InvalidItemStateException: OakState0001: Unresolved conflicts in /

【問題/事象】サイトコンソール(http://localhost:4502/sites.html)では見えないページが、CRXDE Liteではリポジトリにノードとして存在し、そのノードにdeletedプロパティとdeletedByプロパティがついていることがあります。本記事では、この事象について原因と対応方法を説明します。 【環境】AEM as a Cloud Service、AEM 6.5 【対応方法】管理者ユーザーのインボックスでRequest for Deletionワークフローの通知を探し、Deactivates the pageステップとRequest for Deletionステップをそれぞれ完了にします。 【原因】公開権限のないユーザーがページを削除すると、そのページはサイトコンソールで非表示になり、Request for Deletionワークフローが始まります。次の流れのとおり、ワークフローが完了するまでページのノードはリポジトリに残っています。　1. 公開権限のないユーザーがページを削除　2. そのページはサイトコンソールで非表示になる (ページのdeletedプロパティとdeletedByプロパティが付与される)　3. Request for Deletionワークフローが始まる　4. 管理者ユーザーのインボックスにワークフロー通知が届く　5. 管理者ユーザーがワークフローステップを完了にする　6. 実際にページのノードが削除される ＜留意事項＞・上記は以下記事の抄訳/翻訳となります。KB記事タイトル(英語). The page to be deleted is hidden but remains in the repository , April 22, 2022, https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-19240.html, (参照 2022-04-25).・本記事にいただいたコメントへの返信はお約束できません。あらかじめご了承ください。

Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.6:npm (npm dependency build) on project wcax-core.ui.apps: Failed to run task: 'npm run build' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1] 1.I had installed the latest version of Node JS but getting the above error on maven build.Could anyone please help me resolve this issue.

I am trying to set the OAuth 2.0 flow for server to server communication. I am able to do the steps outlined here https://medium.com/tech-learnings/how-to-manage-the-protected-aem-resources-through-oauth-2-0-851ce4c7a5ef up until the point of getting the token back form AEM. Using the token on the next request always gives a 404 response. I have tested the manual flow to authorize the user and the JWT method as well with the same results. User is part of administrators group (just while I'm testing) so permissions are good and the scope has all permissions for /content/dam.  

Hi there,I have a very similar issue that was posted on StackOverflow (see link below), but unfortunately, I was not able to find a solution yet.https://stackoverflow.com/questions/68459743/aem-dialog-using-slingresourcetype-include-on-the-same-component-dialog-twice How I can use the following in the same dialog multiple times?<ctaLinks jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/foundation/include" path="/apps/my_project/components/base/_ctagroup/content/items/ctaLinks"/>  Assume i have 2 Tabs, and I want to be able to use this generic / global ctaLinks in both tabs.But when I use (the code snippet above) multiple times in dialog .content.xml,cta button is duplicated, so Tab 1 and Tab 2 dialog config in new component is overriding each other's value.So whenever I change the cta value in Tab 1, it also changes the cta value in Tab 2.Your help is greatly appreciated. 

i am using Adobe AEM with GraphQL and i am trying to use Fragments here (because i want to query the data with Gatsby.js, but this is not related i think).When i try to run this Query: { testList { items { typename headline } } } the result is { "data": { "testList": { "items": [ { "__typename": "TestModel", "headline": "test headline" }, { "__typename": "TestModel", "headline": "Test headline two" } ] } } } which looks fine.. BUT when i try to query with fragments, the field is getting no data (headline is null){ testList { items { __typename ...TestModelFragment } } } fragment TestModelFragment on TestModel { headline } { "data": { "testList": { "items": [ { "__typename": "TestModel", "headline": null }, { "__typename": "TestModel", "headline"

Hi All,I have  a requirement to show/ hide the HTML content on the page based on the feature flag value returned from the Adobe Target.Description:1.When the feature flag named "displayHTML" from Adobe Target is set to true , then the HTML, CSS , javascript present within the component gets rendered on the page and the flag value is set to false as default. So, can anyone please help me out with any reference or ideas inorder to achieve this implementation. Thanks in Advance!

Is it possible to add a thumbnail image for a pdf link hosting in DAM? For web page, there's a field for thumbnail image, so when we share the page link in messenger or social media, the image will show.Can we do the same for a pdf link? How? Thank you!

Hi all,When I tried to use ACS commons error handler for custom error pages, in author it is correctly routing to the error page we configured. Whereas in publisher it is showing the default error page.I've verified all the configurations, but no idea what is the issue. Please help me out.

Hello, I have a problem with AEM links rewriting. I have a set of mappings that works correctly for my site. All links in content are mapped nad works fine. The problem happened when my component (for example core components RTE) links to a page that is not published. In that case link is not mapped and I can see in cached HTML file that the link is `/content/my-site./en/not-existing` isntead of `/en/not-existing`. When I publish `not-existign` page and clear cache link is correctly mapped. Is that a new feature of AEM / Sling mappings? Can I change that ? I would like to avoid having unmapped links even if they points to 404 page.  AEM 6.5.9 Link checker transformer config:<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" jcr:primaryType="sling:OsgiConfig" linkcheckertransformer.strictExtensionCheck="false" linkcheckertransformer.rewriteElements="[a:href,area:href,form:action,img:src,link:href

Personalization using AEM Experience Fragments and Adobe Target by Adobe Abstract With the ability to export AEM Experience Fragments into Adobe Target as HTML offers, you can combine the ease-of-use and power of AEM with powerful Automated Intelligence (AI) and Machine Learning (ML) capabilities in Target to test and personalize experiences at scale. AEM brings together all of your content and assets in a central location to fuel your personalization strategy. AEM lets you easily create content for desktops, tablets, and mobile devices in one location without writing code. There is no need to create pages for every device—AEM automatically adjusts each experience using your content. Target lets you deliver personalized experiences at scale based on a combination of rules-based and AI-driven machine learning approaches that incorporate behavioral, contextual, and offline variables. With Target, you can easily set up and run A/B and Multivariate (MVT) activities to determine the best

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

Building a Project in AEM 6.5 with React Integration by 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. We have come up with a comprehensive step-by-step guide to help you out while working on AEM 6.5 and React integration. Introduction AEM has multiple options for defining headless endpoints and delivering its content as JSON. Building a React JS app in a pure Headle