Product Communities

Introduction to AEM Document Security Extension for Microsoft Office by Adobe Docs Abstract Adobe® Experience Manager Document Security Extension for Microsoft® Office ensures that only the people you authorize can use Word, Excel, and PowerPoint files that contain your intellectual property. By using Document Security Extension for Microsoft Office, you can apply predefined confidentiality settings to your files. Document Security Extension for Microsoft Office extends LiveCycle Rights Management and Document Security add-on for Adobe Experience Manager Forms to protect Word, Excel, and PowerPoint files and to allow authorized users who have this software installed to use policy-protected files according to the confidentiality settings established in the policy. How Document Security protects intellectual property Document Security ensures that only the people you authorize can use files that contain your intellectual property. Using Document Security, you can protect files by usin

 Are you free September 14th from 9:00AM PT – 12:00PM PT? Join us for Experience Makers The Skill Exchange – where Adobe Analytics experts will be giving you the inside scoop on the Adobe Analytics application. This is your chance to ask the experts questions and get tips and tricks that you can implement for enhanced productivity within the application. This free, 3-hour event has two content paths for you to choose from, based on your level of expertise with Adobe Analytics:  Learn: Are you newer to Adobe Analytics? Adobe Experts who will not only show you how to successfully use the application, but you will also have the opportunity  ask questions and get answers from Adobe Experts live.  Grow: Ready to experience the power of your peers? Adobe Experts and peers will share tips, tricks, and best practices to help you get the most out of Adobe Analytics. This is also yo

Hi Team, We have a use case in our project and need to move close to 100k assets to a different folder. We tried using AEM OOTB move functionality but it is extremely slow. I wanted to understand - ACS Commons Refactor is efficient than AEM OOTB operations of move, delete etc.?What are the other benefits/use cases of using ACS refactor.ACS Commons Refactor is not supported by AEM Assets as Cloud. Any other suggestion that we could have utilized here?Thanks,Manpreet

AEM: debugging Apache rewrite rules on dispatcher by Jeroen Druwà Abstract On my current project, we have many Apache rewrites rules configured. I recently discovered an issue in one of our rules that caused our product pages not to render correctly. It can be quite cumbersome to check every single rule, I went looking for a better solution and found one: mod_rewrite logging using the LogLevel directive. Within your directive LogLevel alert rewrite:trace3 mod_rewrite offers detailed logging of its actions at the trace1 to trace8 log levels. The log level can be set specifically for mod_rewrite using the LogLevel directive: Up to level debug, no actions are logged, while trace8 means that practically all actions are logged. Using a high trace log level for mod_rewrite will slow down your Apache HTTP Server dramatically! Use a log level higher than trace2 only for debugging! - http://httpd.apache.org/docs/current/mod/mod_rewrite.html#logging tail -f error_log | fgrep '[rewrite:' Can

Hello Experts    Need your suggestion on i18n keys management for microsites sharing same code base as main site. Currently we using hints to manage keys for microsite i.e "key: { "jcr:primaryType": "nt:folder", "jcr:mixinTypes": [ "sling:Message", "cq:ReplicationStatus" ], "sling:message": "MESSAGE", "sling:key": "key" }, "key0: { "jcr:primaryType": "nt:folder", "jcr:mixinTypes": [ "sling:Message", "cq:ReplicationStatus" ], "sling:message": "MESSAGE1", "sling:key": "key ((MICROSITE1))" }, "key1: { "jcr:primaryType": "nt:folder", "jcr:mixinTypes": [ "sling:Message", "cq:ReplicationStatus" ], "sling:message": "MESSAGE2", "sling:key": "key ((MICROSITE2))" }, This approach creates unnecessary keys even if microsites sharing same message as main site.Any other suggestions to manage this better? ThanksDipti Chauhan

OR Split in Workflow in AEM 6.5 by lhotsetechnologies Abstract The OR Split creates a split in the workflow, after which only one branch will be active. This step enables you to introduce conditional processing paths into your workflow. You add workflow steps to each branch as required. OR Split – Configuration Common Tab : In this tab, only one property will be display : Split Name – Give the name to your split. Branches Tab : In this tab, By default two branches will be display. We can also add more branches by clicking on Add Branch : We can add multiple branches here but only one branch will be execute among them. In every branch firstly we need to Select a Routing Expression like as : Rule Definition, External Script or ECMA Script. Read Full Blog OR Split in Workflow in AEM 6.5 Q&A Please use this thread to ask the related questions.

Dialog Participant Step in Workflow in AEM by lhotsetechnologies Abstract We use a Dialog Participant Step to collect information from the user who is assigned the work item. This step is useful for collecting small amounts of data (with the help of dialog) that is used later in the workflow. Dialog Participant Step – Configuration Common Tab : In this tab, the following properties will be display : Title – Give the title of the step. Description – Give the small description for the step Workflow Stage – Here we select the stage of workflow. When the workflow is run, the user can view the progress according to the Stage names (like – Start, Review, Approve, Complete). Note : Firstly we need to add the stages in workflow model properties. Timeout – It defines the period after which the step will “timed out” automatically. Timeout Handler – It defines what will happen when the workflow is timed out. (We need to select a script or process step here) User/Group Tab : In this tab, we

Asset Link – integrate your Creative Cloud apps with AEM Assets by Markus Bulla Abstract Adobe Asset Link is a feature to directly access assets stored in AEM from within your Creative Cloud (CC) applications, such as Photoshop, InDesign, Illustrator or XD. It consists of an extension that needs to be deployed to the CC app(s) and an endpoint on the AEM side. This article will outline the setup process and point out some pitfalls. Deploying the Asset Link Plugin I’m currently not aware of a way to deploy the Asset Link extension to an already existing CC installation. Instead, it needs to be included in a dedicated installation package for CC apps that can be created and retrieved through the Adobe Admin Console. To do this, your Adobe ID will need the according permissions in the Admin Console. Once you are logged in, select “Packages” from the main navigation and got to “Packages” where you will find a “Create a Package” button Read Full Blog Asset Link – integrate your Creative C

But it works in the Dependency Finder!? by Danklco Abstract Let's say I wanted to use the Microsoft Azure API's from my AEM application in Cloud Service. After checking the bundles in AEM, I notice the bundle org.apache.jackrabbit.oak-segment-azure exposes the API packages I need. Awesome! Oak Azure Segment Storage Bundle in the OSGi Console Just to double check (or maybe first) I can use the Package Dependencies OSGi console to see if the package is exported and get the dependency information. I see the dependency there as well: Package Dependencies showing the Azure Dependency But, when I try to use the API I get an error indicating OSGi can't resolve the Azure imports? What is going on!? Groovy Console Failing to Import Class Some History Most developers that have worked with CQ5 or AEM 6 are pretty familiar with an API surface that resembles the wild west. Since OSGi only cares if a package is exported from a bundle, it was possible to use features of AEM dependencies or c

New Adobe Tools Help Developers Manage Content and Power Digital Experiences by Josh van Tonder Abstract At Adobe, we understand that content is the life blood of customer experience. Now that our world is more connected than ever, it is important to be able to quickly create and reiterate customer experiences, and a big part of that is making sure customers receive the right content across the entire customer journey. App-like and immersive experiences are now a must, and at the center of this effort are developers. However, developers are struggling to deliver cohesive content across every touch point (modern web, smart watches, native apps, etc.). That is because until now, content has been siloed and difficult for developers to easily access to create new app-like experiences that meet consumer expectations. Today, at Adobe Developers Live — Adobe’s virtual conference dedicated to bringing together digital experience developers — we announced new Adobe Experience Cloud capabilit

Kafka quick introduction and AEM Integration by Juan Aranda Abstract Introduction Apache Kafka is an open-source distributed event streaming platform used by many companies around the world, allowing us high-performance data pipelines, streaming analytics, data integration for mission-critical applications. Companies use to start using a simple integration point-to-point, something like this: After a while, the requirements change, and then the companies need integrations with more sources and more targets complicating in the future. The above architecture has the following problems: 1. If you have 4 source system and 6 target systems, you need to write 24 integrations 2. Each integration comes with difficulties around protocols (TCP, HTTP, REST, FTP, JDBC, etc), data format (Binary, CSV, JSON, etc), data schemas how the data is shaped and may change. Read Full Blog Kafka quick introduction and AEM Integration Q&A Please use this thread to ask the related questions.

Hello All, This is another attempt from me to get an insight into AEM 65 communities components (hbs components like comments and groups) performance. We have about 300+ community groups. We use comments on post pages with pagination (10) and as the comments on the post page/s increase the load times of the page/s increase. Same with groups, the group landing page load time increases with increase in community groups. Was able to see the same behavior in we-retail ootb vanilla instance as well (in local). This is not noticed in current AEM 6.2 (live) I wanted to check with fellow community members if something similar or opposite was faced from someone. Please comment below if you are using AEM communities on AEM 65 and any thoughts. Trying to get a basic idea to do better in these terms.

Ask the Perficient Experts at Adobe Experience Makers Live by Perficient Abstract Perficient is a proud sponsor of Adobe Experience Makers Live. We would like to invite you and your team to join us at the virtual event held on August 31 and September 1 from 11:00 am – 2:00 pm CT each day. The event will feature 20 target sessions and thought-provoking keynotes. Along with that, Perficient will be hosting an Ask the Experts session on September 1 at 12 pm CT. Our experts will answer all your burning questions for the manufacturing industry. Panel of experts includes: Robert Sumner – He is a tenured Adobe Digital Marketing and Experience Maker with over 20 years of experience. In that time, he helped Fortune 500 companies improve customer satisfaction, drive organizational efficiencies, and increase revenue using proven digital marketing/ecommerce strategies. Robert specializes in manufacturing and automotive industries. Karie Daudt – She is a B2B Commerce Strategy Director at Perfici

AEM Spa editor - Error Page handling by Aemfrontend Abstract One of the questions we frequently got from customers was on how to handle 404 / 500 pages in the SPA editor. Unfortunately we could not give a good answer, and it required a lot of hacking to make it work. Thats why just now, we updated the spa page model manager to support handling 404 / 500 pages! It works like this: Page Request is made and ACS AEM error handler catches it. Client tries to fetch a model JSON but get's a 404 error in return. Client now will take the error page root (given as meta property) and use the status code to make a new request. Presuming the page exists, the authored error page model JSON is injected as requested path. The error page is displayed. Check out the repository providing a demo: https://github.com/niekraaijmakers/aem-spa-editor-errorpages-example Read Full Blog AEM Spa editor - Error Page handling Q&A Please use this thread to ask the related questions.

How To Reuse Editable Template With Multiple Sites — Adobe Experience Manager(AEM)? by Albinsblog Abstract Editable templates have been introduced in AEM 6.2, which allows the authors to create and edit templates. Template authors can create and configure templates from the Templates console in the AEM without the help of the development team. Template authors can define the policies, structure, and initial content for the templates that will be shared by all the pages created based on this template. Editable Templates allow the template-authors to configure the client libraries required to style the websites created based on this template — base/common client libraries are included through page rendering component but site-specific client libraries through template policy configuration. Read Full Blog How To Reuse Editable Template With Multiple Sites — Adobe Experience Manager(AEM)? Q&A Please use this thread to ask the related questions.

AEM Content Services: Using Sling and Node APIs to Provide Asset collections – Part 2 by Perficient Abstract In part 1 of this series, I discussed a method for getting AEM Asset Collection items into the JSON representation of a page. This uses the Sling model + HTL component pattern to obtain the collection items and display their values in the JSON, based on asset type. Specifically, the Sling model enables the JSON renderer to display markup in content fragments and SVGs, and the AEM path to binary formatted assets. With this method, third party apps and services can consume the JSON, using AEM in a headless manner. With this approach, authors can update the collections, while the content consumers see those collection updates in their JSON feed. This is a powerful solution already, but we can add some automation in updating the JSON and making it available on the customer/consumer facing dispatcher domain. Let’s start with automating the JSON updates. When an author adds or re

Adobe once again named a leader in the 2021 Gartner Magic Quadrant for Personalization Engines by Adobe Blogs Abstract It is an honor for Adobe to be recognized as a Leader in the Gartner Magic Quadrant for Personalization Engines for the fourth consecutive year. At Adobe, we believe that this report is an indication of the critical role a personalization program plays in a brand’s relationship with new visitors and loyal customers across the entire customer journey, beginning at first touch and extending into customer service and support. As consumers grapple with new digital experiences while looking for better and safer ways to engage in stores, branches and resorts, personalization can set a brand apart from the competition when it comes to creating exceptional relevant experiences and achieving customer loyalty. Recognized as a leader in the Gartner Magic Quadrant for Personalization Engines is a testament to the success our customers and partners have achieved using Adobe Targe

Duy Nguyen and Alex Thiers will share how AEM Assets customers can leverage content automation features to create with magic (photoshop API) by Eventbrite Abstract About this event This week we share how customers of AEM can bring the magic of Photoshop to AEM Assets with Project Firefly. Duy Nguyen will give a demo of this new capability and then dive into how you can build this with Project Firefly. For AEM Assets customers and partners this adds a flexible new way to programmatically create asset renditions. Read Full Blog Duy Nguyen and Alex Thiers will share how AEM Assets customers can leverage content automation features to create with magic (photoshop API) Q&A Please use this thread to ask the related questions.

Multi-Lingual Personalization at Scale with Experience Fragments (AEM and Target) by Praveen Penupati Abstract AEM integrated with Adobe Target makes life easier for content creators and marketers. They both work in the tool of their choice and the integration allows them to focus on what they do best independently. Managing personalization for a multi-lingual brand is, however, still a big challenge. Wouldn’t it be dreamy if there was a trick to centralize multi-lingual personalization? How AEM and Target work together By Integrating Adobe Experience Manager with Adobe Target, one can harvest the power of AEM capabilities of cross channel’s content delivery, multi-language site capability and responsive behaviour, with the intelligence of Adobe Target which can be used to serve relevant content to the relevant customer. AEM and Adobe Target combined to facilitate the right customer with the right content in right language. Read Full Blog Multi-Lingual Personalization at Scale with E

We raised a ticket with adobe enterprise support more than 2 months ago - but no answer yet. We have several AEM Cloud environments, including the "stage" and "production" envs (and several separate dev and test ones). We control access via the cloud admin console (https://adminconsole.adobe.com/). In the cloud manger, we assign product profiles to users (not via groups as this has bugs - another outstanding multi-month ticket with adobe support).  We use adobe logins (not AD). See screen shots We setup the groups and assigned the product profiles as instructed here: https://helpx.adobe.com/enterprise/using/user-groups.html  When we assign the two product profiles, which look like "AEM Adminstrators-xxx" and "AEM Users-xxx" we can then login to the author instances as expected. But, on some envs we can create/edit pages, and some we cant. In addition, some users can, and some users cant, even though they have exactly the same setup in Admin Contr

Hi Team,We are working in assets as cloud project and are noticing multiple errors in logs related to collections.The number of such errors is quite significant and we suspect if it might not be related to any manual action.*ERROR* [27.6.223.5 [1627984198406] GET /mnt/overlay/dam/gui/content/commons/createlightbox.html HTTP/1.1] com.day.cq.wcm.tags.IncludeTag Error while executing script ../lightboxassetcount/lightboxassetcount.jspjavax.servlet.ServletException: Failed executing script /libs/dam/gui/coral/components/admin/collections/lightboxassetcount/lightboxassetcount.jsp: nullat org.apache.sling.servlets.resolver.internal.bundle.BundledScriptServlet.service(BundledScriptServlet.java:82) [org.apache.sling.servlets.resolver:2.7.14]at com.day.cq.wcm.tags.IncludeTag.includeScript(IncludeTag.java:178) [com.day.cq.wcm.cq-wcm-taglib:5.13.6]at com.day.cq.wcm.tags.IncludeTag.doEndTag(IncludeTag.java:95) [com.day.cq.wcm.cq-wcm-taglib:5.13.6]at libs.dam.gui.coral.components.admin.collections.

Hi Team, Getting below error in AEM Author logs. Any idea on same. Kindly suggest 18.08.2021 09:09:04.573 *ERROR* [10.43.1.72 [1629241744569] GET /editor.html/content/test/en/home/tl/resorts/destinations/abc/%5bobject%20Object%5d HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingExceptionjava.lang.IllegalArgumentException: Not a valid identifier 'object Object'at com.google.common.base.Preconditions.checkArgument(Preconditions.java:93)at org.apache.jackrabbit.oak.plugins.identifier.IdentifierManager.getTree(IdentifierManager.java:134)at org.apache.jackrabbit.oak.plugins.identifier.IdentifierManager.getPath(IdentifierManager.java:156)at org.apache.jackrabbit.oak.namepath.impl.NamePathMapperImpl.getOakPath(NamePathMapperImpl.java:100)at org.apache.jackrabbit.oak.jcr.session.SessionContext.getOakPath(SessionContext.java:361)at org.apache.jackrabbit.oak.jcr.session.SessionContext.getOakPathOrThrow(SessionContext.java:380)at org.apache.jackrab

Sir, I have a table of 2 columns and a repeating row (Row2)  of which Cell1 is a Dropdown field  and Cell2 is a Text Field   I have another subform which is also repeatable which as Textfield.  Now i want that whenever user selects the Dropdown the same value should be set to the Textfield (in the Subform).  if user adds 5 rows in the table and select value a, b,c,d,e in the dropdowns then the 5 textfield in the  subform should also be set to a,b,c,d,e  attached is the actual AEM form    ... in this form i want "Raised By"    field to be always equal  to the dropdown field "Team. Member"   https://www.dropbox.com/s/ywd7rdh00ywn4u1/Setting%20field%20value%20of%20repeatable%20form%20to%20other%20repeatable%20field.pdf?dl=0 Thanks

Hello Community - I see some issues with the clientLib minification in the JS. This is happening only for few of the clientLibs and for other clientLibs in the same project is working fine without any issues.After enabling the debug logs, I found that there are some issues with minification for the spcecific clientlib failed with the error "with processor gcc for mode min rejected". Even though it failed with some errors for the minification, I am able to minify the JS using online utility(https://closure-compiler.appspot.com/home, https://javascript-minifier.com/) without any errors. Error:com.adobe.granite.ui.clientlibs.processor.gcc.impl.GCCScriptProcessor Processed /etc/designs/testapps/testClientlibs.js. 5 error(s), 0 warning(s)13.08.2021 13:55:19.616 *DEBUG* [10.129.38.226 [1628880917365] GET /etc/designs/testapps/testClientlibs.min.js HTTP/1.1] com.adobe.granite.ui.clientlibs.impl.HtmlLibraryBuilderImpl processing /etc/designs/testClientlibs/testClientlibs with processor gc

AEM Cloud Service - Extend React SPA Sling Model for Page Style System support by Sreekanth Choudry Nalabotu Abstract Goal AEM Cloud Version : 2021.5.5257.20210505T101930Z-210429 (May 05, 2021) Extend the JSON model eg. /content/eaem-cs-spa-style-system/us/en.model.json for supporting Page Style System in a React SPA. The following extension adds page level css classes configured via Style System in the model's children cssClassNames property eg.spa page basicpage eaempage--background-aero and necessary logic on the react side to apply it... Solution 1) Create the project using following maven archetype command mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=24 -D aemVersion=cloud -D appTitle="Experience AEM SPA Style System" -D appId="eaem-cs-spa-style-system" -D groupId="apps.experienceaem.sites.spa" -D frontendModule=react -D includeExamples=n -D includeDispatcherConfig=n 2) Create the CSS file for P