Product Communities

Adobe Experience Manager Assets Brand Portal Guide by Adobe Docs Abstract Adobe Experience Manager Assets Brand Portal aids organizations to meet their marketing needs by securely distributing approved brand and product assets to external agencies, partners, internal teams, and resellers for download. The lack of a secure asset sharing solution can result in: Manual asset sharing through email or cloud Brand compliance issues Lack of control over asset usage Delays in campaigns and product launches Duplication of content across geographic locations and organizations Unsecured storage of assets before release With Brand Portal, organizations can ensure brand compliance by enabling marketers to collaborate with channel partners and internal business users to quickly create, manage, and deliver the latest design guidelines, logos, campaign and product assets to the stakeholders. Brand Portal is a cloud-based SAAS offering. It is available as an add-on to Adobe Experience Manager Assets

Configure AEM Assets with Brand Portal by Adobe Docs Abstract Configuring Adobe Experience Manager Assets with Brand Portal enables asset publishing, asset distribution, and asset contribution features for the Brand Portal users. It allows the AEM Assets users to publish and distribute assets with the Brand Portal users. The Brand Portal users can access the shared assets and contribute by uploading new assets to the asset contribution folders and publishing them back to AEM Assets. Configuring AEM Assets with Brand Portal is supported on: AEM Assets as a Cloud Service AEM Assets (on premise and managed service) 6.3 and above AEM Assets as a Cloud Service is automatically configured with Brand Portal by activating Brand Portal from the Cloud Manager. The activation workflow creates the required configurations at the backend and activates Brand Portal on the same IMS org as of the AEM Assets as a Cloud Service instance. Whereas, AEM Assets (on premise and managed service) is manuall

Share folders on Brand Portal by Adobe Docs Abstract Assets need to be published to Brand Portal from a pre-configured AEM Author instance, as Brand Portal does not support asset ingestion. Folder sharing workflow in Brand Portal The following describes the folder share workflow and user access: By default, all the folders published from AEM Assets to Brand Portal are visible only to the Brand Portal Administrator, unless marked as public while configuring replication. The Administrator uses the Folder Properties console to share a folder with selective users or groups. Only those users or groups with whom the folder is shared can see the folder after they log in to Brand Portal. The folder is not visible to other users. The Administrator can also choose to make a folder public through the Public Folder check box in the Folder Properties console. A public folder is visible to all the users. Irrespective of user roles and privileges, when users log in to Brand Portal, they see all

AEM - Content Insight by Adobe Docs Abstract Content Insight provides information about page performance using web analytics and SEO recommendations. Use Content Insight to make decisions about how to modify pages, or to learn how previous changes have changed performance. For every page that you author, you can open Content Insight to analyse the page. The layout of the Content Insight page changes to suit the screen dimensions and orientation of the device that you are using. Report Data The Content Insight page includes reports that use Adobe SiteCatalyst, Adobe Target, Adobe Social, and BrightEdge data: SiteCatalyst: Reports for the following metrics are available: Page views Average time spent on page Sources Target: Reports on campaign activity for which your page includes offers. BrightEdge: Reports on the page features that improve the visibility of the page to search engines, and recommends features that should be implemented. Read Full Blog AEM - Content Insight Q&

AEM - Analyzing Page Performance by Adobe Docs Abstract Open the Content Insight page to analyze the performance of the page that you are authoring. Configure the reporting period to focus your analysis. Opening Analytics and Recommendations for a Page Use the following procedure to see the Analytics and Recommendations for a page: Navigate to the page that you want to analyze. In the toolbar, click or tap Analytics and Recommendations. NOTE Analytics and Recommendations for a page only appear if you have configured AEM to integrate with Adobe Analytics. Changing the Reporting Period Change the following time-related aspects of the analytics reports: The period of time on which to report. The granularity of the data. The tools for changing the time-related aspects of the reports appear at the top of the Content Insight page. chlimage_1-126 Changing the Reporting Period Change the reporting period of the Content Insight page to focus your analysis of page activity to a specific

AEM - Forms Automated Conversion Guide by Adobe Docs Abstract Introduction Automated Forms Conversion service helps accelerate digitization and modernization of data capture experience through automated conversion of PDF forms to adaptive forms. The service, powered by Adobe Sensei, automatically converts your PDF forms to device-friendly, responsive, and HTML5-based adaptive forms. While leveraging the existing investments in PDF Forms and XFA, the service also applies appropriate validations, styling, and layout to adaptive form fields during conversion. The service helps: Save manual effort required to convert print forms to adaptive forms Applies patterns and appropriate validations during conversion Generate Document of Record during conversion Group commonly occurring fields into reusable form fragments Enables Adobe Analytics during conversion Onboarding The service is available for free to AEM 6.4 Forms and AEM 6.5 Forms On-Premise term customers and Adobe-Managed Service en

AEM - Development Best Practices by Adobe Docs Abstract Work according to a Definition of Done Each team has a different definition of what “done” means, but it is important to have one and ensure that a story meets the defined criteria before being accepted. Some criteria that are commonly specified by teams include: Code reviewed for formatting Comments/Javadoc added Meets required test coverage levels Passes unit and integration tests Validated in the QA environment Localization implemented Without a well-defined DoD, it is easy to end up in a situation where a lot of things are halfway done and nothing is truly complete. Define and adhere to coding and formatting conventions Things like indentation levels and white space may not seem important, but having properly formatted code goes a long way towards readability and maintainability. Conventions should be discussed and agreed to as a team and then followed in the code. Aim for high test coverage As a project implementation gr

AEM - Development Tools by Adobe Docs Abstract To develop your JCR, Apache Sling or AEM applications, the following tool sets are available: one set consisting of CRXDE Lite and WebDAV. CRXDE Lite is embedded into CRX/AEM and enables you to perform standard development tasks in the browser. With CRXDE Lite, you can create and edit files (like .jsp and .java), folders, templates, components, dialogs, nodes, properties and bundles while logging and integrating with SVN. CRXDE Lite is recommended when you do not have direct access to the CRX/AEM server, when you develop an application by extending or modifying the out-of-the-box components and Java bundles or when you do not need a dedicated debugger, code completion and syntax highlighting. one set consisting of an Integrated Development Environment (for example: Eclipse or IntelliJ), a build tool (for example: Apache Maven), FileVault which has been developed by Adobe to map a repository to a file system, a version control system (f

AEM Modernization Tools by Adobe Docs Abstract AEM Modernization Tools allow for the easy conversion of: Static templates to editable templates Design configurations to policies Foundation Components to Core Components Classic UI to Touch-Enabled UI For further information about the usage of these tools, see their documentation. NOTE AEM Modernize Tools are a community effort and are not supported or warrantied by Adobe. Read Full Blog AEM Modernization Tools Q&A Please use this thread to ask the related questions.

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