Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
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 Classic Community forums, we present to you the two top users in the Community for the month of May 2021 - @wodnicki and @CedricRey Congratulations and a big thanks to both of you for being dedicated and helpful community members of the Adobe Campaign Communities. Become the 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 Classic Community forums, we present to you the two top users in the Community for the month of May 2021 - @jonathon_wodnicki and @cedricrey 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 Campaign Classic, and ca
Using Metadata Import and Export in AEM Assets by Adobe Docs Abstract Learn how to use the import and export metadata features of Adobe Experience Manager Assets. The import and export capabilities allow content authors to bulk update metadata for existing assets. Metadata Export and Import Metadata CSV File Format First Row The first row of the CSV file defines the metadata schema. The First column defaults to assetPath, which holds the absolute JCR Path for an asset. Subsequent columns in the first-row point to other metadata properties of an asset. For example : dc:title, dc:description, jcr:title Read Full Blog Using Metadata Import and Export in AEM Assets Q&A Please use this thread to ask the related questions.
AEM - Explore GraphQL APIs by Adobe Docs Abstract The GraphQL API of AEM provide a powerful query language to expose data of Content Fragments to downstream applications. Content Fragment models define the data schema that is used by Content Fragments. Whenever a Content Fragment Model is created or updated, the schema is translated and added to the “graph” that makes up the GraphQL API. In this chapter, we will explore some common GraphQL queries to gather content using an IDE called GraphiQL. The GraphiQL IDE allows you to quickly test and refine the queries and data returned. GraphiQL also provides easy access to the documentation, making it easy to learn and understand what methods are available. Prerequisites This is a multi-part tutorial and it is assumed that the steps outlined in the Authoring Content Fragments have been completed. Objectives Learn to use the GraphiQL tool to construct a query using GraphQL syntax. Learn how to query a list of Content Fragments and a single
Use workflow to automate asset updates for an AEM Screens channel by Adobe Docs Abstract Learn how to create a workflow to automatically process assets uploaded to Adobe Experience Manager and dynamically assign them to a Screens channel. In this example, when an image is added to a specific folder, a workflow is triggered that applies a dynamic text overlay (watermark process) and assigns the image to a Screens channel. Lessons learned from this example can be applied to a wide variety of automation scenarios. Prerequisites To complete this tutorial the following is needed: AEM 6.5 AEM Service Pack 8 or greater AEM 6.5 Screens FP7 or greater Quick setup The below video illustrates how to install a sample code package that will introduce a new workflow to Adobe Experience Manager. This feature allows a user to update the properties of a folder in AEM Assets to point to a Screens channel. Whenever an image is added to that folder it will be added to the specified screens channel. Rea
AEM - Create a site by Adobe Docs Abstract This chapter covers the creation of a new site in Adobe Experience Manager. The Standard Site Template, provided by Adobe, is used as a starting point. Prerequisites The steps in this chapter will take place in an Adobe Experience Manager as a Cloud Service environment. Ensure that you have administrative access to the AEM environment. It is recommended to use a Sandbox program and Development environment when completing this tutorial. Review the onboarding documentation for more details. Objective Learn to use the Site Creation Wizard to generate a new site. Understand the role of Site Templates. Explore the generated AEM site. Log in to Adobe Experience Manager Author As a first step, log in to your AEM as a Cloud Service environment. AEM environments are split between an Author Service and a Publish Service. Read Full Blog AEM - Create a site Q&A Please use this thread to ask the related questions.
Author content and publish changes by Adobe Docs Abstract It is important to understand how a user will update content for the website. In this chapter we will adopt the persona of a Content Author and make some editorial updates to the site generated in the previous chapter. At the end of the chapter, we will publish the changes to understand how the live site gets updated. Prerequisites This is a multi-part tutorial and it is assumed that the steps outlined in the Create a site chapter have been completed. Objective Understand the concepts of Pages and Components in AEM Sites. Learn how to update content of the website. Learn how to publish changes to the live site. Create a new page A website is typically broken into pages to form a multi-page experience. AEM structures content in the same way. Next, create a new page for the site. Log in to the AEM Author Service used in the previous chapter. From the AEM Start screen click Sites > WKND Site > English > Article In th
AEM - Page templates by Adobe Docs Abstract In this chapter we will explore the relationship between a Page Template and a Page. We will build out an un-styled Magazine Article template based on some mockups from AdobeXD. In the process of building out the template, Core Components and advanced policy configurations are covered. Prerequisites This is a multi-part tutorial and it is assumed that the steps outlined in the Author content and publish changes chapter have been completed. Objective Inspect a page design created in Adobe XD and map it to Core Components. Understand the details of Page Templates and how policies can be used to enforce granular control of page content. Learn how Templates and Pages are linked. What you will build In this part of the tutorial, you will build a new Magazine Article Page template that can be used to create new magazine articles and aligns with a common structure. The template will be based on designs and a UI Kit produced in AdobeXD. This chapt
AEM - Theming workflow by Adobe Docs Abstract In this chapter we will update the theme sources of an Adobe Experience Manager Site to apply brand specific styles. We will earn how to use a proxy server to view a preview of CSS and Javascript updates as we code against the live site… This tutorial will also cover how to deploy theme updates to an AEM Site using GitHub Actions. In the end our site will be updated to include styles to match the WKND brand. Prerequisites This is a multi-part tutorial and it is assumed that the steps outlined in the Page Templates chapter have been completed. Objectives Learn how the theme sources for a site can be downloaded and modified. Learn how code against the live site for a real-time preview. Understand the end-to-end workflow of delivering compiled CSS and JavaScript updates as part of a theme using GitHub Actions. Update a theme Next, make changes to the theme sources so that the site matches the look and feel of the WKND Brand. Read Full Blog
Repository Modernizer by Adobe Docs Abstract Repository Modernizer is a utility developed to restructure existing project packages by separating content and code into discrete packages to be compatible with the project structure defined for Adobe Experience Manager as a Cloud Service. Introduction Adobe Experience Manager as a Cloud Service brings many new features and possibilities into your AEM projects. However, there are some changes required to Adobe Experience Manager Maven projects to be compatible with AEM Cloud Service. At a high-level, AEM requires a separation of content and code into discrete sub-packages to respect the split between mutable and immutable content. Please refer to AEM Project Structure for more details about the new AEM project structure for Cloud Service. The Repository Modernizer creates a compatible AEM Cloud Service project structure by creating the following deployment structure: ui.apps package deploys to /apps and contains all the code ui.content
AEM - Quick setup SPA Editor and Remote SPA by Adobe Docs Abstract Video: https://images-tv.adobe.com/mpcv3/5247/4df87c93-5bc0-43bc-94c3-6547e4d36c84_1620333042.854x480at800_h264.mp4 Quick Setup Quick setup is an expedited walk-through illustrating how to install and run the WKND App and as a Remote SPA, and author it using AEM SPA Editor. Quick setup takes you directly to the end state of this tutorial. Prerequisites This tutorial requires the following: AEM as a Cloud Service SDK Node.js v14+ npm v7+ Java™ 11 Maven 3.6+ Git macOS only prerequisites Xcode or Xcode command line tools aem-guides-wknd.all.0.3.0.zip or greater aem-guides-wknd-graphql source code This tutorial assumes: Microsoft® Visual Studio Code as the IDE A working directory of ~/Code/wknd-app Running the AEM SDK as an Author service on http://localhost:4502 Running the AEM SDK with the local admin account with password admin Running the SPA on http://localhost:3000 Read Full Blog AEM - Quick setup SPA Editor an
If your form’s Thank You page is on a different private domain — not just another subdomain of your main domain — and you want to pass over form values, they need to be appended to the query string.[1] For example, if you’re forwarding people to a partner site, they probably have a keen interest in the person who filled out the form. Below is a little bit o’ Forms 2.0 JS to append form fields — only the fields you want, so you can protect PII if necessary — to the Thank You URL for next-hop processing. Usage is pretty simple: put the fields you want to append to the Thank You in the array appendFieldsToTYQuery. For each item: Set mktoField (required) to the Marketo form field name. By default, the field name is the query param name, too. Set queryParam (optional) to have the query param name be different. Set onURIEncode (optional) as a callback to make additional changes to the passed value, like uppercasing it or what-have-you. /* * Append poste
Hi Team,Is there a way to add tabs dynamically in touch ui dialog.I have a requirement as follows-1. We have a composite multifield something like in the below example-http://experience-aem.blogspot.co.nz/2016/06/aem-62-touch-ui-composite-image-multifield.html2. Here we are adding the fields in the same tab on click of add field button, instead if we want to add new tab on click of addfield and there again user will fill the same set of fields.We are trying to achieve this as we have 10 fields as part of multifield.Please let us know if we can achieve this.Regards
Albertsons Companies leans on Adobe Experience Cloud as it redefines the grocery shopping experience by David Carrel Abstract In a year where consumers spent a lot more time at home, many have dipped their toes into new ways of doing things. Whether out of necessity or curiosity, websites and apps took on new meaning for many of life’s daily tasks. Through Adobe’s Digital Economy Index, a real-time barometer of online shopping, we saw categories like home improvement grow 60 percent year-over-year. The breakout star however, was in groceries. In February 2021, online grocery shopping in the U.S. grew 230 percent compared to a pre-pandemic period. COVID-19 quickly became a catalyst for consumer behaviors that were already bubbling to the surface. While pushing a cart still works for many grocery shoppers, some prefer going online for speed and efficiency. What we buy is changing as well, as more people look beyond ingredients and seek out meal-oriented offerings that save time and ene
Getting to Know the Adobe I/O Architecture: Experience Cloud Use Cases by Rohan Kapoor and Santosh Mishra Abstract APIs are a way for us to retrieve data from any service, be it a music streaming service, traffic navigation service, or a customer data platform such as Adobe Experience Platform. APIs can be used via serverless computing, an architecture model that allows developers to write and execute code without needing to provision any servers (hardware), which is costly. It’s a revolutionary concept; it is a far cry from the traditional hosted server technology and expedites the code delivery and execution process. There are lots of advantages to serverless that we won’t cover in this post (this article explains it in a bit more detail), but at a high level we can leverage serverless technology to address use cases around third-party integrations, batch file processing, and IoT devices to name a few. In this article, we will take a deep dive into Adobe I/O, which is a one-stop sh
Combining Headless and Traditional Architecture | AEM by Aemsimplifiedbynikhil Abstract Hello AEM folks!! I was going through some of the documentations of Adobe on the usage and benefits of hybrid architecture. I will try to summarize the details around the same. Basically a Hybrid Architecture is a combination of the concepts of traditional and headless CMSs into a single architecture. So let’s go ahead and understand the traditional and headless architecture briefly. 1. Traditional Architecture: A traditional architecture uses a single tech stack, it holds all the templating, logic and produces a formatted HTML as an final output. It provides an end to end solution but the only disadvantage is that it works only with limited number of channels. like websites. Below are some of the advantages of traditional architecture: Provides consistent personalized experience. Enables to update presentation and layout with in-context previews. Reduces the cost of ownership due to single tech s
Manipulating Content - The SlingPostServlet (servlets.post) by sling.apache.org Abstract Multiple Ways to Modify Content As always in life there is more than one way to do it. So to modify content in Sling, you have multiple options, the Sling default POST Servlet also called the SlingPostServlet is one of them. This page is about how you can modify - create, modify, copy, move, delete, import - content through the SlingPostServlet. In addition it also explains how to extend the SlingPostServlet with new operations. Quickstart: Creating Content To create content you simply send an HTTP POST request using the path of the resource to store the content in and include the actual content as request parameters. So one possibility to do just that is by having an HTML Form like the following: This simple form will set the title and text properties on a resource at /some/new/content. If this resource does not exist it is just created otherwise the existing content would be modified. Simila
hirobe talks to : Tadd Reeves, AEM Architect & Consultant by Ted Reeves Abstract Video: https://www.youtube.com/watch?v=WVJW2BdkUJY Tom from hirobe chats to AEM Architect & Consultant Tadd Reeves about AEM as a cloud service, managing effective Adobe Experience Manager deployments and why having good AEM developers has never been more important. Read Full Blog hirobe talks to : Tadd Reeves, AEM Architect & Consultant Q&A Please use this thread to ask the related questions.
This blog is Part 2 of a three-part series that will cover how anyone could use Adobe Target NodeJS SDK to run experimentation and personalization on an edge compute platform. The parts are: Part 1: Akamai Edge Workers and Adobe Target NodeJS SDK, by @artur-ciocanu Part 2: AWS Lambd@Edge and Adobe Target NodeJS SDK, by @artur-ciocanu Part 3: Cloudflare Workers and Adobe Target NodeJS SDK Check it out today, and stay tuned here for Part 3!
I have created multiple data sources through sling:OsgiConfig nodes in the run mode configuration. I can also see these configurations in configurations manager screen.I am trying to get database connection using below code:@Reference private DataSourcePool dspService;....getConnection(){ DataSource ds = (DataSource) dspService.getDataSource("abc-xyz");.....}I get an error:com.day.commons.datasource.poolservice.DataSourceNotFoundException: No data source found with name 'abc-xyz' (after asking 0 providers).If I open the config manager and save the configurations again, connection works successfully. Why is the behavior shown ?I tried the following solution.I created a bundle activator and put the code to programmatically update the configurationsServiceReference serviceRef = context.getServiceReference(ConfigurationAdmin.class.getName());ConfigurationAdmin configAdmin = (ConfigurationAdmin) context.getService(serviceRef);String filter = '(' + C
I have Create a new AEM Project with Archetype 26 and i faced the below issue and resolve it. Please follow the step below for the setup a new project.1. Setup Java 11(Recommended)2. Setup AEM 6.5 Instance. Once AEM is setup then installed the "aem-service-pkg-6.5.4.zip" service package.3. Create a new Project structure using the below command:mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=26 -D appTitle="My Project" -D appId="myproject" -D groupId="com.myproject.aem" -D artifactId="myproject-aem-project" -D version="0.0.1-SNAPSHOT" -D aemVersion="6.5.4" -D includeDispatcherConfig=n -D includeExamples=nWhenever run the above command getting below error while creating a project structure with dispatcher modules.ERROR : Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.1.2:generate (default-cli) on project standalone-pom: java.nio.file.FileSystemException: Project path(Example: /Myproject
I want using the functionality and i want override the the component injected in my site page "cq/experience-fragments/editor/components/experiencefragment" with my custom experience fragments component (inherited from core component). Is it possible? If not, i evaluate to remove the shortcut functionality by replacing with manual steps:1) create an experience fragment template variation2) create the content including a component like the page references (replicating the same data entry)3) introducing in my site page the custom experience fragment component and apply the reference with point 14) delete the component replaced with point 3... Thank you in advance for your help.
Use this thread to ask any questions related to the upcoming course "Getting started with Query Service for Data Engineers" on Experience League. Experts are monitoring this thread to ensure your questions are answered.
Session Details In the 2-hour Building Single Page Applications with Adobe Experience Manager training workshop delivered by Adobe Learning Services expert instructors, you will learn the AEM project structure with a React frontend module. Participants will... Session Schedule Wednesday, Apr 28 1:00 AM - 3:00 AM IST Speaker(s) Iain Maguire, Senior Instructor, ADLS, Adobe Full Schedule Check Here Q&A Please use this thread to ask the question related to this Session. Don't forget to register yourself for this session @ Adobe Summit 2021.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.