Adobe Experience Manager

Use this thread to ask any questions related to Creating a review workflow in the AEM Forms course on the Experience League. Experts are monitoring this thread to ensure your questions are answered.

We are using SAML to authentication users in our Communities environment but by default SAML creates the users in /home/users but for communities we need them in /home/users/community.Is there a way to change the path (via a config or a java hook) to change where SAML saves these user accounts?When the user is created in /home/users they cannot see other usernames of posters (only unknown user) because the ACL property for everyone to access the profile lives on the community folder. I could add this to the users folder too but this would seem like a security risk.Tried making a workflow to move the node that runs on rep:User Created but it fails with the following error:OakConstraint0063: Attempt to manually create or change a token node or it's parent.

Make integrations simple by cognifide Abstract Integration with other systems is one of the most complex parts of software delivery. Is there a silver bullet that can address issues like flaky tests, unstable environments and non-trivial bugs that slow down the development? It is very rare to have an application that is not integrated with other systems. This also applies to AEM application development. In many cases, we don't have control over those other parties. Such APIs are maintained by other teams or even companies. Sometimes they are not maintained at all. On the other hand, they might not exist when we start our delivery. Those external APIs might be unstable, which can lead to unpredictable behavior of the entire system. It can be unclear what is the root cause of a bug: if it was introduced in the external API or our application. E2E and integration tests that we have in our project might fail from time to time without a straightforward reason (timeout, network issues, uns

Debug Adobe Launch on Any Browsers with Charles by engineering.icf Abstract When managing code with Adobe Launch, it’s critical to be able to test changes before publishing. To make sure changes work as expected in a production environment, it’s helpful change the Launch library, allowing you to see how your dev or stage library will work on your production site. There are some great tools like Launch Switch available from Search Discovery (available here). The downside is that these tools are only available on Google Chrome. That means you can’t test on other browsers like Safari, IE, Firefox, or others. Charles is powerful software that can monitor and manipulate all of the internet activity of your computer. Using this functionality, we can change the content of your sites pages on your computer on the fly to request different Launch libraries, allowing you to test any library on your production site. Unless you are a developer wizard, Charles can be difficult to learn, so here ar

I am working on a component which requires an image to be uploaded using fileupload widget inside a coral multi-field  Following is the dialog configuration:<?xml version="1.0" encoding="UTF-8"?><jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0"    jcr:primaryType="nt:unstructured"    jcr:title="Custom Multi-field Component"    sling:resourceType="cq/gui/components/authoring/dialog">    <content        jcr:primaryType="nt:unstructured"        sling:resourceType="granite/ui/components/coral/foundation/container">        <items jcr:primaryType="nt:unstructured">            <tabs                jcr:primaryType="nt:unstructured"                sling:resourceType="granite/ui/components/coral/foundation/tabs"                maximized="{Boolean}true">                <items jcr:primaryType="nt:unstructured">                    &

I am working on an AEM SPA Angular application which is running on AEM 6.4.7. Using the typical implementation where the Angular components are mapped to AEM components. To avoid not exposing the /content directory on the URL, I have resorted to using vanity URLs and this was my approach:Changes made on AEM:- OSGi config for Apache Sling Resource Resolver Factory: Added the URL Mapping: /content/awesome/application/home/-/homeAngular:- The app router redirects to /home.html- All URLs on the application point to something like: /home/something/something-else.html  and /home/another-thing/more-things.htmlproxy.aem.conf.json:The configuration for this file looks like this:[ { "context": [ "/**.model.json", "/content/**/**.jpeg", "/content/**/**.jpg", "/content/**/**.png", "/content/**/**.PNG", "/content/**/**/**.png", "/content/**/**/**.PNG", "/content/**/**/**.jpeg", "/content/**/**/**.jpg", "/content/**/**/**.pdf" ]

Hello, I have created a custom experience fragment template because of our need. I am using OOTB clould config to export experience fragment content to target. The export to target is successful and in target i can see the content through externalizer urls.  Now when i try to use that experience fragment offer into activity, it doesn't include the experience fragment content which i can access through externalizer urls instead it give me below  <!DOCTYPE HTML><html><head><meta http-equiv="content-type" content="text/html; charset=UTF-8"/><link rel="stylesheet" href="/etc.clientlibs/foundation/clientlibs/main.css" type="text/css"><script type="text/javascript" src="/etc.clientlibs/clientlibs/granite/jquery.js"></script><script type="text/javascript" src="/etc.clientlibs/clientlibs/granite/utils.js"></script><script type="text/javascript" src="/etc.clientlibs/clientlibs/granite/jquery/granite.js"></sc

How to Choose the Right Approach When Creating Adobe Target Offers by Bounteous Abstract If you have both Adobe Experience Manager (AEM) and Adobe Target licenses, you have a few options of where and how you can create offers. In my previous blog posts, I discussed how to integrate AEM with Target, both for AEM 6.4 and AEM 6.5. Now the question is when to leverage the integration and when does it make sense to use the Target interface instead. Targeting Approaches Before attempting to answer that question, I want to discuss the differences between the three approaches. Approach One: Target UI-Only The most obvious approach is to leverage the plain old Target interface for all your targeting and personalization needs. With it, you’ll have the full suite of Adobe Target features at your disposal. Most commonly for websites, you’re going to use the Visual Experience Composer (VEC) to create your experiences. This method works regardless of which content management system (CMS) you use

Debug Adobe Launch on Any Browsers with Charles by Sam Kutscha Abstract When managing code with Adobe Launch, it’s critical to be able to test changes before publishing. To make sure changes work as expected in a production environment, it’s helpful change the Launch library, allowing you to see how your dev or stage library will work on your production site. There are some great tools like Launch Switch available from Search Discovery (available here). The downside is that these tools are only available on Google Chrome. That means you can’t test on other browsers like Safari, IE, Firefox, or others. Charles is powerful software that can monitor and manipulate all of the internet activity of your computer. Using this functionality, we can change the content of your sites pages on your computer on the fly to request different Launch libraries, allowing you to test any library on your production site. Unless you are a developer wizard, Charles can be difficult to learn, so here are st

I was trying to create a home page template, which would have iparsys for header, footer and body. My plan is that, header and footer could be added from parent component in authoring mode. I have added the iParsys but these does not display in authoring mode, however if I put some hardcoded text, that is being displayed. For your reference, I am pasting my code here. home-page template (components/structure/home-page):.content.xml code:<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" jcr:primaryType="cq:Component" jcr:title="GLPG Forms Home Page" sling:resourceSuperType="glpg-forms/components/content/page" componentGroup=".hidden"/> home-page.xml<!DOCTYPE HTML> <html data-sly-use.page="com.adobe.cq.wcm.core.components.models.Page" lang="${page.language}" data-sly-use.h

Use this thread to ask any questions related to the How to add commerce capabilities to your AEM Site on Experience League. Experts are monitoring this thread to ensure your questions are answered.

We are planning to migrate from AEM 6.4 to AEM 6.5 with in-place upgrade. what are the key areas that we would need to give a focus during migration. Is there any guidance from adobe ?

Use this thread to ask any questions related to the Create custom asset renditions by extending Asset Compute microservices course on Experience League. Experts are monitoring this thread to ensure your questions are answered.

Hello,I am trying to modify metadata/dc:description when I create an asset, but changes does not commited on CRX.My asset is a PDF and my code:Asset assetFitxer = assetManager.createAsset(pathDAM, inStream, mimeType, true);Resource metadataRes = assetFitxer.adaptTo(Resource.class).getChild("jcr:content/metadata");ModifiableValueMap map = metadataRes.adaptTo(ModifiableValueMap.class);map.put("dc:description", newCode);ResourceResolver rs = metadataRes.getResourceResolver();rs.commit();--> PDF's file has own metadata and I need to modify dc:description If I did commit before to change metadata and after it, changes do not save yet. I think workflow dam asset does not end before I try to change dc:description, so metadata field has original value.  Any suggestions?Thanks! 

User identification and Adobe Target by Pedromonjo Abstract A year ago I wrote about Declared IDs. I briefly mentioned then an issue that arises with setting these IDs: lazy loading and Adobe Target. However, I know that I did not explain too much about the issue. In this post I will get into more detail. Order of execution The typical order of execution of the Adobe tools on a page is as follows: 1. Request ECID on the first page of the first visit or read the stored value 2. Call Adobe Target 3. Apply changes to the DOM according to the response from Target 4. Call Adobe Analytics 5. Call Adobe Audience Manager or use server side forwarding. Steps 1 & 2 must happen inside the HEAD section of the HTML page. Expect the unexpected if moved outside. Steps 4 & 5 can be moved to the very bottom of the page, just before the tag, although you could put them elsewhere in the HTML. Number 3 takes place automatically as the page loads. What happens when you have a declared ID? You

AEM — JMX Solution to delete packages programmatically by Pradeep Moolemane Abstract Package — A package is a zip file holding repository content in the form of a file system serialization that enables easy to use and edit files & folders. Package also contains vault information including filter definition, import configuration. Additional content properties can be included in the package such as description, a visual image or an icon. Imp: Packages are current version of content repository at the time package built. Following action can perform on/with packages. Create package, preview package content, build package, view package information, view package content, modify package definition, rebuild package, download/upload packages etc. Create package: Go to Package manager -> create package -> provide information — Package name, version, group. Minimum information package name must be given to create package. And by default, packages created under “my_packages” group. W

Commerce Integration Framework Introduction by Adobe Docs Abstract Adobe’s Commerce Integration Framework (CIF) is Adobe's recommended pattern to integrate and extend commerce services from Magento and other third party commerce solutions with the Experience Cloud. This enables Adobe Customers to deliver extraordinary and personalized omnichannel shopping experience based on state-of-the-art technology. The Commerce Integration Framework is an add-on module for AEM and provides a set of authoring tools, components, and a reference storefront to accelerate integrations between AEM and commerce solutions. CIF is supported on all AEM offerings (On-Premise, Managed Services, & Cloud Service). There are some differences in the deployment model for the different AEM offerings. This set of documentation provides details for CIF on AEM On-Premise and AEM Managed Service. For more details on CIF on Cloud Service, refer to AEM Commerce as a Cloud Service CIF Benefits 1. The main benefits

Please guide me to some resources/documentation regarding the best approach for migrating AEM application from on-prem to Azure cloud. Apart from packaging and and installing applications on cloud what all should be considered?

AEM - Embed Component by Adobe Docs Abstract The Core Components Embed Component allows embedding external content in an AEM content page. Usage The Core Component Embed Component allows the content author to define selected external content to be embedded within an AEM content page. In addition, there is an option to define free-form HTML to be embedded as well. 1. The component's properties can be defined in the configure dialog . 2. Defaults for the component when adding it to a page can be defined in the design dialog Version and Compatibility The current version of the Embed Component is v1, which was introduced with release 2.7.0 of the Core Components in September 2019, and is described in this document. The following table details all supported versions of the component, the AEM versions with which the versions of the component is compatible, and links to documentation for previous versions. Sample Component Output To experience the Embed Component as well as see examples of

Hi Team, Is it possible to disable  notification mail for a specific workflow, I have gone through the Day CQ workflow email notification service in configuration manager console and disabled "notify on abort" and "notify on complete" doing so will disable notification mails for all the workflows , could any one let me know how to disable mail notification for a specific workflow.Thanks in advance,Jhansi.

Simplifying the Data Science Lifecycle with Adobe Platform Experience by Stories by Jaemi Bremner on Medium Abstract In this post, we explore how we can take a business problem to potential business outcomes using Adobe Experience Platform Data Science Workspace to quickly connect to data and build, experiment, validate and deploy machine learning models at scale. While the model building itself has several steps like data cleaning, data preparation, feature engineering, and ultimately, model building, Adobe Experience Platform provides a much broader and wider end-to-end framework to accelerate the data-to-insights process, perform experiments through hyperparameter tuning, and creating a custom, personalized and intelligent publishing service which can be shared in just a few clicks. This service can be monitored, and retrained for continuous optimization of personalized experiences The end-to-end machine learning framework in Adobe Experience Platform can be broken down into five

How to Choose the Right Approach When Creating Adobe Target Offers by Insights Feed Abstract If you have both Adobe Experience Manager (AEM) and Adobe Target licenses, you have a few options of where and how you can create offers. In my previous blog posts, I discussed how to integrate AEM with Target, both for AEM 6.4 and AEM 6.5. Now the question is when to leverage the integration and when does it make sense to use the Target interface instead. Targeting Approaches Before attempting to answer that question, I want to discuss the differences between the three approaches. Approach One: Target UI-Only The most obvious approach is to leverage the plain old Target interface for all your targeting and personalization needs. With it, you’ll have the full suite of Adobe Target features at your disposal. Most commonly for websites, you’re going to use the Visual Experience Composer (VEC) to create your experiences. This method works regardless of which content management system (CMS) you

Dispatcher Cache Invalidation - Programmatically AEM Dispatcher : The Dispatcher is Adobe Experience Manager's caching ... by AEM Guide by Saumya Abstract AEM Dispatcher : The Dispatcher is Adobe Experience Manager's caching and/or load balancing tool that helps realize a fast and dynamic Web authoring environment. In a load balancing role, the Dispatcher distributes user requests (load) across different AEM instances (renders). For caching, the Dispatcher works as part of an HTTP server, such as Apache, with the aim of storing (or "caching") as much of the static website content as possible and accessing the website's layout engine as infrequently as possible. For caching, the Dispatcher module uses the Web server's ability to serve static content. The Dispatcher places the cached documents in the document root of the Web server. Dispatcher Caching: 1. The Dispatcher uses the web server's ability to serve static content. The Dispatcher stores cached documents in the web server’s

Just need a suggestion on below points. How I can add bootstrap css in angular SPA project - I have added bootstrap under client libs but not able to load in use in my angular project (ui.frontend).  

Cloud Manager meets Jenkins by Cognified Abstract The popularity of cloud infrastructures and serverless designs is still going up. Adobe doesn't fall behind and proposes a myriad of cloud tools meant to revolutionize ways of working with AEM projects. The new solutions bring lots of changes to both developing and deploying the code. DevOps engineers have to face a challenging task of adapting the current deployment pipelines into the new, cloud-based approaches based on Adobe's Cloud Manager. Introduction First, let's delve deeper into the subject of code deployments and the way it's done with Cloud Manager. Usual deployment pipelines Deploying your code is all about making your software available to the end-users. However, as the project you're working on is growing you might need to perform multiple additional actions revolving around this process. This is where the concept of deployment pipelines comes into play - in most real-world scenarios deploying software is much more than