Product Communities

Adobe Experience Manager 6.5 vs WordPress - Feature Comparison by Shivanand Yeurkar Abstract For many years WordPress has been the most popular CMS platform for blogs and marketing sites among small and mid-sized companies. Easy to set up, OTB plugins, and excellent community support make it the right choice if your goal is to bring up a site quickly in a cost-effective way. With a growing digital footprint and cross channel customer journey, enterprise marketing teams need to have a tighter and agile cross-channel campaign orchestration. This requires a modern platform that allows marketers to do faster delivery of content and create a cross experience and personalized experience. Adobe AEM is the most popular Web CMS platform that meets all modern enterprise marketing teams’ demands. Limitations of WordPress as an Enterprise CMS? WordPress provides many out of box templates for different types of online experiences. However, these templates are not flexible at all and often requir

OSGi Bundle States in AEM by Codingwithtea Abstract OSGi is a fundamental element in the technology stack of AEM. It is used to control the composite bundles of AEM and their configuration. OSGi “provides the standardized primitives that allow applications to be constructed from small, reusable and collaborative components. OSGi OSGi is a Java framework for developing and deploying modular software programs and libraries. OSGi has two parts. Bundles or Plug-in Java Virtual Machine (JVM)-level service registry. In this article, we will focus on bundle states only. A Bundle object is the access point to define the lifecycle of an installed bundle. Each bundle installed in the OSGi environment must have an associated Bundle object. A bundle must have a unique identity, a long, chosen by the Framework. This identity must not change during the lifecycle of a bundle, even when the bundle is updated. Uninstalling and then reinstalling the bundle must create a new unique identity. Read F

AEM 6.5 Upgrade Part 1: Discovery and pattern detector analysis by Taqalytics Abstract AEM upgrade is a multi-step process that depends on scope of the upgrade and requirements defined in the discovery phase. Adobe documentation has covered various steps on how to upgrade, but the code upgrade process itself isn’t discussed in much detail and is different for each project. We will be covering a few topics related to code and customizations for the AEM 6.5 upgrade from the lower version. List down the AEM Upgrade Scope and Requirements During the discovery phase, identify key elements and make an inventory of existing code repositories. This list must have adobe standard requirements for upgrade and any custom requirements from the customer. Here are some prerequisites to consider – Technical requirements: Adobe supports Adobe Experience Manager (AEM) on the platforms as detailed in the following information – https://experienceleague.adobe.com/docs/experience-manager-65/deploying

Hey Everyone, Visit one of my published topic Part 7 out of 8- AEM Run ModesRepository based configurationRun modes & OSGI configsConfiguration managerOSGI property typesSummaryI’m sure there is a tricky new information about Run Mode you get it in the video, please have a look!https://www.techinnovia.com/run-modes/Feel free to share your feedback on blog. Happy Learning!Cheers!!

Hi All, I would like to customize the view and some flow changes of CIF Core component as per my own requirement. As example I would like to adapt the mini cart to my own HTML wireframe not just by customizing the css, also would like to do some changes in React components (https://github.com/adobe/aem-core-cif-components/tree/master/react-components/src/components/Minicart). And also I am not able to find the documentation for how to customize the CIF React components. It will be great if someone can help me to achieve that and help me with the documentation. Thanks In Advance

I have a template for a custom component heroTeaser that I would like to inherit in another custom component called homeHeroTeaser. How do I do it?  In the new custom component I have configured sling:resourceSuperType="xxx/components/content/heroTeaser" Is the homeHeroTeaser.html required? If not, how does it know it has to call heroTeaser.html?

The purpose of this thread is to continue the conversation from the Virtual User Group on the topic of Transitioning to the New Workfront Experience on February 2, 2021. Many thanks to everyone who came to our virtual meetup! Special thanks to @Kate McGuinness‚ for sharing her perspective and guidance, and to @Brittney Lewis‚ for sharing more about the journey SSGA has been on. As promised, attached is a PDF of the presentation, and you can watch the recording here. Do you have any outstanding questions related to the new Workfront experience? If you've started your transition, how's it going? Is there anything you'd share with those about to start? Or if you haven't started your migration, what's holding you back? Leave a comment below and we’ll keep the conversation going. Thanks again. If you have any feedback (good or bad), please don’t hesitate to reach out. You can find the schedule for all upcoming User Groups on the Events page on Workfront One (one.workfr

Press Release: Bounteous Selected to Inaugural Adobe Experience Manager Champion Class and adds Dom DeGustino as SVP, Digital Strategy & Solutions to Adobe Practice by Bounteous Abstract CHICAGO — May 17, 2022 — Bounteous continues to invest in its award-winning Adobe Practice as it increasingly becomes the go-to choice for companies that use Adobe Experience Cloud to deliver amazing digital experiences at scale rapidly. Bounteous has hired Dom DeGustino as Senior Vice President, Digital Strategy and Solutions to drive the go-to-market strategy and growth of the Adobe Practice. Additionally, they announced that Brett Birschbach, VP AEM Engineering at Bounteous, was recently selected as one of only 18 members of Adobe's inaugural 2022 Adobe Experience Manager Champion Class. DeGustino, most recently Senior Director Client Lead & Growth at Gorilla Group, has more than 15 years of experience in strategy, sales, and digital transformation services. Dom is an expert in positioning

<categorycq:showOnCreate="{Boolean}true"granite:class="page-tagging-inheritance"jcr:primaryType="nt:unstructured"fieldLabel="page.category.label"fieldDescription="page.category.label.desc"sling:resourceType="cq/gui/components/coral/common/form/tagfield"autocreateTag="{Boolean}false"emptyText="page.tag.singleSelect.emptyText"name="./pagetagging/category"required="{Boolean}true"rootPath="/content/cq:tags/com/careers/category/"><granite:datajcr:primaryType="nt:unstructured"cq-msm-lockable="pagetagging/category"category-field=""/></category>I have the above and it is getting the correct tags because I used rootPath to have a specific tags to use. Now I want to only show the parent tags and not the child tags .Is this possible ? I tried using datasource but the data in datasource is not use for the tags.I want to show only the parent like the first tag and remove the child tag for the 2nd and third tags.

AEM 6.5.10.0 - Visibility rules in Content Fragment Editor using Naming Conventions by Sreekanth Choudry Nalabotu Abstract Goal Support Field Visibility in Content Fragment Editor. Visibility Rules are available in Metadata Schema editor out of the box; this post provides a simple rule based visibility in CF editor using naming conventions.... Solution 1) Create a clientlib /apps/eaem-cf-visibility-group/clientlibs/clientlib-cfv with categories=dam.cfm.authoring.contenteditor.v2 and dependencies=[lodash.compat], add below code to make the editor dynamic and follow naming conventions for visibility... (function ($) { const URL = document.location.pathname, CFFW = ".coral-Form-fieldwrapper", BORDER_STYLE = "1px solid #AAA", FIELD_TYPE_SELECTOR = "coral-select[name$='FieldType']"; let initialized = false; if( !isCFEditor() ){ return; } init(); function init(){ if(initialized){ return; } initialized = true; window.Dam.CFM.Core.registerReadyHandler(addFieldGrouping); } function add

How To Pre-Populate Values In AEM Component by Heena Shirke Abstract Let's continue with the first component we created here. This component has two text fields Title and Description. By default these values are not set. To set the values on include of a component follow the given steps: 1.Create a node of type"nt:unstructured" named "cq:template" inside your component. 2. We will add the default value with same name key on "cq:template" node. Note: The values will be pre-filled only on include of the component. In scenarios, where the value gets stored in sub node(For example multifield stores the values in tree structure when composite is set to TRUE), create same structure under the "cq:template" node. Lets take another example to understand this scenario: Component created in this post stores data in following structure. So, the "cq:template: node for this component will look like this: Wouldn't it be repetitive to add this node in each component? "cq:templatePath" can be

AEM How To Create A Multi-field by Heena Shirke Abstract What is a Multi-field? Mulitifield allows you to create a set of input fields. Let's take Header Navigation Items as an example. In such case navigation items count is not constant and thus we need cannot create fixed list of fields. So, instead we will create a multi-field. Let's create a multi-field with following input fields. Name URL Steps to create nodes:(For all steps create nodes of type nt:unstructured) 1. Create node called "multifieldcollection" with following properties: sling:resourceType="granite/ui/components/coral/foundation/form/multifield" composite="{Boolean}true" fieldDescription="Click + to add a new page" fieldLabel="Multifield collection" 2. Create node named "field". Add following properties to it name="./multifieldList" sling:resourceType="granite/ui/components/coral/foundation/container" 3. Create node named "items" under "field". 4. Create "column" under "items" and add following property to

How to generate an AEM Project by Heena Shirke Abstract Today we will generate an AEM Project using a Maven archetype with the help of command line. Prerequisites: JDK should be installed Maven should be installed What is Maven Project? Apache Maven is a software project management and comprehension tool. All Adobe Experience Manager Projects leverage Maven Project to generate, build, and deploy code. What is Maven Archetype? Archetype is a Maven project templating toolkit. AEM requires project code to be in particular structure. To generate this pre-created structure we use "aem-project-archetype" as an Archetype Id. Paste the following into the command line to generate the project in batch mode and hit ENTER: mvn -B archetype:generate \ -D archetypeGroupId=com.adobe.aem \ -D archetypeArtifactId=aem-project-archetype \ -D archetypeVersion=35 \ -D appTitle="WKND Sites Project" \ -D appId="wknd" \ -D groupId="com.adobe.aem.guides" \ -D artifactId="aem-guides-wknd" \ -D packa

What is an AEM Component? by Heena Shirke Abstract Remember the first html project you created in your college days? We added all the content in html even if it was repetitive. Lets take an example of following page: Here, to create this simple structure I had to copy paste same structure. This was okay during college days, however, things will become complex in real world and this approach will not work in real scenarios. So, to increase the maintainability of the code and content and avoid duplicity, we have something called components in AEM. In simple words, component is the block of code which we can add to a page multiple times without duplicating the code. Going back to the example, to create same structure in an AEM Page we will create a component with accepts a title and description and add it 3 times to the page. Lets create an AEM component with same structure: 1. Go to your project in apps folder where you want to create a component in CRX. 2. Right click on the fol

How to configure s3 in AEM by Aemrules Abstract Configuring s3 data stores in AEM 6 In Adobe Experience Manager (AEM), binary data can be stored independently from the content nodes. The binary data is stored in a data store, whereas content nodes are stored in a node store. Both data stores and node stores can be configured using OSGi configuration. Each OSGi configuration is referenced using a persistent identifier (PID). In this article we learn the detailed steps for configuration S3 data store in AEM. You can get the architectural level understand of S3 with AEM from article - https://www.aemrules.com/2021/06/how-does-s3-works-with-aem.html Amazon S3 Data Store AEM can be configured to store data in Amazon’s Simple Storage Service (S3). It uses the org.apache.jackrabbit.oak.plugins.blob.datastore.S3DataStore.config PID for configuration. In order to enable the S3 data store functionality, a feature pack containing the S3 Datastore Connector needs to be download

Adobe Experience Manager 6.5: everything you need to know about the system by Shruti Damle Abstract Adobe Experience Manager (AEM) is an enterprise content management system that covers dynamic digital asset management, contact form and document management solutions, online community experience management, user-generated content organisation and countless social engagement features. AEM acts as a central hub for creative, marketing and IT teams, ensuring that processes and media delivery are seamlessly streamlined across all departments. AEM aids siloed teams with managing their digital assets, and the solution further provides an arena for delivering attractive media enhanced for different channels on demand. AEM version 6.5 connects with other Adobe products such as Creative Cloud and Marketing Cloud. This enables teams to create, curate, and distribute media across various avenues to ensure an enriching journey for customers. Overall benefits of Adobe Experience Manager 6.5 inclu

This post is part of a series about auto-taggingTagging Standards will allow you to set up a set of rules for your tagging team members to follow. By following them we will ensure that the content of your Adobe Launch container is secure, maintainable, and reusable.Naming ConventionAs a member of the tagging team, a big part of your daily job involves working inside the Adobe Launch interface. Without proper naming, you will soon realize that it is very difficult to maintain over time. Example of good naming convention:use camelCase when possible. This is particularly useful for data elements and direct call rules. Try to avoid snake_case or PascalCasenever use a single character to describe the web property, rule, data element, or a buildnever use trailing or leading underscores (except if it refers to_satellite object)acronyms and initialisms should always be capitalized or all lowercaseinactive rules and data elements should be prepended by zzz so you can filter

I don't know why the where to buy button is disabled, any ideas?   

I am experiencing the exact issue logged more then 1 year ago on the AEM core components: https://github.com/adobe/aem-core-wcm-components/issues/1371. Basically this is what happens:As you can see the url is rewritten and this makes sense when css is included using a link tag on a page but it causes a lot of issues when using inline styling which I am using to inline critical css. In my cases the font-face url is rewritten just like in the Github issue mentioned above. I've found Adobe docs mentioning this process: https://experienceleague.adobe.com/docs/experience-manager-64/developing/introduction/clientlibs.html?lang=nl&mt=false but I did not find any way to prevent this from happening, am I missing something? All help would be appreciated! 

Hi all! This is related to a previous question that I've asked, but I think I narrowed things down quite a bit. I have a script (Fragment) that runs on submission that scans the form and makes all hidden-required fields optional, that way the form will submit as long as all of the visible required fields are filled. This script worked really well on PDF forms, but I'm transitioning to .xdp (HTML5 rendered) forms.  I'm having 1 key issue. Whenever I try to change a hidden field to optional, the script crashes. My initial fix was to, in the script code, make the field visible, make it optional, then make it hidden. This briefly worked but now is broken for some unknown reason. It makes the user push submit twice before submitting, obviously not great from a user experience standpoint. Is there a known way to make a hidden field optional in a script? This seems like something that lots of people would want to do, but I can't find anything about it which leads me to wor

Last week, I attended my seventeenth Adobe Summit! Like last year, it was all online, but that didn’t stop Adobe from sharing a ton of information about their products. While, as usual, the amount of content was overwhelming, the online format allowed attendees to see sessions on-demand right away instead of past “live” summits where you would have to wait a while to view session recordings. So I did my best to watch as many analytics-related sessions as possible before my eyes and brain hurt! Below are some of my initial reactions to what I saw at Summit.   Adobe Analytics = Customer Journey Analytics If you work with the Adobe Analytics product, you had likely heard of Customer Journey Analytics before Adobe Summit. Customer Journey Analytics (or CJA) is the next evolution of Adobe Analytics. While I think the name “Customer Journey Analytics” vastly undersells what CJA delivers (I would prefer the name Omnichannel Analytics), it became abundantly clear t

If anybody is still missing, last few more hours to RSVP - Hurry Up!  https://aem-augs.adobe.com/events/details/adobe-experience-manager-aem-developer-user-group-presents-osgi-overview-osgi-bundles/

<image_policy jcr:primaryType="nt:unstructured" sling:resourceType="wcm/core/components/policy/policy" jcr:title="Image" allowUpload="false" allowedRenditionWidths="[960,720,590]" small="300x200" cq:styleDefaultClasses="l-content-width"> <jcr:content jcr:primaryType="nt:unstructured"/> <cq:styleGroups jcr:primaryType="nt:unstructured"> <item0 jcr:primaryType="nt:unstructured"> <cq:styles jcr:primaryType="nt:unstructured"> <item0 cq:styleClasses="l-content-width l-content-width--narrow" cq:styleId="1603361754179" cq:styleLabel="Small" jcr:primaryType="nt:unstructured"/> </cq:styles> </item0> </cq:styleGroups></image_policy>HiI am trying to understand how will this policy apply the classes. This policy is used for the image compone

AEM as a Cloud Service Tutorials - Cloud 5 by Adobe Abstract Introduction Welcome to the Cloud 5 Series from AEM Engineering. One of the primary problems in the implementation phase of any product is having enough code samples and/or live demonstrations of those samples, tool, or APIs. The goal of this series is to deliver useful information about AEM as a Cloud Service in 5 minutes or less. Visit the Suggestion Box for submitting topic ideas. Season 1 Each season varies in length and will be released on a fixed schedule. Season 1’s topics are primarily driven from past requests that we have come across in our day-to-day engagements with customers and partners. Visit this page for weekly updates or follow us on the social network of your choosing. Read Full Blog AEM as a Cloud Service Tutorials - Cloud 5 Q&A Please use this thread to ask the related questions.

Dispatcher #2 | What is AEM Dispatcher. by AEM GEEKS Abstract Video: https://youtu.be/7llomGMmzdE This tutorial explains about aem dispatcher. What is dispatcher. What is the purpose and role of dispatcher. How aem communicate with apache web server using dispatcher. Dispatcher is web server module which is used to instruct web server to perform aem related task. Read Full Blog Dispatcher #2 | What is AEM Dispatcher. Q&A Please use this thread to ask the related questions.