Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
Session Details In this session, learn the no-code approach to quickly create a landing page or microsite with Site Templates and other Quick Site Creation features in AEM. In today’s fast-paced digital world, getting your experiences up and running quickly is critical to driving success. Yet creating and launching a simple landing page or microsite can be a complex and lengthy process. You can now accelerate this process with the new Quick Site Creation feature. Start with a Site template, and create web experiences within minutes with just a few clicks. Join us to learn about: 1. No-code approach to quickly create a landing page or microsite based on a Site template 2. Flexible authoring capabilities with best practice components and templates 3. XD-driven theming workflows that can be used by any web agency, if necessary Session Recording Session Schedule 2022-03-16 | 12:30:00 PST | 30 Mins Duration Speaker(s) Gabriel Walt & Pauline Huynh Moderator(s) Adobe Resource(s) Product
Session Details Learn how Sales, Marketing and Customer Success teams can use the Learning Platform to boost sales and customer loyalty. Studies suggest that nearly half of a organizations struggle with post-sales customer experience, thereby impacting future growth and sales for their products and services. Marketing, Sales, and CX teams can overcome this challenge by delivering a personalized and highly engaging learning experience, resulting in higher customer satisfaction, retention, and growth. Organizations can also leverage learning to improve sales performance of their direct and partner channel networks. Learn how Sales, Marketing, and Customer Success teams can use the Learning Platform to: 1. Gain the trust of customers and earn their loyalty 2. Nurture high-performing sales and partner teams that beat sales quotas every time 3. Build a self-service model for customers to get instant resolution to their queries, thereby reducing your customer support costs and onboarding ti
Session Details Learn how to improve in store customer retail experiences with Adobe Experience Manager's content management system for Digital Signage. As the world becomes increasingly connected, so has the importance of digital signage to unify the customer experience across digital and physical spaces. With static signage, brands struggle to keep up with customer demands and deliver exceptional in-store experiences. Join us to discover how a large retailer unlocked the potential of Adobe Experience Manager Screens to reinvent the customer retail experience, engage with customers in new ways, and maintain brand consistency throughout the customer journey. Learn how a large retailer leveraged Screens to: 1. Enrich the omnichannel experience and multi-touchpoint customer journey 2. Drive personalized journeys that are relevant and contextual 3. Achieve efficiency and reduce environmental impact Session Recording Session Schedule 2022-03-16 | 13:30:00 PST | 30 Mins Duration Speaker(s
Session Details See how CSU Fullerton designed and built a virtual end-to-end digital onboarding solution including forms, automated workflows, and e-signatures. With the help of Adobe Experience Manager Forms and Adobe Sign, California State University, Fullerton established a virtual onboarding process for new students and routed administrative forms digitally, all while meeting deadlines earlier than expected. The use of e-signatures, automatic routing, and digital workflows enabled CSU Fullerton to shorten these administrative processes from weeks to hours and also decrease costs by reducing paper usage by 50%. Hear from CSU Fullerton on how they built a fully digitized onboarding journey to deliver a best-in-class user experience, and see how you can achieve those results, too. Join our session to hear about: 1. How CSU Fullerton designed and built a virtual end-to-end onboarding experience 2. Best practices for implementing a forms and e-signature solution 3. Increasing efficien
Session Details Extend & customize your Adobe products with Adobe Developer App Builder which connects with your Adobe Commerce integrations and AEM to build applications. Learn how to extend and customize your Adobe solutions so that they work best for you. Adobe Developer App Builder is now available for Adobe Experience Manager and coming soon for Adobe Commerce. In this session: 1. Introduction of App Builder 2. Demo of the developer journey for App Builder 3. Customer use cases and best practices Session Recording Session Schedule 2022-03-15 | 11:30:00 PST | 30 Mins Duration Speaker(s) Amol Anand & Sarah Xu Moderator(s) Adobe Resource(s) Product(s) Adobe Experience Manager,Adobe Experience Cloud,Adobe Commerce Full Schedule Check Here Session Q&A Question Answer Does this integrate with XD? App Builder integration with XD does not exist OOTB currently. Thanks Sarah, great to hear there is a trial. Is there a ballpark price range per user/site/developer? Hi Pat
Session Details See how AEM Headless empowers developers to build single-page web apps and deploy using Adobe App Builder and best practices for each type of content. Quickly bootstrap and deploy single-page apps (SPA) using Adobe App Builder workflows and tools, no traditional Experience Manager skills, like Java and Sling, required. With Experience Manager Headless, marketers and developers can each have expertise of their own domain — developers control the overall application framework, styling, and routing while marketers determine the content and how it’s displayed. Learn how: 1. Experience Manager Headless empowers developers to build SPAs using modern web technologies and flexible deployment models 2. Marketers can control content with Content Fragments and the SPA Editor Session Recording Session Schedule 2022-03-15 | 12:00:00 PST | 30 Mins Duration Speaker(s) Duy Nguyen & Sean Steimer Moderator(s) Adobe Resource(s) Product(s) Adobe Experience Manager,Adobe Experience Pl
Session Details Monitor custom applications development projects with Log Forwarding in Adobe App Builder. Learn the benefits of log forwarding with any workflow applications. Your team just built a custom asset processing profile worker to add watermarks to your assets in Adobe Experience Manager. It’s running well in production, but you notice that at times it didn’t produce the correct output. How do you debug that? How can you better monitor the health of your custom application? Join us to learn about log forwarding in any App Builder application, including custom asset processing profile worker. In this session: 1. Learn about the benefits of forwarding your App Builder application logs 2. A demo of log forwarding in action 3. Getting started with log forwarding for App Builder applications Session Recording Session Schedule 2022-03-16 | 11:30:00 PST | 30 Mins Duration Speaker(s) Manik Jindal & Olga Kopylova Moderator(s) Adobe Resource(s) Product(s) Adobe Experience Manager
Session Details Join this session to see how to GraphQL enables teams to create, update & delete content in fragments that can be consumed at scale by the headless implementation. With the rising popularity of the headless approach to content management, the Adobe Experience Manager hybrid content editing capabilities continue to evolve to accommodate. Using the power of GraphQL, developers can enable business users to create, update, and delete structured content in the form of content fragments. Data from these fragments can be consumed efficiently at scale by any headless implementation. Developers or data architects can also work alongside business users to create content fragment models to define the desired data structures. These models contain the necessary information to let developers accurately query and consume the content using GraphQL APIs. Learn how to empower business users to play a vital role on the web team by freeing developers from the work of content updates.
Session Details Learn how to use Adobe’s Cloud Acceleration Manager application to ensure a smooth and successful transition to Adobe Experience Manager in the Cloud. Adobe Experience Manager as a Cloud Service provides you with a modern cloud foundation to help your teams accelerate their customer experience management initiatives and stay ahead of the curve. With Adobe’s tried-and-tested transition methodology and tools, you can accelerate the transition of your Adobe Experience Manager application from an on-premises implementation to Experience Manager as a Cloud Service. In this 60-minute training workshop, learn how to get started on this transition journey with Adobe’s Cloud Acceleration Manager application, designed to ensure a smooth and successful transition to the cloud. Learn how to: 1. Read readiness reports in Cloud Acceleration Manager to self-assess your readiness 2. Outline a clear transition strategy and define the migration activities 3. Create a successful go-live
Set Cookie Example of AEM Servlet and Sling Model by SourceCode Abstract In this short article, we will show two code examples; for example, one will be showcasing how cookies values can be set for an AEM Servlet, and for example two, Sling Model. 1. AEM Servlet Set Cookie Example package com.sourcedcode.core.servlets; import com.cat.wcm.core.util.JSONObject; import org.apache.sling.api.SlingHttpServletRequest; import org.apache.sling.api.SlingHttpServletResponse; import org.apache.sling.api.servlets.SlingAllMethodsServlet; import org.osgi.service.component.annotations.Component; import javax.servlet.Servlet; import javax.servlet.http.Cookie; import java.io.IOException; import static org.apache.sling.api.servlets.ServletResolverConstants.SLING_SERVLET_PATHS; @Component( service = { Servlet.class }, property = { SLING_SERVLET_PATHS + "=/bin/setCookieExample" } ) public class SetCookieServletExample extends SlingAllMethodsServlet { @Override protected void doGet(SlingHttpServletR
Get Cookie Example of AEM Servlet and Sling Model by SourceCode Abstract In this short article, we will show two code examples; for example, one will be showcasing how cookies values can be accessed for an AEM Servlet, and for example two, Sling Model. 1. AEM Servlet Get Cookie Example package com.sourcedcode.core.servlet; import com.cat.wcm.core.util.JSONObject; import org.apache.commons.lang.StringUtils; import org.apache.sling.api.SlingHttpServletRequest; import org.apache.sling.api.SlingHttpServletResponse; import org.apache.sling.api.servlets.SlingAllMethodsServlet; import org.osgi.service.component.annotations.Component; import javax.servlet.Servlet; import javax.servlet.http.Cookie; import javax.servlet.http.HttpServletRequest; import java.io.IOException; import static org.apache.sling.api.servlets.ServletResolverConstants.SLING_SERVLET_PATHS; @Component( service = { Servlet.class }, property = { SLING_SERVLET_PATHS + "=/bin/getCookieExample" } ) public class GetCookieSer
How to deal with Oak login token session expiration and token refresh in AEM by Debal Das Abstract I believe we are all aware with session expiration and token refresh process. We have encountered these two situations with numerous web applications , even with our work day profile also. Now if it’s required to deal with session expiration and token refresh in AEM instance then we must be thinking do we have any OOTB feature in AEM or we need to develop a custom logic. Yes, we do have following OSGi configuration in AEM: Apache jackrabbit oak TokenConfiguration as shown below - Let’s suppose we need to set this token expiration time for 30 minutes and also we need to enable the token refresh process. Let’s suppose we need to set this token expiration time for 30 minutes and also we need to enable the token refresh process. We can achieve it very easily as shown below - Please restart the AEM instance after saving these changes. Here, I have done it on local AEM author instance and I
Troubleshooter #1 : PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException for Node.js installation error in ui.frontend. by Nikhil Kumar Abstract Along with the technical articles on AEM, I have started a Troubleshooter series which will help developers to troubleshoot any error or any blocker while working on AEM code in local. In this article we will look into the below error which I have seen coming up from quite sometime with new archetypes( mostly 27+) while building the project for the first time. Error As per the above error we can clearly see that it’s not able to download node – v12.14.1 which is required for ui.frontend module in our AEM codebase. Now to rectify this error we need to follow below steps: 1. Copy and paste the URL which is market in blue in above image in any browser. 2. Once you do so a node.exe will be downloaded in your PC. 3. Go to C:\Users\.m2\repository\com\github\eirslett\node. 4. Now create a folder with the same ver
Custom Rich Text Editor (RTE) Plugins for Adobe Experience Manager by Bounteous Abstract Out-of-the-box (OOTB) plugins and their features cover many text editing use cases, but there will always be a need for customization. Recently, I came across a requirement where authors wanted the flexibility to add data attributes to the HTML elements for analytics tracking using the Text component RTE capabilities in Adobe Experience Manager (AEM). Learn how to add a custom tool to RTE that will add data attributes to a specific element within HTML by following the steps outlined in this article. This same process can be used for any other custom RTE Tools you have to add as well. By following these steps, you will enable the author to add attributes or remove attributes using the in-place editing toolbar in AEM, as can be seen below. How to Add a Custom Plugin to RTE? Adding a new plugin to RTE is a five-step process and involves JavaScript coding. Create a new Clientlib and provide Catego
Dam UI card View Error : Fail to load dataI'm fairly new to AEM, when the build is get installed in the crxde, there is a default metadata schema is creating automatically under /conf/global/settings/dam/adminui-extension/metadataschema. With this folder if we go to DAM card view it will show an Error saying Fail to load data.If I'm removing this folder , there won't be any error. in error logs it is saying as follows. GET /mnt/overlay/dam/gui/content/assets/jcr:content/views/card.0.20.html/content/dam/nexus/en HTTP/1.1] com.day.cq.wcm.tags.IncludeTag Error while executing script ../common/card-banner.jsporg.apache.sling.api.scripting.ScriptEvaluationException: An exception occurred processing JSP page /libs/dam/gui/coral/components/admin/contentrenderer/card/common/card-banner.jsp at line 363
Hi All,After activate the bundle in Adobe experience manager web console bundles getting following exception in error.log file:Please give me solution for above problem.
AEM - Touch UI Dialog | Field Description with Image by Arun Patidar Abstract In Touch UI dialog Coral/Granite type fields have fieldDescription property which displays the help text(tooltip) for a field. The value for this property is restricted to have plain text. property and It will show fields in a dialog. Improve Authoring Experience With the headless architecture where the presentation layer is separated from AEM and Author does not have a view on WYSIWYG, to provide a view of how the content is gonna render can be implemented in many ways. One of the options is to use an image in the field description. OOTB Coral/granite type does not support the HTML tags(due to the encoding), which could have been used to add an image in fieldDescription property. To overcome this situation an image can be added as another property fieldDescriptionImage e.g. using data attribute fieldDescriptionImage = /content/dam/aemlab/system/components/sample/dialog/text.png The fieldDescriptionImage
Hi All, I am working on integration of a channel with Adobe Analytics using data insertion API. Just wanted to understand how Adobe creates visit KPI for data flowing from data insertion API without time stamps. Thanks in Advance
Server: AEM-6.5.1 SP-6.5.1OS: RHEL7Oak: 1.10.2We use SAML for authentication, this server is migrated from AEM 6.3 to 6.5 a month back.The users were able to log in but recently a couple of users not able to log in and the "SamlAuthenticationHandler" error is captured in the error.log.I have attached the log.
A new option has been added in the Error management properties of workflow activities - The Abort on error option. This option will stop the workflow automatically and you will not be able to restart it afterwards. To know more, read here in the dedicated documentation: Abort on error option Please feel free to reach out for your queries and feedback in the below comment section.
AEM - Restricting CRXDE Access for few users by Arun Patidar Abstract In AEM, CRXDE access can be disabled by 1. Disabling the required bundles Adobe CRXDE Support (com.adobe.granite.crxde-support) Adobe Granite CRX Explorer (com.adobe.granite.crx-explorer) Adobe Granite CRXDE Lite (com.adobe.granite.crxde-lite) 2. From dispatcher https://helpx.adobe.com/experience-manager/kb/LimitAccessCRXandCRXDE.html What if CRXDX needs to be disabled/restricted for a few users/groups. One of the solutions could be to check the user when the user attempts to access CRXDE and block the access or re-route. Step to Implement the above approach : 1. Create a Sling Filter to check the CRXDE access request. 2. Create an OSGi configuration and service to maintain restriction data(Users, groups, excluded user) 3. Create a clientlibs to re-route the user to another page while accessing CRXDE. In the Sling Filter get the current user and check against service configuration and if found then replace/redir
In AEM 6.2 I created a simple workflow model with only participation steps. This is for reviewing/approving/publishing AEM Content Fragments.I tried two options, but one doesn't work and the other seems to have an error...I created a workflow launcher that listens to the AEM Content Fragment section in /content/dam. When a change is made, the workflow gets triggered correctly. In the Inbox is also the link to the content fragment. When clicking the link, a download box appears that will download the content fragment as a physical file. This is not good for review purposes.In the navigation page I selected the content fragment. Then I selected "Timeline" and from there "Workflow". I selected the workflow model and started the workflow. The payload shows a different link now. When clicking on the payload link, nothing happens. If I select an asset, e.g. an image, these links show the image. But with an AEM Content Fragment the link does nothing.When I though mouse over the link, the stat
Hi All, We have seeing the blank page while accessing the OSGi console in Production author instance. We have tried to restart the server but still the issue persists.Please note - we are not seeing the issue in lower environments and Production Publisher. All the bundles are in Active and we don't see anything in the error log as well. Anyone faced this issue ?
I am looking for a solution to document a custom component, more like a Component Library or Storybook for the author team and developers. Searching for the same, I came across the ui.frontend module guide on experience league. The first thing is regarding Component Library, it has mentioned that "we could use Component Library and work at the component level rather than the page level." Is there any document/guide that shows how to implement this?Link to section Using Webpack Static Development Server: https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/archetype/uifrontend.html?lang=en#using-webpackRegarding Storybook, there is a section in the doc on "Using Storybook" (attached a link below). It has been mentioned that "...you can install it and store your Storybook artifacts within the ui.frontend module. When ready for testing within AEM, they can be deployed as ClientLibs by running npm run dev." I have no clue on how to impl
Authors: @danny-miller, Shruti Jagtap, Douglas Paton In this post, we look at the process for capturing the latest event experience across multiple products in Adobe Experience Platform. We also dive into how this technique can be used to create dynamic list segmentation for these products. Data models can sometimes be structured in such a way where you can track different types of events in one schema/dataset. For example, this might be a single dataset that has all subscriptions for newsletters or subscriptions. The data structure might be common, but you have many newsletters across many products with differing statuses over time. When subscribe and unsubscribe events are tracked as individual events, it is common to want to know what the current state is so that you can deliver the next best customer experience. To address this, we considered two approaches during implementation for a customer: Track the current state on an Array on the profile Use a segment against the
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.