Product Communities

NEW WebAPI (REST) integration now available for Microsoft Dynamics 365 CRM   NOTE: The WebAPI (Rest) integration is currently ONLY available for Dynamics online & on-prem versions 9.x using ADFS 2016 and above.   Authentication The WebAPI (Rest) integration is only supported with Microsoft Dynamics 365 Online and on-prem instances v9.x in conjunction with ADFS 2016 and above. If you do not use these supported Dynamics/ADFS configurations, the native SOAP integration will continue to work for the foreseeable future; however, we are no longer developing SOAP enhancements.   Please note that the WebAPI (Rest) integration requires a client ID and Client secret for authentication.  Pre-ADFS 2016 (on-prem v8.x and older, with ADFS versions earlier than 2016) authentication requires login and password credentials only – the use of a client ID/Client secret is not needed or supported.   Connector As part of the continued investment in Adobe and Micro

AEM Experience Fragments: URL Externalization with Adobe Target by Exadel Abstract The Basics Using the “Export to Target” feature you can create an XF, add components to it, and then export it as an Adobe Target Offer. This feature can be enabled on an author instance of AEM. Since Experience Fragments are exported from the AEM author instance, you need to make sure that any references within the XF are externalized for web delivery. This requires a valid Adobe Target Configuration and configurations for the link externalizer. The Link Externalizer is used to determine the URLs for the HTML version of the Target Offer. Adobe Target requires all links inside the Target HTML Offer to be publicly accessed, so you need to publish the XF itself and all its links before pushing to Target. When a Target HTML Offer is being constructed, a request is sent to a custom Sling selector in AEM. This selector is called .atoffer.nocloudconfigs.html. After you generate the HTML page, the Sling Rewri

Cost Efficiency in Adobe Experience Platform Pipeline’s Public Cloud Spend: An Iterative Optimization Framework by Photoshop and Adobe Experience Manager: Accelerating creativity through APIs Abstract This is a follow-up to our previous blog about public cloud cost management for Adobe Experience Platform Pipeline. The previous blog covered an overview of Adobe Experience Platform Pipeline, a breakdown of expenses, a plan of action, and the need for a cost governance program. We recognize that both technology vendors and our enterprise customers (CIOs and IT organizations) have been faced with public cloud cost management. Building upon that, we focused on defining a cost optimization framework that establishes an iterable approach with sustainable long-term impact. In this blog, we will share our progress on how we reduced annual public cloud COGS spend by 40% without incurring any downtime. Goals We began by defining the following goals which would serve as our guiding principles

Hi,We have developed a new component, and we are trying to export it to server. Until now we have used AEM sync(VS code extension) to sync to AEM Server. But, when trying to sync core folder it does not work, because it does not have a jcr:root folder. How should we sync the core folder to server? We would really appreciate your help on this!

AEM as a Cloud Service Code Refactoring Tool: Repository Modernizer by Manas Kumar Maji Abstract Adobe Experience Manager (AEM) is now available as a Cloud Service, the cloud-native way of leveraging the AEM applications. For existing users, the transition journey to AEM as a Cloud Service involves three phases — Planning, Execution, and Post Go-live. We at Adobe, are constantly trying to make the transition journey faster and easier for users. One such initiative is developing code refactoring tools to make existing content (code, package structure, indexes, configurations) compatible to AEM as a Cloud Service. This article outlines the Repository Modernizer tool which changes existing AEM Maven projects to be AEM as a Cloud Service compatible by ensuring that they respect the split of mutable and immutable content, dependencies are established to create non-conflicting, deterministic deployments and that they are packaged in a deployable structure. Read Full Blog AEM as a Cloud Ser

AEM Fiddle a ACS AEM Tool for Debugging and to play around the CMS APIs by Aemsimplifiedbynikhil Abstract This article is quite new and quite interesting as here we will see how we can use AEM Fiddle to Debug/Chekout/Play-around around our AEM CMS by just executing small pieces of code directly on CMS without creating an actual project from any archetype. There are many tools that you can use from ACS AEM Tools package. To know detailed information of the AEM Fiddle click here. To find the latest packages of ACM AEM tools you can directly go to ACS AEM Git. As mentioned above, I have downloaded my package and installed it on my AEM instance. To use AEM fiddle you can navigate to Tools > Operations > Configuration and open the AEM Fiddle from ACS Tools. Read Full Blog AEM Fiddle a ACS AEM Tool for Debugging and to play around the CMS APIs Q&A Please use this thread to ask the related questions.

Joey Smith Completes AEM Sites DevOps Certification by Peter Nash Abstract There’s always lots of good stuff happening at Hoodoo Digital. We are pleased to announce that Joey Smith has completed the Adobe Certified Expert exam for the Adobe Experience Manager Sites DevOps Engineer. This exam certifies that he “has proven knowledge and experience to help clients optimize the value of their Adobe solution.” Adobe provides an exam guide that outlines the things that an Architect should be proficient with in order to pass the exam. At a minimum, the candidate seeking to become certified as an Adobe Experience Manager Dev/Ops Engineer has: ->At least 2 years of experience installing, configuring, monitoring, operating, and troubleshooting AEM (V6.3 and higher) ->Configure Continuous Integration/Continuous Deployment tasks Read Full Blog Joey Smith Completes AEM Sites DevOps Certification Q&A Please use this thread to ask the related questions.

AEM's Editable Templates: Common ground for authors and developers by Amplexor Abstract Editable Templates give content authors more independence from developers – If you make the best use of all features. Here's what you need to know. The creation of templates within Adobe Experience Manager (AEM) can sometimes be a tedious and time-consuming task for developers. But it doesn't have to be: Meet Editable Templates. The feature of Editable Templates was introduced already with the release version AEM 6.2, making it a breeze to create new and adjust existing Editable Templates on the fly. Since then, the concept has opened up the world of template creation for content authors, making it not solely a developer's task anymore. Editable Templates have a lot of potential and can create notable value to the content management process. However, there are a few things to consider when taking the plunge towards the feature. Before we dive in, let's get you acquainted with a few basic functio

Must-have dashboards for you and your team! It’s not uncommon for organizations to have more than one dashboard, each serving a different audience and purpose ‚Äî in fact, we encourage you to have multiple! Learn what reports and dashboards we recommend for System Administrators, Executives, Project Managers, Workers and Requester/Reviewers. Have questions about dashboards? Reply to this post and we'll be happy to help!

Hello everyone, I have a question about ACS Tracking.On every click that i'm doing on my emails, I have a deliveryName parameter added in my final URL : https://myWebsite/?deliveryName=DM5646 Rhere is my HTML link: https://myWebsiteOn my email, this is the link transformed (by the tracking formula) : http://myTrackingInstance/r/?id=h3ba1ff,e97ce0,e97ce2 That's ok because I have a classic formula NmsTracking_ClickFormula ! The thing that I don't understand, it is why I have this deliveryName parameter which I never called on my tracking process ? If my formula were modified by myself, that could be ok, but it's not the case If you can help me to delete this parameter, that could be great Thanks a lot !Alex

    Email marketing delivers the highest ROI of all marketing channels, but achieving that return is dependent on so many factors. One factor is the most critical for Deliverability: Permission. Follow along as Marketo Engage experts, Carmi Jones and Dusty Garner as they deep dive into email opt-in strategies and their impact on email deliverability and response. During the webinar you'll learn: How and why to opt-in or re-permission an old list Effective organic capture strategies to build pipeline Opt-in best practices that drive conversion Looking for additional resources? Slides: The Power of Permission for Email Deliverability On-demand webinar: How to "KonMari" Your Marketo Instance for Peak Performance

I get a lot of questions about data types in Marketo. There's information about them in the documentation plus here in the developer documents. I've aggregated the data types in a Google Doc that puts it all in one convenient place, distinguishing between the Person and Custom Objects, and addressing things line min and max values which can be a bit vague elsewhere.   Please let me know if you find this useful!

Hello!First Post here, and I’m interested in your thoughts What POS API can I use to connect to retailers and not just restaurants?

Hi all! I'm a student who's trying to gather research about competitive ad tech solutions. Could you share for me how/ why you/your company started using Adobe Advertising Cloud? Or, if you weren't the decision maker, how would you describe your experience with it? Any information on your role/ responsibilities would be appreciated! 

Our Adobe Digital Experience Communities are the heartbeat that connect, engage and empower our users to create game-changing digital experiences leveraging Adobe solutions. To help us continue to elevate your experience and inspire others to do more in our Communities, we are renaming the Adobe MVP program to Adobe Community Advisors.    The Community Advisor program is designed to recognize our most engaged, passionate, and supportive Digital Experience Community members. Community Advisors will mentor, encourage, and facilitate Community participation, share their product expertise, knowledge, and reinforce the Communities as the primary peer-to-peer resource for Experience Cloud customers. User needs to achieve level 6 in the Experience League communities to apply.    Please complete the Community Advisor Interest Form using the link below:   Apply here      COMMUNITY ADVISOR PROGRA

AEM - Project Archetype by Adobe Docs Abstract The AEM Project Archetype is a Maven template that creates a minimal, best-practices-based Adobe Experience Manager (AEM) project as a starting point for your website. Resources Archetype Documentation (this document): Overview of the archetype architecture and its different modules. ->Using the Archetype: further details on using the archetype and the modules available ->ui.frontend: How to use the front end build module The following tutorials are based off this archetype: ->WKND Site: Learn how to start a fresh new website. -> WKND Single Page App: Learn how to build a React or Angular webapp that is fully authorable in AEM. Git Link: https://github.com/adobe/aem-project-archetype Read Full Blog AEM - Project Archetype Q&A Please use this thread to ask the related questions.

AEM - Using Client-Side Libraries by Adobe Docs Abstract Using Client-Side Libraries Modern websites rely heavily on client-side processing driven by complex JavaScript and CSS code. Organizing and optimizing the serving of this code can be a complicated issue. To help deal with this issue, AEM provides Client-side Library Folders, which allow you to store your client-side code in the repository, organize it into categories, and define when and how each category of code is to be served to the client. The client-side library system then takes care of producing the correct links in your final webpage to load the correct code. How Client-Side Libraries Work in AEM The standard way to include a client-side library (that is, a JS or CSS file) in the HTML of a page is simply to include a

How to programmatically access the AEM JCR by Adobe Docs Abstract You can programmatically modify nodes and properties located within the Adobe CQ repository, which is part of the Adobe Marketing Cloud. To access the CQ repository, you use the Java Content Repository (JCR) API. You can use the Java JCR API to perform create, replace, update, and delete (CRUD) operations on content located within the Adobe CQ repository. For more information about the Java JCR API, see https://jackrabbit.apache.org/jcr/jcr-api.html. Create a Repository instance Although there are different ways to connect to a repository and establish a connection, this development article uses a static method that belongs to the org.apache.jackrabbit.commons.JcrUtils class. The name of the method is getRepository. This method takes a string parameter that represents the URL of the Adobe CQ server. For example http://localhost:4503/crx/server. The getRepositorymethod returns a Repositoryinstance, as shown in the foll

Overview of AEM Assets Brand Portal by Adobe Docs Abstract As a marketer, you sometimes need to collaborate with channel partners and internal business users to quickly create, manage, and deliver relevant digital content to customers. Timely delivery of relevant content across the entire customer journey is critical to driving greater demand, conversion, engagement, and customer loyalty. However, it is a challenge to develop solutions that support efficient and secure sharing of approved brand logos, guidelines, campaign assets, or product shots with extended internal teams, partners, and resellers. Adobe Experience Manager (AEM) Assets Brand Portal focuses on the marketer’s need to effectively collaborate with the globally distributed Brand Portal users by providing asset distribution and asset contribution capabilities. Asset distribution allows you to easily acquire, control, and securely distribute approved creative assets to external parties and internal business users across

AEM - Core Components Versions by Adobe Docs Abstract The current release of the Core Components is 2.15.2 and is compatible with AEM as a Cloud Service and on-premise AEM installations. Release History and Compatibility The Core Components are designed to be flexible and compatible with all supported AEM versions. Because of this a release of the components can contain multiple versions of the same component. The following tables illustrate the compatibility of the releases of the Core Components along with which component versions are contained in which releases. Release History & Requirements The following table, the contents of which are available on GitHub with full release details, gives an overview of the releases of the Core Components and their compatibility with AEM releases and Java versions. Read Full Blog AEM - Core Components Versions Q&A Please use this thread to ask the related questions.

Develop Sling Model Exporters by Adobe Docs Abstract This technical walk through walks through setting up AEM for use with Sling Model Exporter, enhancing an existing Sling Model using the Exporter framework to rendition as JSON, and how to use Exporter options and Jackson annotations to further customize the output. Sling Model Exporter was introduced in Sling Models v1.3.0. This new feature allows new annotations to be added to Sling Models that define how the Model an can be exported as a different Java object, or more commonly, serialized into a different format such as JSON. Apache Sling provides a Jackson JSON exporter to cover the most common case of exporting Sling Models as JSON objects for consumption by programmatic web consumers such as other web services and JavaScript applications. Read Full Blog Develop Sling Model Exporters Q&A Please use this thread to ask the related questions.

AEM - Search assets in Adobe Experience Manager by Adobe Docs Abstract Adobe Experience Manager Assets provides robust asset discovery methods that help you achieve higher content velocity. Your teams can reduce time to market with seamless, intelligent search experience using out-of-the-box functionality and custom methods. Searching assets is central to the usage of a digital asset management system – be it for further use by creatives, for robust management of assets by the business users and marketers, or for administration by DAM administrators. Simple, advanced, and custom searches that you can perform via Assets user interface or other apps and surfaces help fulfill these use cases. Experience Manager Assets supports the following use cases and this article describes the usage, concepts, configurations, limitations, and troubleshooting for these use cases. Read Full Blog AEM - Search assets in Adobe Experience Manager Q&A Please use this thread to ask the related questions

AEM - Introduction to AEM Forms by Adobe Docs Abstract For information about latest features and enhancements in AEM Forms, see What’s new in AEM Forms. About AEM Forms Adobe Experience Manager (AEM) provides an easy-to-use solution to create, manage, publish, and update complex digital forms while integrating with back-end processes, business rules, and data. AEM Forms combine form authoring, management, and publishing along with correspondence management capabilities, document security, and integrated analytics to create engaging end-to-end experiences. Designed to work across web and mobile channels, AEM Forms can be efficiently integrated into your business processes, reducing paper processes and errors while improving efficiency. In large enterprises, forms are often created once and reused by copying to a content management system. Keeping a large database of forms up-to-date and making them discoverable can be a considerable challenge. AEM provides a customizable Forms Porta

AEM - What is AEM Screens? by Adobe Docs Abstract AEM (Adobe Experience Manager) Screens - a Digital Signage Solution that allows you to publish dynamic and interactive digital experiences and interactions involving different types of screens in conjunction with a comprehensive digital marketing platform. Get up and running with a simple digital signage experience, using Kickstart for AEM Screens. Overview AEM Screens is built on the solid foundation of AEM Sites and enables marketers and IT personnel to create and manage experiences on multiple digital screens that impact in-store/in-venue goals for building brand and driving demand. Integration of AEM Screens with Sites allows you to re-use already existing content and effectively deliver a coherent and consistent customer solution. This provides a streamlined workflow to create dedicated digital experiences that are highly cost-effective and usable. It further helps to influence brand perception and impact decisions leading to up

Getting started with Junit Code coverage in AEM using Mockito Framework by aemsimplifiedbynikhil Abstract Welcome back AEM folks! In this article we will look into the process by which we can write junit test cases for the code coverage for our Java code in AEM. As this is the first article which will just cover the basics, if required I can go ahead and publish more article on in-depth knowledge on Junit. So to cover the code using Junit test cases we will use Mockito framework. So, lets go ahead and add the below dependency to our POM.xml org.mockito mockito-core 1.10.19 test Now once we are done adding the maven dependency, lets have a Java class for our article. So below is my Accordion Java Sling Model class. package com.company.models; import javax.inject.Inject; import org.apache.sling.api.resource.Resource; import org.apache.sling.models.annotations.DefaultInjectionStrategy; import org.apache.sling.models.annotations.Model; /** * @author Nikhil Kumar * */ @Model(adapta