Adobe Experience Manager Sites

Get the Asset meta data from the asset node in AEM by keshav chaurasiya Abstract Get the Assets meta data from the asset node in AEM sling model @Model(adaptables = {SlingHttpServletRequest.class,Resource.class}, defaultInjectionStrategy = DefaultInjectionStrategy.OPTIONAL, resourceType="myproject/components/content/image") @Exporter(name="jackson", extensions="json", options= { @ExporterOption(name = "MapperFeature.SORT_PROPERTIES_ALPHABETICALLY", value = "true") }) public class ImageModel{ private static Logger LOG = LoggerFactory.getLogger(ImageModel.class); @SlingObject private SlingHttpServletRequest request; @Inject @Via("resource") private String image; } @Inject @Via("resource") private String imageMetaData; /** * @return the imageMetaData */ public String getImageMetaData() { String url = request.getRequestURI(); Resource resource = request.getResourceResolver().getResource("/content/dam/my-project/image/image.png"); Asset asset = resource.adaptTo(Asset.

Using cURL with AEM Cloud by Prince Shivhare Abstract What is cURL? cURL is an open-source command-line tool used to perform URL manipulations. It supports a wide range of internet protocols including HTTP, HTTPS, FTP, FTPS, SCP, SFTP, TFTP, LDAP, DAP, DICT, TELNET, FILE, IMAP, POP3, SMTP, and RTSP. Downloading cURL cURL is a standard part of macOS and some Linux distros. However, it is available for almost every operating system. The latest downloads can be found at https://curl.haxx.se/download.html. Fetch the AEM as a Cloud Service Credentials Users with access to the AEM as a Cloud Service developer console will see the integrations tab in the Developer Console for a given environment, as well as two buttons. A user with the AEM as a Cloud Service Environment administrator role can click the Get-Service Credentials button to display the service credentials JSON, which will contain all the information required for the non-AEM server, including client id, client secret, private

Introducing Adobe Experience Manager’s New Headless Extension for Adobe Commerce PWA Studio by Jaemi Bremner Abstract This is the first part of a series of the new headless architecture for Adobe Experience Manager. In this post, Adobe Experience Cloud introduces its Adobe Experience Manager Headless Extension for PWA Studio that enables developers to leverage headless architectures to build app-like experiences for their customers that are fast, secure, and delightful on any device, mobile or desktop. Adobe Experience Manager provides the most innovation-friendly content tools in the market. Adobe Experience Manager enables you to more easily use and reuse your content across the web, mobile, and emerging channels such as IoT devices. Now, Adobe is introducing a new extension that enables Adobe Experience Manager authors to manage rich content and commerce experiences for the progressive web apps (PWAs) they build in PWA Studio by Adobe Commerce, powered by Magento. In this blog, we

How to handle Sling Scheduler in Adobe as a Cloud Service? by sudeshaempodcast Abstract With lot of new and fast features being provided by AEMaaCS, there are some important things we need to keep in mind while doing the implementation, one of them is cluster aware coding or develop cluster aware application. What is the need of cluster aware coding? With AEM as a Cloud Service, some things are changed and we need to keep them in mind while developing the application. The major one is, now the application will be running on cluster nodes which means instances can go down and new ones can come up any time. It will be great for authors with no downtime during the deployments but the question arises what will happen if the instance will go down during the scheduler is running? The code must be resilient especially as an instance might be stopped at any point in time. To over come this problem, we can use Sling Scheduled Jobs. If we are migrating project from 6.X.X to AEMaaCS, it is n

PDFs in AEM: Embed PDFs into Your Pages with PDF Viewer by Ben Vanderberg Abstract Content can come in a variety of formats in AEM. They could be images, videos, or even PDF documents. When it comes to PDFs, what is often the case is these PDFs are linked to and then rendered in the browser or downloaded to your computer, taking you away from the context and navigation of your own website. You also don’t get any insights into how they were interacting with PDFs other than downloading. There are a lot of common scenarios where this is the case. For example, you might see white-papers, guides, contracts, documents. If you are using AEM to power a customer portal or an intranet, you could have documents specifically related to a certain person that you want to host online. As part of AEM Core Components, there is now a new component called PDF Viewer, powered by Adobe PDF Embed API as part of Adobe Document Services. In a previous blog, I wrote in detail how you can take advantage of PD

Content Package Type Validation Forces Rethink of Standard Project Structure for Adobe Experience Manager ADOBE EXPERIENCE MANAGER by Mark Adamcin Abstract With the launch of Adobe Experience Manager (AEM) as a Cloud Service, Adobe has redefined the way content, code, and configurations are stored in AEM. The changes create a more explicitly structured project with strict enforcement, which translates to how AEM projects are set up and deployed. Let’s dive into the before and after pictures of that change, as well as providing reasoning for the changes in order to effectively deploy AEM as a Cloud Service. Prehistoric FileVault For about a decade, 2009 to the beginning of 2019, we built and deployed CQ5/AEM content packages like this, where question marks, dashed lines, and cloudy boundaries indicate areas of ambiguity, non-determinism, and opportunities to become more proficient with the Felix Admin Console. In the above diagram, we build two top-level content packages, herein labe

Listening and Handling Copy/Paste Events in Adobe Experience Manager by Sreenivas B Abstract This article will help you to do any post processing activity on copy/paste of an asset/page — here, I explain one of the important use cases which I have experienced, for which I needed this. When we integrate AEM with any cloud solution (Adobe or third party) for synchronizing assets or pages, we use some kind of reference ID for linking the content between AEM and the cloud service. For example, in the case of exporting an Experience Fragment to Adobe Target, we use Offer ID for linking the AEM XF and the corresponding offer in Adobe Target for further synchronization or updates to the offer. We usually save this reference ID in the content or metadata node of the page/asset. Now, the problem is, what if I copy/paste the asset/page in AEM for reuse? The metadata or properties also get pasted in the newly created page/asset. Now we have two assets/pages with same reference ID, which is pr

Customer Activity Hub: Blueprint for Building Extraordinary Customer Experiences with Adobe Experience Platform by Kevin Cobourn, Wendy Braun, Nick Hecht, Joel Huff, and Jody Arthur. Abstract In this post, Adobe Experience Platform introduces the fourth in its series of Digital Experience Blueprints — a whole new way to learn and understand how you can use its technology to build incredible customer experiences in real-time. The challenge in creating incredible customer experiences isn’t a lack of data. Architecting an amazing experience should be easy with all the customer data enterprises collect today. Yet doing so remains an elusive goal for many not because they don’t have the data they need, but because they cannot get that data into the right place at the right time and in a way that allows them to fully leverage it. Every day, customers interact with a brand, whether on the web, a mobile app, or in a physical store. A company is collecting these behavioral and personal data

I am trying to migrate a component from Coral 2 to Coral 3. We have a sling:resourceType= granite/ui/components/foundation/form/fileupload which we changed to granite/ui/components/coral/foundation/form/fileupload. But after doing so the component dialog doesn't open. I looked at the OOTB AEM core image component at this location (/apps/core/wcm/components/image/v1/image) and got surprised that its using “cq/gui/components/authoring/dialog/fileupload”, instead of coral-3 resource type (/libs/granite/ui/components/coral/foundation/form/fileupload). All other nodes in this component are using coral-3 resource-type, but not the fileupload. Is there any reason for that? We went ahead with the cq/gui/components/authoring/dialog/fileupload, but this is breaking our Alt Text validation functionality. Can you please let me know why in Coral3 granite/ui/components/coral/foundation/form/fileupload is not being used?

as above. The drop-down list that supposed to list all the Marketo forms is empty. All I get is a message that says "Unable to load forms"setup:AEM 6.5.6ACS commons 4.8.6 (release version) (in our AMS hosted environment) | 4.8.6 (release version),5.0.4 (release version), 5.0.5-snapshot and 5.0.7-snapshot (just downloaded yesterday via git clone) (in my local instance)Things I did to setup Marketo in AEM:I followed this guide => https://adobe-consulting-services.github.io/acs-aem-commons/features/marketo-form/index.htmlBecause I cannot added the embed built-in/core component directly, I had to create a new component and extend the embed component. My new component has this => sling:resourceSuperType = core/wcm/components/embed/v1/embedI have created a Marketo config via Settings => Cloud services => Marketo. This created a new node/entry in /conf/myapp/settings/cloudconfigs/MarketoI also have to setup the design mode configuration for my component (configuration located in /

Learn About CMS Headless Development by Adobe Docs Abstract In this part of the AEM Headless Developer Journey, learn about headless technology and why you would use it. Objective This document helps you understand headless content delivery and why it should be used. After reading you should: 1. Understand the basic concepts and terminology of headless content delivery 2. Understand why and when headless is required 3. Know at a high-level how headless concepts are used and how they interrelate Full-Stack Content Delivery Ever since the rise of easy-to-use, large-scale content management systems (CMSes), organizations have leveraged them as a central location to manage messaging, branding, and communications. Using the CMS as a central point for administering experiences improved efficiency by eliminating the need to duplicate tasks in disparate systems. In a full-stack CMS, all of the functionality for manipulating your content is in the CMS. Features of the system make up differe

AEM in Action - Debugging a component. Part 1 by Veena Vikraman Abstract Video: https://youtu.be/ZMAMGk4NK3A If you are a beginner in AEM and do not know how to debug a component from a page , I will try to help walk you through the basic steps. In this video I will walk you through the steps to identify a component and its rendering logic from only the given page. Once you finish this video, you should be able to locate the component, it's rendering script and its Sling Models. In another video , I will show how to change the related Sling Model , build and deploy . Please use the below navigation to easily navigate to portions you want to listen 0:00 Introduction 2:43 Debugging in Action - Problem 4:10 How to debug ? 10:16 Sling Resource Type - Sling resolution 12:30 Sling Resource Super Type 16:00 Conclusion Read Full Blog AEM in Action - Debugging a component. Part 1 Q&A Please use this thread to ask the related questions.

How a Delta Migration Moves Content More Efficiently into AEM by Divya Kandikatti Abstract Moving from a legacy CMS into AEM requires the organization and management of a lot of moving parts; each of which must be rooted in your current needs, while keeping future strategic goals in mind. One of the most crucial steps is data migration, because the content needs to be moved into, and made acceptable, for the new system. A complication often occurs because of the time gap between content migration completion and site launch, when a data clean up is necessary. However, for most organizations, authors are not likely to be able to stop creating content for any length of time. It is critical to define a content cutoff strategy to ensure that all of the content created in this interim is migrated over to the new system, yet allows the least interruption to modifying and generating new content. Delta migration is a process that was created by Blue Acorn iCi experts in response to a recent

Update Link References inside Experience fragment on Rollout by Bimmisoi Abstract As we all know that when we create a live copy of experience fragment or rollout any experience fragments the site's link reference inside it does not get updated as it gets updated in a page. This feature is not available OOTB. In order to achieve that we can create a custom rollout config and can achieve our use case. Steps : Add Synchronization Actions to the Rollout Configuration Go to /apps/msm , create folder named rolloutconfig Under this node create another node jcr:primaryType ----- cq:RolloutConfig Title: Update XF Site Links Name: updateXFlinks cq:trigger: rollout Under this node now create another node Name: linksUpdateXF Type: cq:LiveSyncAction Implement LiveActionFactory : The following LiveActionFactory class implements a LiveAction which updates the link refence in experience fragment on creating a live copy or rollout from master experience fragment. I have excluded countryselecto

Adobe Journey Optimizer-Realtime Omnichannel Journeys For Better Customer Interaction by Nextrow Abstract Please note that while Adobe Journey Optimizer is expected to be released later in 2021, we have only been given a “roadmap” without any commitment to this specific application or its related features. Whether you’re still catching up on sessions or watching highlights from Adobe Summit 2021, you’re sure to hear or read about Adobe Journey Optimizer. This Adobe Experience Platform Application will be a centralized app “that helps brands to easily identify, create, and deliver the next best interaction,” according to Anjul Bhambhri, SVP Adobe Experience Cloud. Bhambhri’s description, in addition to the few related sessions, is enough to excite most anyone in the martech space, but there isn’t a lot of information on AJO available as of now. Based on what we do know, here is a general overview of what we hope to see when the application is released and why this tool is such a huge

The shift to cookieless will change marketing forever: 5 reasons to get there ahead of the competition by Adobe Blogs Abstract Google’s recent announcement that it will delay the depreciation of third-party cookies in their Chrome browser by nearly two years didn’t come as a shock to many observers. Between legal and regulatory challenges, lack of broad agreement and participation on standards, and a myriad of new and untested replacement technologies, companies and vendors alike are struggling to find new ways to reconcile their need to acquire new customers with consumer demand for transparency and privacy. While the announcement provides marketers more time to evolve their strategies around first-party data, consumer sentiment isn’t changing, and it won’t wait for brands to catch up. In other words, just because advertisers and publishers can continue to use third party cookies to track and target consumers doesn’t mean they should do so at the expense of developing first-party d

Code Reuse With Custom Sling Model Injectors by Perficient Abstract In my blog Writing Less Java Code in AEM with Sling Models, I talked about writing less code using Sling Models. I followed that up with Writing Less Java Code in AEM with Sling Models & Lombok. I talked about code generators helping in saving time by not writing redundant codes. You could say I am lazy. I like to use the tools and frameworks at my disposal. But sometimes it is inevitable. We have to write code. I am anything if not efficient. When I write code, I like to make it as concise and simple to understand as possible. In this blog, I am going to talk about the reusability of code helping in writing less code. Tag ID Model As an example, I am going to revisit the Tag id model from that first blog post. In that example, the multifield items had a tag ids property named ./tags. This I injected into the model as ItemTags @ChildResource ItemTags getTags(); And ItemTags implemented Iterable interface ItemTa

Hi Team,I have installed AEM 6.4 (with Service pack 2) on local machine successful. My plan is to create AEM SPA project in local environment. So i have refereed below adobe site link to create AEM SPA project Getting Started with React and AEM SPA Editor---------------------------------------------------------------https://helpx.adobe.com/experience-manager/kt/sites/using/getting-started-spa-wknd-tutorial-develop/react.html#local-dev-envBelow is the listing of chapters in the tutorial:OverviewChapter 0 - Project SetupChapter 1 - Editable ComponentsChapter 2 - Front End DevelopmentChapter 3 - Navigation and RoutingSuccessfully completed Chapter 0 - project Setup steps and finally build deployed project into my local AEM instance. As per the Chapter 1 steps i have created React "Text " in  wknd project and build and deployed successfully into my local AEM instance. But "Text" component is not visible on my local environment.Chapter 1 - Editable ComponentsAdobe Experience Manager Help |

We are on 6.5.8 and have a requirement where-in we need to show page properties to a certain group while ensuring the corresponding group is not able to edit content and edit page properties. However when we provide read access to /content to that group we are not able to see page properties in action tool bar in Sites console. I have also overlayed /libs/wcm/core/content/sites/jcr:content/actions/selection/viewproperties and created a rendercondition to handle the scenario but still it doesnt work. We cant provide modify access to the group. Any pointers?

Some time back, we had 2 users.  Now we have many.  None of the new users can create anything, despite having all possible permissions. In the admin control panel, we assigned all possible permissions for each env to each user, i.e.publish-usersauthor-usersauthor-administratorsWhen the two old users open our sites in author, and hit create, the 2 original  But all our newer users, with exactly the same permissions only see this: We have tried deleting the users, re-adding them, trying to login on a different machine and browser, nothing works.We have raised a ticket with Adobe, but no response (since a week).This is stopping us go live.  Any one has any ideas? To recap:1) our original 2 users can create pages2) new users cant create pages.3) all users have identical permissions in admin console, and users were all added in the same way4) we use the adobe built in user authentication (not AD). We just spent 1 hour going through this with a Ad

Update Link References inside Experience fragment on Rollout  As we all know that when we create a live copy of experience fragment or rollout any experience fragments the site's link reference inside it does not get updated as it gets updated in a page. This feature is not available OOTB. In order to achieve this please go through the blogUpdate Link References inside Experience fragment on Rollout Q&APlease use this thread to ask the related questions  

Hi,My touchui value property is not working for textfields.In the same way selected property is not working for the touchui select field.I am using arm 6.4 and coralui3.When I debug the code , when ever the cmp.getvalue().Val() is returning null and cmp.getvalue().isselected() methods is always returning false.So if any cmp.getvalue().somemethod() the functionality is not working.I have overridden the global.jsp and it is missing the componenthelper import.The issue is intermittent.Does the dialog structure causes the issues?Where can I validate the dialog in aem?How can I resolve the issue??

Hey all, I have the following SQL2 query where I am retrieving documents that have an associated notification. Users have notification nodes under their home path directory, with a documentPath attribute containing the path to the document. Users can have multiple notification nodes referencing the same document path. Is there a way to retrieve the list of unique document paths (no duplicates) of these documents? Currently, the below simple query will return duplicate documents if there are multiple notification nodes referencing the same document. I thought DISTINCT would mitigate that unless I am misunderstanding the spec? SELECT DISTINCT document.[jcr:path] from [cq:Page] as documentINNER JOIN [nt:unstructured] as notification on document.[jcr:path] = notification.[documentPath]where isdescendantnode(document, '/content/experience-fragments/documents') and isdescendantnode(notification, '/home/users/bluh') The reason I would like the uniqueness to occur in oak is

I can see the pdf viewer in publish servers but in the varnish/webserver url the pdf viewer is not loaded. The sdk or the component div is not created, i am not seeing any errors in log or console. 

Hi, I am using AEM 6.5. I have a requirement in which I want to provide a guest login to external user to complete a workflow in AEM. How can I achieve this using any feature in AEM. Please guide. Thank you!