Product Communities

Authors: Tina Dilip Soni, Marina Mahtab, and Althaf Kudiyama Kandi 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 interdependent steps. Model building and recipe cr

Adobe Experience Manager Sites launching quick site creation features by Haresh Kumar Abstract Content agility has never been more important for brands in today’s fast-moving digital economy. Consumers expect information in real-time, and brands are forced to push out varying experiences across more channels than ever before. According to Adobe’s Future of Marketing Research Series, marketers feel that they should be personalizing between 50 and 70 percent of owned content but are currently achieving far less. Ultimately, delivering timely and fresh content has become table stakes, whether it’s a simple campaign landing page or an extensive corporate redesign. Historically, having to work closely with IT teams to create and maintain these experiences has made it cumbersome for brands to rapidly push out new content. Now more than ever, brands find themselves seeking out low- and no-code tools and capabilities that allow various teams within their organization, whether it’s within mar

AEM 65 sp10 - Simple Token Based Authentication by Sreekanth Choudry Nalabotu Abstract Goal AEM Cloud Services provides OAuth 2 based authentication documented here. For OAuth 2 based authentication in AEM 65 check this post. The solution discussed here is a more simple non standard token based authentication.... Solution 1) Create an overlay for the tools nav item /apps/cq/core/content/nav/tools/experience-aem/experience-aem-config 2) Create the Token Auth Config page /apps/eaem-simple-token-based-auth/extensions/simple-token-auth/token-config accessed using http://localhost:4502/apps/eaem-simple-token-based-auth/extensions/simple-token-auth/token-config.html/conf/global/settings/dam/experience-aem Read Full Blog AEM 65 sp10 - Simple Token Based Authentication Q&A Please use this thread to ask the related questions.

Composable: Expanding Beyond Headless by bounteous Abstract Headless and composable are hot topics in digital, but what exactly do they mean? In the simplest terms, headless is a system with a decoupled back-end and front-end. Composable, on the other hand, is a comprehensive approach to consolidating headless initiatives—ultimately bringing agility to the digital experience (DX) infrastructure. Think of composable as the big sister of headless digital experience architecture. Let's take a closer look. What Is Headless? Headless, or decoupled, refers to any system where the front-end and the back-end are connected by an Application Interface (API). It is a pretty broad definition that can be applied to a lot of solutions, like Ajax, web apps, PWAs, IoT, or native apps. Headless makes sense; it is a great way to deliver snappy user experiences by reducing the amount of redundant data being sent during an experience. By separating content and presentation layers into separate back-e

AEM Cloudservice - React SPA with Sling Vanity URLs by Sreekanth Choudry Nalabotu Abstract Goal Adobe Experience Manager 2021.9.5899.20210929T093525Z-210800 (Sep 29, 2021) Create a AEM React SPA supporting Vanity Urls. Otb Vanity Urls are added in Page Properties, saved as jcr:content/sling:vanityPath Solution 1) Add the function getVanityUrls() to get the list of vanity urls using querybuilder before loading the app. VanityURLModelClient extending ModelClient was added as a workaround to not request model.json using the vanity url (eg. this is invalid request http://localhost:4502/eaem-home.model.json). Code in eaem-spa-vanity-urls\ui.frontend\src\index.js facilitates loading of vanity urls into the app... import 'react-app-polyfill/stable'; import 'react-app-polyfill/ie9'; import 'custom-event-polyfill'; import { Constants, ModelManager } from '@adobe/aem-spa-page-model-manager'; import { createBrowserHistory } from 'history'; import React from 'react'; import { render } from '

Hey folks,           We are getting lot queries for connecting dots between different components of AEP to have complete experience. We are starting #FridayFinding with Platform Experience which will cover concepts and golden nuggets. Every Friday a topic would be released, and the thread would be moderated by experts @karandhawan @ankita_sodhi @ankitbhatt @skand  who would be answering the queries on thread. Way of Working for FridayFinding Each #Fridayfinding would cover a topic as What will we do? Perquisites, steps, and outcome. Connect what we just did to why we did. This part would explain what we did in previous step would connect in real life. Before we dive into world of Platform Experience next Friday onwards, consider setting environment by having instances and licenses handy to grow together. Access to Adobe Experience Platform: https://experience.adobe.com/platform Access to

Hey folks,           We are getting lot queries for connecting dots between different components of AEP to have complete experience. We are starting #FridayFinding with Platform Experience which will cover concepts and golden nuggets. Every Friday a topic would be released, and the thread would be moderated by experts @karandhawan @ankita_sodhi @ankitbhatt @skand  who would be answering the queries on thread. Way of Working for FridayFinding Each #Fridayfinding would cover a topic as What will we do? Perquisites, steps, and outcome. Connect what we just did to why we did. This part would explain what we did in previous step would connect in real life. Before we dive into world of Platform Experience next Friday onwards, consider setting environment by having instances and licenses handy to grow together. Access to Adobe Experience Platform: https://experience.adobe.com/platform Access to

I would like to run a test to specifically target "direct traffic" meaning visitors who have typed in the URL directly or have the URL bookmarked. Is there a way to do this?

Hi Everyone, Alex (designer) and Anna (product manager) are trying to improve the way information is structured on projects, tasks, and issues. They want to learn more from you about how you use those objects. If you're interested in participating in this discovery research, please sign up below! Sessions are 45 minutes. https://calendly.com/wf-product-research/project-task-issue-information-discovery

Hi All, I would like to know how to bring up the character count for a text field or rich text field that is available inside a component which uses Multifield resource type.Eg: the below is a component that uses a Multifield resource typewhen i click on Add button, the counter should appear for the Head line field: Actually, I have already added themaxlength="54"property in the XML. If i click on the add button the counter does not appear. But when i edit the component and save it and reopen the same, the counter appears. PFB: I want the counter to appear as soon as i click on the add button.Please help. Thanks

If I click on any package in https://experience.adobe.com/#/downloads/content/software-distribution/en/aemcloud.html It says "Error 404: Package not found" Is there anywhere else we can get it from?    

Hello, We have a requirement for the document of record to be ADA compliant and screen reader accessible. Currently, we are generating document of records with the OutputService API in AEM. In the PDFOutputOptions object, setTaggedPDF is set to true to generate accessibility tags in the PDF. When using a screen reader on the resulting PDF, we find that the field values and names are often repeated. Radio buttons are not read in order and does not state which option is checked.  This results in having to manually remediate the document of record to resolve accessibility issues. Is there a way to generate document of records that are ADA complaint without having to manipulate the tag tree? Thank you

Local Development Access Token by Adobe Abstract Developers building integrations that require programmatic access to AEM as a Cloud Service need a simple, quick way to obtain temporary access tokens for AEM to facilitate local development activities. To satisfy this need, AEM’s Developer Console allows developers to self-generate temporary access tokens that can be used to programmatically access AEM. The Local Development Access Token provides access to AEM Author and Publish services as the user who generated the token, along with their permissions. Despite this being a development token, do not share this token, or store in source control. In Adobe AdminConsole ensure you, the developer, are a member of: Cloud Manager - Developer IMS Product Profile (grants access to AEM Developer Console) Either the AEM Administrators or AEM Users IMS Product Profile for the AEM environment’s service the access token will integrate with Sandbox AEM as a Cloud Service environments only require m

AEM Dispatcher Cache Tutorial by Adobe Abstract The Dispatcher is an essential part of most, if not all AEM installations. The goal of this tutorial is to help you better understand how the Dispatcher works and how you can work with it. This tutorial is divided into three parts. Concepts, Patterns, and Antipatterns Provides a brief introduction of the Dispatcher’s history, mechanics and discusses how this influences how an AEM developer would design his components. Infrastructure Pattern Discusses various topologies on how to scale up an AEM system with a cluster of Publish systems and Dispatcher caches in front. Advanced Caching Topics Where the first two parts focused on plain http caching in the Dispatcher and what limitations there are. This part discusses some ideas on how to overcome these limitations. Read Full Blog AEM Dispatcher Cache Tutorial Q&A Please use this thread to ask the related questions.

IMS Support for Adobe Experience Manager as a Cloud Service by Adobe Abstract Introduction AEM as a Cloud Service includes Admin Console support for AEM instances and Adobe Identity Management System (IMS for short) based authentication. The Admin Console allows administrators to centrally manage all Experience Cloud users. Users and Groups can be assigned to product profiles associated with AEM as a Cloud Service instances, allowing them to log in to that instance. Key Highlights AEM as a Cloud Service offers IMS authentication support only for Author, Admin and Dev users. It does not offer support for external end users of customer sites like site visitors. The Admin Console will represent customers as IMS Organizations, Author and Publish Instances in an environment as Product Context Instances. This will allow System and Product administrators to manage access to instances. Product Profiles in the Admin Console will determine which Instances a user can access. Customers will be

An Introduction to the Architecture of Adobe Experience Manager as a Cloud Service by Adobe Abstract Adobe Experience Manager (AEM) as a Cloud Service has resulted in changes to the architecture. Scaling AEM as a Cloud Service now has: A dynamic architecture with a variable number of AEM images. Dynamic architecture This architecture: Is scaled based on the actual traffic and actual activity. Has individual instances that only run when needed. Uses modular applications. Has an author cluster as default; this avoids downtime for maintenance tasks. This enables autoscaling for varying usage patterns: Autoscaling for varying usage patterns To achieve this, all instances of the AEM as a Cloud Service are created equal, each with the same default sizing characteristics in terms of the number of nodes, allocated memory and allocated computing capacity. AEM as a Cloud Service is based on the use of an orchestration engine that: Constantly monitors the state of the service. Dynam

Index Converter by Adobe Abstract Index Converter is a utility developed to migrate a customer’s Index Definitions in preparation for the move to AEM as a Cloud Service. Introduction The Index Converter allows AEM developers to migrate existing Custom Oak Index Definitions to AEM as a Cloud Service compatible Custom Oak Index Definitions. NOTE Index Converter only transforms lucene type Custom Oak Index Definitions which are present under /apps or /oak:index. It does not transform lucene type indexes which are created for nt:base. There are two ways to create Custom Oak Index Definitions: under /apps (through any custom content package) directly under /oak:index path If Ensure Oak Index was used, please note that Ensure Definitions are not supported on AEM as a Cloud Service, and hence they need to be converted to Oak Index Definitions first and then need to be migrated to Custom Oak Index Definitions that are compatible with AEM as a Cloud Service as per below guidelines: If pro

Asset Workflow Migration Tool by Adobe Abstract Asset Workflow Migration tool is used to automatically migrate asset processing workflows from on-premise or AMS deployments of AEM to processing profiles and OSGi Configurations for use in AEM Assets as a Cloud Service. Introduction This section describes resources and implementation details on Asset Workflow Migration tool. This utility allows the AEM developers to migrate existing AEM asset processing workflows to AEM as a Cloud Service. Supported workflows The workflows have varying level of migration support. See this list of specific workflows. The workflows are categorized in the following categories based on the support provided. Adobe supports migration of the workflows that are listed in SUPPORTED, REQUIRED, or OPTIONAL categories. The workflow steps mentioned in the other categories are not supported. SUPPORTED: Supported functionality in Experience Manager Assets as a Cloud Service. OPTIONAL: Optional functionality in Exp

AEM Dispatcher Converter by Adobe Abstract Adobe Experience Manager Dispatcher Converter converts existing AEM Dispatcher configurations to AEM as a Cloud Service Dispatcher configurations. Introduction to Dispatcher Dispatcher is Adobe Experience Manager’s caching and/or load balancing tool. Using AEM’s Dispatcher also helps to protect your AEM server from attack. Therefore, you can increase the security of your AEM instance by using the Dispatcher in conjunction with an enterprise-class web server. NOTE The most common use of Dispatcher is to cache responses from an AEM publish instance, to increase the responsiveness and security of your externally facing published website. Refer to Dispatcher Overview to learn how dispatcher performs caching, returns documents and performs Load Balancing. Apache and Dispatcher Configuration and Testing You must learn how to structure the AEM as a Cloud Service Apache and Dispatcher configurations, as well as how to validate and run it locally

Learn About CMS Headless Development by Adobe Abstract n 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: Understand the basic concepts and terminology of headless content delivery Understand why and when headless is required 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. Read Full Blog Learn About CMS Headless Development Q&A Please use this thread to ask the related questions.

Someone bumped an old Nation thread with my code to add a CSS class to every <label> element indicating the type of input it’s labeling, like:   <label id="LblProductInterest" for="ProductInterest" class="mktoLabel for-type-radio"><label id="LblIndustry" for="Industry" class="mktoLabel for-type-select-one">   You can then use generic CSS selectors, i.e. .mktoForm label.for-type-radio. After all, you almost certainly want to style all labels for radio buttons the same way (on a given form). You don’t need to know the field name for that!   That code was bad by my current standards, especially because it didn’t pick up new fields added by Visibility Rules. Also, a data- attribute is a better fit than a class.   Here’s the updated code: /** * Tag labels with type of related input * @author Sanford Whiteman * @version v2 2021-10-02 * @copyright © 2021 Sanford Whiteman * @license Hippocratic 2.1 * */ MktoForms2

Session Details Learn from the most common mistakes that others have made so that you can avoid them yourself! In this session, we will look at some of the common issues that our on-call and support engineers have seen and discuss best practices for ensuring that you can avoid these in your own AEM as a Cloud Service implementation. Experience League Session Recording  Session Schedule 10/4/21 13:30 PDT 10/4/21 22:30 CEST Speaker(s) Ian Reasor and Joerg Hoh Moderator(s) Speaker team Product(s) Experience Manager as a Cloud Service Full Schedule Check Here Q&A from the Session Any specific performance tests for author env for AEMaaCS, Previously we had toughday but it seems to be outdated. Toughday was always just a test-suite to evaluate the (hardware-) plattform, and less something to test an application. Toughday is still working, but the results are less meaningful. Q&A Please use this thread to ask the question related to this Session. Don't forget to register

What is hotter in the industry than lead scoring?     You guessed it… predictive lead scoring!   Sometimes you may hear the term “intent scoring” which refers to the same methodology.     Every conversation that revolves around predictive scoring typically goes into one of two extremes, with levels of moderation between these extremes.     On one side are your hard-core predictive scoring believers who will die on the hill of “AI and Machine learning will revolutionize marketing and why on earth would you do anything differently?”  Trust the algorithm, they would say.  We have data that you don’t have and you need!  Behavior-based scoring from your own resources is so antiquated!     On the other side are people who believe that predictive scoring is conjured up from some form of magic trick.  Others consider it a form of technical Gnosticism, with the methodology of the vendor being opaque and requiri

Hi Everyone, In our effort to reward the monthly top two users with a gift card for their participation on the Adobe Campaign Standard and/or the Adobe Campaign​ Community forums, we present to you the two top users in the Community for the month of September 2021 - @Deb007 and @SatheeskannaK. Congratulations and a big thanks to both of you for being dedicated and helpful community members of the Adobe Campaign Communities. Become a top user and win every month simply by answering questions and being helpful to other members on this community. Perhaps, YOU could be a winner next month! While we hope that this token of appreciation motivates you to give back to other members, we also hope that you already enjoy helping your Community friends with their queries, as this helps us build a better product for you. 

Hi Everyone, In our effort to reward the monthly top two users with a gift card for their participation on the Adobe Campaign Standard and/or the Adobe Campaign​ Community forums, we present to you the two top users in the Community for the month of September 2021 - @debtr and @satheeskannak. Congratulations and a big thanks to both of you for being dedicated and helpful community members of the Adobe Campaign Communities. Become a top user and win every month simply by answering questions and being helpful to other members on this community. Perhaps, YOU could be a winner next month! While we hope that this token of appreciation motivates you to give back to other members, we also hope that you already enjoy helping your Community friends with their queries, as this helps us build a better product for you.  We're always open to new ideas for Adobe Campaign, and can't wait to hear