Product Communities

<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.

AEM Analyser Maven Plugin by Adobe Abstract A Maven plugin used by developers of applications for AEM as a Cloud Service (AEMaaCS). The plugin provides an easy way to run the same checks locally as in the Cloud Manager pipeline and ensures that the application works correctly when deployed in the cloud. NOTE: Please make sure to always use the latest version. Refrain from using any version below 1.1.10 Functionality The plugin performs similar tasks as the Cloud Manager pipeline after the application is built and before it is deployed. It inspects the generated content packages and runs a set of checks (analysers) on the contents of the packages. By default it check against the latest available SDK version. Most of the analysers are based on the Apache Sling Feature Model Analyser framework. Installation This is a plugin to Apache Maven. It can be enabled by referencing its coordinates in a pom.xml: com.adobe.aem aemanalyser-maven-plugin ... version ... Example: com.adobe.ae

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 check the node property type is single value or multi value in aem? by Rashid Jorvee Abstract How to check the node property type is single value or multi value in aem? We can check the type of property(whether single or multiple) using the method isMultiple() of Property interface. Below is an example to check the node property "items" is a single value or multiple values and based on that get the value or values for that property in AEM. Property property = node.getProperty("items"); Value[] values = null; if(property.isMultiple()){ values = property.getValues(); } else { values[0] = property.getValue(); } Hope this helps. Thank you! Read Full Blog How to check the node property type is single value or multi value in aem? Q&A Please use this thread to ask the related questions.

Hello, I am learning features available in the AEM forms. I am building a form that consist of multiple panels and I would like to show the submit button only if all required fields are valid. I can see that there is an API that allows to validate form using `guideBridge.validate()` which will return true/false but this also changes the form (invalid fields are marked as invalid). Is there a function that can check if form is valid without actually changing form fields? I wonder how I could dynamically show/hide submit button based on the status of the for.API: https://developer.adobe.com/experience-manager/reference-materials/6-5/forms/javascript-api/GuideBridge.html#validate__anchor

Environment: Mac OS (AEM 6.5 + Adaptive Forms)Test Scenario:1. Install AEM 6.5 (AEM_6.5_Quickstart.jar)2. Install Adaptive Forms (AEM-FORMS-6.5-OSX-6.0.80.zip)3. Got first error consistently with every start of aem service4. Got second error consistently with every stop of aem service08.06.2019 20:49:39.201 *ERROR* [FelixDispatchQueue] adobe-aemfd-signatures FrameworkEvent ERROR (org.osgi.framework.BundleException: Activator start error in bundle adobe-aemfd-signatures [673].)org.osgi.framework.BundleException: Activator start error in bundle adobe-aemfd-signatures [673].    at org.apache.felix.framework.Felix.activateBundle(Felix.java:2452)    at org.apache.felix.framework.Felix.startBundle(Felix.java:2308)    at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1539)    at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)    at java.lang.Thread.run(Thread.java:748)Caused by: java.lang.NoClassDefFoundError: com/rsa/asn1/ASN_Exceptio

Hello all,    CRM Integration is a vital cog in the Martech setup to ensure single source of truth for your contacts and supercharging collaboration between marketing and sales towards winning and keeping the customer.  Towards assisting our healthcare customers in this endeavor, we have now declared the availability of Marketo's native integration with Veeva CRM.    Here is a presentation that introduces the integration, features and suggests on how to enroll .  Please feel free to reach out to me at prasannb@adobe.com regarding any queries and requests.   I will keep posting interesting implementation details, video tutorials and tips/tricks over the next few weeks. Looking forward to hearing back from you with questions and suggestions in this regard.    Regards, Prasanna Belkale    

Are you frustrated and exhausted living the 'Lone System Admin Life’?In this on-demand webinar, originally broadcast on May 11, 2022, Cynthia Boon‚ former System Admin and current Workfront Customer Success Manager, and Kathy McLaughlin, Operations Specialist and Workfront Group Administrator at Mayo Clinic Alix School of Medicine, came together to discuss: How to determine when it’s time to add group administrationCommon roles and responsibilitiesBest practices for defining standard practices across groups, and more.PRO TIP: If you have Group Admins, we encourage you to share this webinar with them. And if you haven’t needed Group Administrators yet, watch yourself to learn about the things you will want to think about as you start introducing this role!You can view the recording here and a copy of the slides is attached. Have questions for our speakers? Tag them in a comment below.  

I am not able to access to the aem cloud service how to do that as I want to download the aem sdk folder from there??