Product Communities

We are currently reviewing the default value for predecessor behaviour when copying/moving tasks. The question is: do you commonly need the predecessors to be kept when copying/moving a group of tasks?

Video October AEM Release Overview Video -  Highlights the new AEM Sites “Quick Site Creation” features now available, as well as AEM Forms + Analytics integrations and enhancements to Cloud Manager for faster CI/CD pipeline. 

Authors: Yeshwanth Vijayakumar, Vineet Sharma, and Sandeep Nawathe In Part 1, we went over how we applied some Spark optimizations to our Structured Streaming Workloads. In Part 2, this blog details how we optimized our Interactive Query Evaluation workloads on top of Apache Spark. This blog post is adapted from this Spark Summit 2020 Talk. Architecture Overview Just as a reference from the previous blog to set the context. Here again is the relationship between Adobe Experience Platform Real-time Customer Profile and other services within Adobe Experience Platform is highlighted in the following diagram: Our Requirements Adobe Experience Platform assimilates data from various channels and makes this data actionable for targeting and marketing experiences. Our customers needed to express their segments as rules to the platform and it takes care of executing these complex rules in a high performant fashion. Therefore, our requirements were at a high level: Build an interactive segment

Authors: Anshuman Nangia, Anand Phatak, Nipun Nair, and Douglas Paton This blog post continues our look at how Pipeline powers the Adobe Experience Platform. We break down the components and look at how Pipeline is being used for data processing in-flight. Our team thinks of Adobe Experience Platform Pipeline, a Kafka-based message bus, as a “data power grid” for Adobe. It is a critical piece of our infrastructure, which runs across 14 clusters covering AWS, Azure, and our private data centers. Going back about five years, most of the communication between services at Adobe was point-to-point. Unsurprisingly, this pattern became untenable very quickly as teams started to break down existing monolithic systems and the number of services started to grow. Configuration management burdens grew exponentially and became unmanageable to the point where “integration” horror stories became commonplace. Adobe Experience Platform Pipeline project started with the goal of making it easier to integ

Authors: Miao Wang, Jun Ma, and Jenny Medeiros This post describes our approach to addressing the challenges of cost and scale in scanning for GDPR compliance in Adobe Experience Platform. In today’s data-driven economy, user data is an increasingly valuable asset. Although as companies collect increasingly more personal information, users have rightfully raised the question of how to manage their data privacy. In response, the European Union instituted the General Data Protection Regulation (GDPR), which aims to give EU individuals control over their personal data. This has prompted other nations to strengthen their own data privacy laws, such as the upcoming California Consumer Privacy Act (CCPA). Under these protections, users have the right to request a copy of their data collected by a company or have it erased. To ensure Adobe Experience Platform customers meet data privacy regulations, we developed Adobe Experience Platform Privacy Service, which automates applications to provi

Authors: Constantin Muraru and Jody Arthur This post provides code examples of how Adobe Experience Platform uses helmfile in Kubernetes to streamline the installation and management of infrastructure applications needed to support large-scale deployment of applications. Kubernetes is one of the most widely used and popular open-source container management systems among data-driven enterprises today. At Adobe, we use Kubernetes for a wide range of tasks that power Adobe Experience Platform. To meet the needs of our internal use cases, we build Kubernetes clusters and make them available to our internal customers for the deployment of their applications. One example is Adobe Experience Platform Pipeline, which uses Kafka to provide a single enterprise-level message bus for transferring data between different applications within Adobe Experience Platform. Pipeline operates through a simple web service on top of the Kafka service and is deployed using Kubernetes. Due to the huge volumes o

Authors: Raman Gupta, Anand Gupta, Piyush Dewnani, Richard Ding, and Jody Arthur Learn how Adobe Experience Platform is leveraging Apache Airflow support for Kubernetes to achieve high scale. This article builds on our previous work to build an orchestration service to enable users to author, schedule and monitor complex hierarchical jobs using Apache Airflow for Adobe Experience Platform. You can get additional insights on how Adobe Experience Platform is using Apache Airflow to exponentially scale its workflows for better performance here. Adobe Experience Platform’s Orchestration Service provides APIs to author and manage multi-step workflows. Behind the scenes, this service leverages Apache Airflow as its workflow execution engine. With the 1.10.1 release, Apache Airflow added support for Kubernetes (K8S) Executor. Now, with K8S Executor, a new K8S pod is created for each instance of a workflow task, resulting in one-to-one mapping between the worker pod and its corresponding task.

Authors: @danny-miller , Shrutivj, Jenny Medeiros,  This post describes how we approached the challenge of obtaining deltas from audience segments so that Adobe Experience Platform clients can export the users they need when they need them. This blog details a single implementation or customization on Adobe Experience Platform. Not all aspects are guaranteed as general availability. If you need professional guidance on how to proceed, then please reach out to Adobe Consulting Services on this topic. Adobe Experience Platform allows clients to easily segment user profiles into specific, attribute-based audiences using their Real-Time Customer Profile data. Through segmentation, clients can distinguish marketable customers and effectively tailor their marketing strategies, such as email campaigns. Recently, an Adobe Experience Platform client requested the ability to create a single segment that could be reused for both the initial population as well as changes to that populat

Author: @danny-miller , Shrutivj, and Douglas Paton In this post, we look at data science for XDM and make it scale. We look at how we build tens and hundreds of models and activate it for Adobe Experience Platform. And we look at how data science is manifested at Adobe and basics around operationalizing. This blog details a single implementation or customization on Adobe Experience Platform. Not all aspects are guaranteed as general availability. If you need professional guidance on how to proceed, then please reach out to Adobe Consulting Services on this topic. When it comes to data science models, our focus tends to be on building all these amazing models. But what about operationalizing or activating them with the Adobe Experience Platform. We look at the output, which eventually turns into a score or classification that can be assigned to a person. We look at things like if a person is likely to buy or churn. This, may in turn or in parallel, feed into whether a person is c

Authors: Wouter Van Geluwe, Krishna Punyakoti, Kalaiyarasan Venkatesan, Althaf Kandi, and Douglas Paton This blog details a single implementation or customization on Adobe Experience Platform. Not all aspects are guaranteed as general availability. If you need professional guidance on how to proceed, then please reach out to Adobe Consulting Services on this topic. In this post, we look at an early stage POC workflow on how to generate real-time sales predictions for anonymous, unknown website visitors using Adobe Experience Platform. We discuss how we used Adobe Experience Platform and Data Science Workspace services to provide brands with the ability to use ML Models to score customer behavior in real-time to personalize and contextualize personalization in order to increase conversions. When anonymous prospects interact with your website, knowing whether or not they’re likely to become a customer gives you the ability to make informed decisions about how you should engage with them

Authors: Sandeep Nawathe and Jody Arthur In Part 1 of this series, we described all the digital components enterprises need to develop a 360-degree view of their customers and the capabilities and limitations inherent in the technologies available to help them do that. Here in Part 2, we + a new approach — one that unifies disparate data sources and system architectures to develop a Unified Profile that is actionable in real-time. With the proliferation of information technology systems, an enterprise’s customer information is often fragmented across disparate sources hampering its ability to fully leverage the power it holds. Delivering the real-time personalized experiences that today’s consumers demand starts with building a holistic understanding of the customer, a Unified Profile. In Part 1 of this series, we described the digital components needed to develop a unified, centrally accessible customer profile that allows an enterprise to target people with personalized cross-channe

Authors: Ye Xu and Douglas Paton In this post, we, Adobe Experience Platform, round up the key takeaways from AWS re:Invent 2019. We look at the big things coming up for Computing, AI and Machine Learning, Database and Analytics, Security, IoT. AWS re:Invent is Amazon Web Services (AWS) annual conference for all things cloud computing. The 8th year of the event, held in November of 2019, was the biggest yet, attracting 60,000 people, and featured the launch of 75 new services for AWS. The new services were launched in over 13 different categories, ranging from Analytics to developer tools, and has some exciting implications for Adobe Experience Platform. Looking at everything from the show would be impossible, but we’ve got a roundup of some of the more applicable new services that were launched. Let’s dive in and take a look. Computing Amazon has made enhancements to Amazon EMR, their big data processing and analysis platform that allows you to run and scale Hadoop, Apache Spark, and

Authors: Amy Durocher, Andrew Kirkpatrick, and Jenny Medeiros This post describes our journey building accessibility into Adobe Experience Platform and our approach to achieving the ambitious goal of becoming accessibility compliant by the end of 2020. The accessible design has rightfully become the focus of leading organizations worldwide. With almost 20% of the global population living with some form of disability, it should no longer be an afterthought to offer different ways for people with sensory, physical, or cognitive impairments to access online products. At Adobe, we firmly support and encourage building inclusive user experiences that are accessible to customers of diverse abilities. To further our commitment, we are purposefully designing new Adobe products with human differences in mind, and revisiting past ones to bring them up to standard. In this post, we share the highlights of our ongoing accessibility journey as we tirelessly work to make Adobe Experience Platform

Authors: Sandeep Nawathe and Jody Arthur This is the first post in a two-part series that explores the challenges inherent in developing a 360-degree view of the customer. In this post, we describe the digital components a business needs to develop a holistic understanding of the customer and the difficulties associated with pulling them all together in the current solution landscape. In Part 2, we will present a new approach to unifying disparate data sources and system architectures to develop a Unified Profile that is actionable in real-time. To be successful, enterprises have always strived to provide the best customer experience. With the rise of digital technology, proactively understanding a customer’s interests has been a key approach for businesses seeking to deliver personalized experiences that engage and delight their customers. And, customers expect this today. They have come to expect relevant material across all their interactions with a brand that optimizes their exper

Authors: @danny-miller , Shruti Jagtap, Douglas Paton In this blog, we look at how modeled a one to many relationships in XDM for Adobe Experience Platform. We discuss the options we had for modeling and the surprises that came up along the way. This blog details a single implementation or customization on Adobe Experience Platform. Not all aspects are guaranteed as general availability. If you need professional guidance on how to proceed, then please reach out to Adobe Consulting Services on this topic. One-to-many (1:M) relationships are everywhere these days. We sign up for things using different names, email addresses, and user names depending on the product or service we’re using. We create a whole host of mini-profiles that all point back to us. This creates a situation where multiple profiles online can all be attributed to a single person. The challenge is that most 1:M profiles end up looking very similar to Figure 1. Not surprisingly, something like that can be fit int

Warning: this blog post will seem out-of-nowhere until you read the next one, which is a Marketo-focused use for the code supplied below. But this had to come out first in preparation.   Something’s notable about a <style> element with no attributes (no id, no title, no class or custom data-). While the styles inside will work perfectly, there’s no standard way to distinguish the source, purpose, or implied scope of such an element.   Such elements are ridiculously common, of course! You surely have at least one non-attribute-ed <style> in the head of your HTML templates, which you term “local styles.” And 3rd-party libraries can inject many more.   But what if you want to reference a specific one of those stylesheets from JS, like the <style> that brands your video player? Well, you’re basically out of luck unless you get to guessin’.   See, from a DOM standpoint, the

Hi, RTE in AEM 6.4 is throwing an error when I make the component configurable by adding a checkbox for users in the dialog for authors to use the RTE in any custom component. However, after I select the checkbox and add content to it and click on 'ok' checkmark, it throws an error initially but if I refresh the page, the component is throwing content in RTE correctly. If I again update the content in the same page and click on 'ok' checkmark, it's throwing the error again until I refresh the page.Error message - Uncaught (in promise) TypeError: Cannot read properties of null (reading 'data')  - http://localhost:4502/libs/cq/gui/components/authoring/editors/clientlibs/core.894e3547679632b5f44a9833bcb0529b.jsThe code for adding RTE in the component looks like this: <div data-category="${properties.tiletype}" data-sly-test="${properties.includedes}" data-sly-resource="${'something' @ resourceType='/apps/foldername/components/content/genericrichtext'}"></div&g

Last week we published the JCR Query cheat sheet as part of the official AEM documentation: https://experienceleague.adobe.com/docs/experience-manager-65/deploying/practices/best-practices-for-queries-and-indexing.html?lang=en#jcrquerycheatsheet it is appplicable for AEM 6.5 and AEM as a Cloud Service, but the majority of it should be good also for earlier versions down to 6.0. For different type of queries it contains samples which are are the most performant to achieve the expected results, plus the requirements towards the index backing these queries. It contains these queries so you can copy&paste them, has a number of helpful links, and its printable so you can pin it to your wall. And it's the a good learning source for the 3 supported query languages QueryBuilder, XPath and SQL-2. Have fun!Jörg    

Hi,Please checkout the KB article for cq:isContainer Propertyhttps://aemlab.blogspot.com/2021/11/cqiscontainer-property-in-aem.html

EDIT: The pictures shown is for 1 group that is not a member of any other group. problem: having issues with permission inheritance in experience fragments (/content/experience-fragments) preferred outcome: all folders and fragments under the parent path will inherit. In my screenshot, all folders and fragments should inherit the permission for the staff folder.-----The permission were setup by going to author.myhost.com/useradmin - the child folder got the permissions from the parent (/content/experience-fragments/staff/digital-services)- the grandchild folder did not inherit the permissions set in the parent (specifically modify permission)- fragment inside the grandchild folder does not have modify

Fast Facts — AEM Best Practices Analyzer (BPA) by Sanjay Kushawaha Abstract The Best Practices Analyzer (BPA) which earlier known as Cloud Readiness Analyzer is used to assess the AEM project code implementation by indicating areas that are not following the best practice guidelines of AEM as a Cloud Service (AEMaaCS). By using the report generated by BPA you can identify the potential code refactoring areas that need to be fixed before deploying it to AEMaaCS. Let’s understand the flow by referring below diagram. Important considerations for BPA It is supported on AEM instance 6.1 or above and can be run by admin or user having administrator rights. It can be downloaded from Adobe Software Distribution Portal and install on AEM Author using Package Manager. Once installed it can be accessed by following the path Tools → Operations → Best Practices Analyzer. Read Full Blog Fast Facts — AEM Best Practices Analyzer (BPA) Q&A Please use this thread to ask the related questions.

DM Classic - S7 - Show default image when a specific Image or Vignette object not found by Sreekanth Choudry Nalabotu Abstract Missing Product Image In Dynamic Media Classic (S7), if the image (specified in URL with others modifiers) is NOT found, you can serve a default image by adding parameter &defaultImage. This helps when there are new images for a product not published yet or missing for some reason, so when users clicks the link or the specific swatch, a default image for the product is shown (instead of a broken or generic 404 image...) Image not found URL eg: http://sample.scene7.com/is/image/S7trainRender/image_does_not_exist With &defaultImage URL parameter: http://sample.scene7.com/is/image/S7trainRender/image_does_not_exist?defaultImage=ninewest_shoe Unavailable Vignette Object While serving an Image Render or Vignette (composed of objects) if the Object name is NOT found, there is no default image parameter here and error Object not found is shown... Sample O

Join us for our first Adobe Analytics Community Q&A Coffee Break,  taking place Tuesday, November 2nd, 2021 @ 8am PT -  9am PT 🗓️☕Be sure to MARK YOUR CALENDARS with a link to this thread☕🗓️ We'll be joined by Travis Sabin, aka @tsabin03,  Principal Product Manager for Adobe Analytics, who will be signed in here to the Adobe Analytics Community to chat directly with you on this thread about your Adobe Analytics questions pertaining to his focus areas: Quick Segments New Analytics landing page Quick Insights    📊REQUIREMENTS TO PARTICIPATE 📊 Must be signed in to the Community during the 1-hour period  Must post a Question about Adobe Analytics THAT'S IT!  *(think of this as the Adobe Analytics Community equivalent of an AMA, (“Ask Me Anything”), and bring your best speed-typing game)  📊INSTRUCTIONS 📊 Click the b

      In summary, this post will teach you how to optimize the hand-off of email content from your content creation team and create automation that will:   Send email content from a Google Sheet to Zapier Create an email program, email asset, and smart campaigns for this email Upload images from Dropbox to the Design Studio using the API so that they can be used in your email Populate your email by transferring the content from your Google Sheet to email variables using the API Create dynamic content sections and populate these sections with the content from your Google Sheet using the API   All the Python code used in the Zapier actions, the JavaScript code used in the Google Sheet, and the HTML code for the marketing newsletter can all be found in this directory in Github.   N.B. If it is your first time using the API or you need a quick refresher then check out the Quick-Start Guide to the API to see how to make your first API requests in Pos

Hi all, I'm excited to share that we will be starting up our next round of testing. Many of you reached out during our first round and was deferred to this one instead. With that, we will be reaching out to those folks first before we take on other testers—be on the lookout for an email. If you would like to be added to our waitlist, please comment below! In the meantime, a little teaser—can you spot the Workfront tasks on the board living side-by-side with the ad hoc items?