Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
Hello CommunityHope everyone is doing well.I have tried integrating conductor 2.0 with Adobe Analytics. But I am unable to get conductor weekly report due to an error which states "the report failed to successfully transfer". I followed the integration guide and the only part I am confused about is some segment " Page Name to Page URL mapping" which is automatically created but I am unable to see this segment while integrating with data warehouse.Can anybody shed some light on this integration?Thanks & Regards
When attempting to upload and install a file created via ./mvnw clean install I'm running into the error below:Install Package: /etc/packages/apple-cms/cms-content-v1.zipMon Mar 19 2018 15:53:13 GMT-0400 (EDT)Installing contentCollecting import information...Installing node types...Installing privileges...Importing content...- /...saving approx 1 nodes...Package imported (with errors, check logs!)Content is missing from the crx/de tree under /etc/map/publish/http - so I wish to check the logs.Attempting to tail all of the logs under ../author/crx-quickstart/logs but not getting any output at all - same for both publish and authoring instance.
Getting started with an Adobe Marketo Engage implementation is no easy task. There are so many things to do inside and outside your instance. One of the keys to any successful implementation is documentation. Keeping track of tasks in progress along with knowing the key areas to get your instance up and running are not only pivotal now, but it will also set you up for long term success. As a new admin going through a fresh implementation, you can now use this checklist to help guide you through the implementation process! Special thank you to Adobe Marketo Engage Champions @brooke_bartos1, @byoung987, @alane-1, and @chloe_pott for their contributions to this checklist! This checklist was built off our Inherited Instance Checklist so another big thank you to contributors of that checklist: @Grace_Brebner3, @Jessica_Kao3, @Sydney_Gordon2, @Amanda_Thomas6, @Amy_Goldfine, @Ajay_Sarp
Hi Everyone, Adobe Campaign Classic Community is now Adobe Campaign Classic v7 & Campaign v8 Community! We have made a slight change to our Community by renaming it to Adobe Campaign Community from Adobe Campaign Classic Community. This has been done to welcome our new version of Adobe Campaign – Adobe Campaign V8. Now, we will be using the same community to host all your queries, discussions, and ideas for Adobe Campaign Classic as well as the new Adobe Campaign V8. What’s changed? The community name has changed from Adobe Campaign Classic Community to AAdobe Campaign Classic v7 & Campaign v8 Community to accommodate the users and their queries for all the Campaign Classic versions as well as the new Campaign V8, going forward. How will it impact us? This should not impact the way you are using your community. But it would be helpful if we maintain clarity while posting any content. Does this mean Adobe Campaign Classic has no community now? This is still the community
As a System or Group Admin, you likely know how important it is to start new Workfront users out on the right foot. In addition to onboarding, how do you train them on best practices, or when there are updates? Join us on Tuesday, June 8 at 8:00 a.m. Pacific (4:00 p.m. UK) for an interactive networking session on the topic of training end users. Registration here. Kicking things off will be @Rachelle Dilley‚ from the University of Arizona, who had the daunting task of implementing Workfront during the pandemic and had no choice but to create an entirely virtual training program. @Dave Parker‚ from Seed Company will also be joining us to share his guidance on the most important things he's learned over the years about training end users. You'll have a chance to ask questions, and we'll leave plenty of time for roundtable group discussion. This session is 90-minutes and is different from a traditional webinar. Be prepared to turn on your video, come off mute and join the co
Custom Oak Indexes : AEM Part-2 (Synonyms Words) by Bimmisoi Abstract As of now we have created custom Index. let's implement synonyms words for search. Please follow Custom Oak Indexes Part-1 for Custom Index Creation synonyms : In most of the search implementation search should work for synonym words. Example : If a user is searching for Mumbai or Bombay or BOM , results should be same. Or We can follow below steps to implement this. Create analyzers node : type - nt:unstructured Create default node : type - nt:unstructured Create filters node : type - nt:unstructured Create Synonym node : type - nt:unstructured Properties synonyms : synonyms.txt [String] Create synonyms.txt file : type - nt:file After reindex changes will start reflecting. Hope this helps!! Read Full Blog Custom Oak Indexes : AEM Part-2 (Synonyms Words) Q&A Please use this thread to ask the related questions.
Multi-Org Adobe Target and AEM Experience Fragment Integration and Governance Ideas by Rohankapooronline Abstract Adobe Experience Manager and Adobe Target integration is one of the most powerful and robust in the Adobe Experience Cloud. I wrote about some of the benefits of this integration back in 2019. In this post, I want to cover two topics within the context of these two solutions: Cross-IMS Org integration between AEM and Target General Target workspace governance and XF nomenclature ideas AEM & Target Cross-IMS Org Integration This is one topic I never got a clear answer to unless I tried and tested it myself. A well known fact about IMS orgs is that we cannot integrate solutions across which is absolutely true when it comes to the Adobe Experience Cloud Visitor ID among other solution but in this case, it is possible to integrate AEM with different Adobe Target instances via Adobe I/O. Having said this, I must also mention that it's not very common for us to see given m
The Adobe Experience Platform Debugger by pedromonjo Abstract The Adobe Experience Platform Debugger 06 Jun 2021 » Analytics Tips Every time I check the Adobe Analytics reports of this blog, the most visited post is How to debug an Adobe Analytics implementation. That post was written back in 2016 and, in technology, 5 years is an eternity. More importantly, one of my recommendations does not exist anymore. It is time to update that post and to talk about the successor of the Adobe Debugger: the Adobe Experience Platform (AEP) Debugger. Before I forget, I wanted to clarify that both Charles and the browser developer tools are still great options. In my day-to-day job, when I have to debug an implementation of any Adobe tool, I always start with the latter. In my other post, I explicitly mentioned Chrome, but (I believe) all browsers based on Webkit should also have the same set of tools. Next, if the browser is not enough, I use the AEP Debugger. Finally, when things get really comp
Initialyze obtains the Adobe Experience Manager (AEM) Run and Operate Specialization by Initialyze Abstract We feel honored to announce that Initialyze has obtained the Adobe Experience Manager Run and Operate Specialization! It is a prestigious accomplishment to qualify for the Adobe Experience Manager Run and Operate Specialization. To reach this level of competence, Adobe sets a high standard, and we’re delighted to be acknowledged as one of the highly skilled Adobe partners. The Adobe Solution Partners who collaborate with an AEM customer deployment after the project has reached the Run and Operate phase are awarded the Adobe Experience Manager Run and Operate Specialization. Often, as part of a managed services or outsourced arrangement, these partners will handle every aspect of the system’s operation for the customer. “Certification is not easy to obtain, but it is well worth the effort,” said CEO Mihir Mange. He added, “Within the Adobe Experience Cloud, we continue to build
Customer Activity Hub - A Blueprint for Building Extraordinary Customer Experiences with Adobe… by Kevin Cobourn, Wendy Braun, and Jody Arthur Abstract In this post, Adobe Experience Platform introduces the fourth in its series of Digital Experience Blueprints — a whole new way to learn and understand how you can use its technology to build incredible customer experiences in real-time. The challenge in creating incredible customer experiences isn’t a lack of data. Architecting an amazing experience should be easy with all the customer data enterprises collect today. Yet doing so remains an elusive goal for many not because they don’t have the data they need, but because they cannot get that data into the right place at the right time and in a way that allows them to fully leverage it. Every day, customers interact with a brand, whether on the web, a mobile app, or in a physical store. A company is collecting these behavioral and personal data from these channels then storing it in
AEM Cloud Service | Set up Adobe I/O CLI for log tailing by aem6solutions Abstract AEM Cloud Service | Set up Adobe I/O CLI for log tailing Perquisites- Node.js >=10.22.0 must be installed in system. Check this by executing below command: node --version Upgrade to higher node version if needed, using below command: nvm install 12.18.3 Run following commands: npm install -g @adobe/aio-cli aio plugins:install @adobe/aio-cli-plugin-cloudmanager aio plugins:install @adobe/aio-cli-plugin-asset-compute Set up the Adobe I/O CLI authentication Log in to console.adobe.io Ensure your Organization that includes the Cloud Manager product to connect to is active in the Adobe Org switcher Create a new or open an existing Adobe I/O program Adobe I/O Console programs are simply organizational groupings of integrations, create or use and existing program based on how you want to manage your integrations If creating a new project, select “Empty Project” if prompted (vs. “Create from Template”)
Case Study: Retailer Launches Improved Insight POC with Adobe Experience Platform by Sunish Verma and Nick Hecht. Abstract This blog details a single implementation or customization on Adobe Experience Platform. Not all aspects are guaranteed as general availability. If you need professional guidance on how to proceed, then please reach out to Adobe Consulting Services on this topic. We have been experiencing global new trends in customer experience since early 2020. Retailers, in particular, have had to adapt to new safety and security public health requirements while committed to delivering exceptional customer experience. For example, real-time offers from anywhere are imperative to offer the customers the best value as well as delightful interactions. Web, mobile, and curbside shopping must be seamless. For CIOs and CMOs, actionable reporting and real-time data science insights have become mission-critical to deliver these new and improved customer experiences in these extraord
AEM micro-optimizations (part 3) by Jörg Hoh Abstract Welcome to my third post on AEM micro-optimizations. Again with some interesting ways how you can improve your AEM application performance, somethings with little improvements, but sometimes with significant ones. During some recent performance optimization I came across code, which felt a bit odd. Technically it was quite easy: for (Item item : manyItems) { proprocessSingleItem (resolver, item); } void processSingleItem (ResourceResolver resolver, Item i} { // do something with the resourceResolver resolver.commit(); } That is indeed a very common pattern, especially in software, which evolved over time: You have code, which deals with a single item. And later, if you need to do it for multiple items, you execute this code in a loop. Works perfectly, and the pattern is widely used. And it can be problematic. If you have an operation in that performSingleItem() method, which comes with a method creating some overhead . Maybe yo
AEM Cloud Service - Assets Metadata Editor Multifield Limit Validation by Sreekanth Choudry Nalabotu Abstract Goal Add a Client Side Validator for limiting the number of items in a Multifield in Assets Metadata Editor Min/max limit configuration is hardcoded in the extension. For making it configurable via schema model check this post Solution Create a client library /apps/eaem-cs-meta-limit-mf/clientlibs/clientlib-limit-mf with categories=dam.gui.coral.metadataeditor and dependencies= eaem.lodash. Add the following js logic for validator in /apps/eaem-cs-meta-limit-mf/clientlibs/clientlib-limit-mf/meta-limit-mf.js (function($, $document){ var DATA_MF_NAME = "data-granite-coral-multifield-name", MF_NAME = "./jcr:content/metadata/eaemKeywords", EAEM_VALIDATION_ERROR = "eaem-assets-validation-error", EAEM_MAX_ITEMS = 5, EAEM_MIN_ITEMS = 1, continueSave = true; $document.on("foundation-contentloaded", validateMF); function validateMF(){ var $multifield = $("[" + DATA_MF_NAME + "='"
It’s well-established that SFDC’s URL field type isn’t up to the task of storing real-world URLs, since it maxes out at 255 characters.[1] What isn’t discussed much, if at all, is that those 255 characters aren’t limited to ASCII. Indeed, a URL field can contain an IRI, a.k.a. URL with Unicode characters that haven’t been percent-encoded. (And it might be smart to store IRIs: as I mentioned in the recent post on decoding URLs for attribution, IRIs are space-efficient.) It bears repeating that there’s a clear career advantage to knowing your way around text encoding. You don’t want to be the one — and I’ve been the one myself, to my lasting shame — saying “Oops, we’ll never know what those ???? or ���� or ÿÿÿÿ characters were in the original data.” When you pull data into your on-premises db, you need to know what you’re gonna get. Don’t make an A— out of U(nicode) and Me Earlier today I was auditing the column typ
I am a developer and I have a local instance I use for building and testing. My system is using the Java 11 JDK. After some number of builds, I haven't counted but the instance is fine for a bit then fails. The builds are successful and deploy fine. The issue I'm running into is that something happens where the pages I have created no longer render. In fact, neither do the WE Retail pages. The response to the request to the page is an empty document. The only way I have been able to fix it is by deleting the entire crx-quickstart tree then rebuilding the instance. This is time consuming and painful. I loose all of my configurations and changes that aren't backed up in a package, those that are, require me to then load the package after the instance has rebuilt. I have tried compacting the indexes and forcing them to rebuild but that doesn't work. Has anyone else had a similar issue and if you were able to fix it, how did you do so?
Hi Team, Hope you all are fine and safe. AEM version: 6.4.2 Issue: With the admin user, I am able to add components in parsys but with other users "+" sign does not appear. What would be missing here? Regards,AP
The Summit 2021 session recording URLs for the following Adobe Campaign sessions are now available on their respective session posts in the Adobe Campaign Community. Check out the ones you wish to revisit: Session Title Description Speakers Build an Omnichannel Ecosystem That Connects with Customers Empowered customer can engage with a brand whenever and however they want. To deliver valuable experiences, marketers must understand and even anticipate when and how a customer engages. Hear how Comcast uses Adobe Campaign to provide... Bruce Swann, Group Product Marketing Manager , Adobe | Natalie Cawley, Senior Manager, Campaign Management Systems, Comcast NBC Universal | Josh Mann, Head of Marketing Technology, Comcast Find the Value of Adobe Campaign with Managed Cloud Services Learn about upgrading your on-premises or hybrid deployment of Adobe Campaign to Managed Cloud Services. Discover how to: Lower the total cost of ownership by simplif
AEM - Create custom OSGi Configuration by Adobe Docs Abstract Introduction Create custom OSGi configuration to capture the credentials of your document cloud account To make a custom OSGi configuration, we need to first create an interface whose public methods will represent the fields in the configuration. Create an interface named DocumentCloudConfiguration and paste the following code in it. package com.aemforms.doccloud.core; import org.osgi.service.metatype.annotations.AttributeDefinition; import org.osgi.service.metatype.annotations.ObjectClassDefinition; @ObjectClassDefinition(name="Document Cloud Service Configuration", description = "Connect AEM Forms With Document Cloud") public @interface DocumentCloudConfiguration { @AttributeDefinition(name="Client ID", description="Client ID") String getClientID() default ""; @AttributeDefinition(name="Client Secret", description="Client Secret") public String getClientSecret() default "26dc4de1-f7f0-46b6-9e8e-86270ad34f58"; @Attr
Create an Adobe I/O project by Adobe Docs Abstract Video: https://images-tv.adobe.com/mpcv3/5255/30cbbbbf-f4ca-429c-820f-2f80d72dcb50_1620669322.854x480at800_h264.mp4 The first step in creating the integration is to create Adobe ID Go to the Adobe Developer Console Login using your Adobe ID created in Step 1 Create a new project Please follow the video to create your Adobe I/O project. Read Full Blog Create an Adobe I/O project Q&A Please use this thread to ask the related questions.
AEM - Implement the methods of the interface by Adobe Docs Abstract Interface implementation The following is the complete code the class implementing the interface. This class makes use of 2 utility methods getAccessToken, getJWTToken and static method getContentAnalyserRequest of GetContentAnalyser class. package com.aemforms.doccloud.core.impl; import java.io.BufferedInputStream; import java.io.ByteArrayOutputStream; import java.io.File; import java.io.IOException; import java.io.InputStream; import java.nio.charset.Charset; import java.security.KeyFactory; import java.security.interfaces.RSAPrivateKey; import java.security.spec.KeySpec; import java.security.spec.PKCS8EncodedKeySpec; import java.util.ArrayList; import java.util.HashMap; import java.util.List; import javax.mail.BodyPart; import javax.mail.internet.MimeMultipart; import javax.mail.util.ByteArrayDataSource; import org.apache.http.Consts; import org.apache.http.HttpEntity; import org.apache.http.HttpHost; import org
AEM as a Cloud Service Tutorials - Create custom process step by Adobe Docs Abstract Custom Process Step The following is the complete code of the custom process step which converts and replaces the native files with the converted pdf’s. This custom step searches for all attachments under the folder name which is provided as a process argument in the workflow. This custom process step uses the methods of the custom DocumentCloudSDKService to create PDF’s. package com.aemforms.doccloud.core; import java.io.InputStream; import java.util.HashMap; import java.util.Map; import javax.jcr.Binary; import javax.jcr.Node; import javax.jcr.Session; import org.osgi.framework.Constants; import org.osgi.service.component.annotations.Component; import org.osgi.service.component.annotations.Reference; import org.slf4j.Logger; import org.slf4j.LoggerFactory; import com.adobe.aemfd.docmanager.Document; import com.adobe.granite.workflow.WorkflowException; import com.adobe.granite.workflow.WorkflowS
Creating your first OSGi Service with AEM Forms by Adobe Docs Abstract OSGi Service An OSGi service is a Java class or service interface, along with a number of service properties as name/value pairs. The service properties differentiate among different service providers that provide services with the same service interface. An OSGi service is defined semantically by its service interface and implemented as a service object. A service’s functionality is defined by the interfaces it implements. Thus, different applications can implement the same service. Service interfaces allow bundles to interact by binding interfaces, not implementations. A service interface should be specified with as few implementation details as possible. Read Full Blog Creating your first OSGi Service with AEM Forms Q&A Please use this thread to ask the related questions.
Creating your first servlet in AEM Forms by Adobe Docs Abstract Sling Servlet A Servlet is a class used to extend the capabilities of servers that host applications accessed by means of a request-response programming model. For such applications, Servlet technology defines HTTP-specific servlet classes. All servlets must implement the Servlet interface, which defines life-cycle methods. A servlet in AEM can be registered as OSGi service: you can extend SlingSafeMethodsServlet for read-only implementation or SlingAllMethodsServlet in order to implement all RESTful operations. Servlet Code import javax.servlet.Servlet; import org.apache.sling.api.SlingHttpServletRequest; import org.apache.sling.api.SlingHttpServletResponse; import org.apache.sling.api.servlets.SlingAllMethodsServlet; import org.osgi.service.component.annotations.Component; import org.osgi.service.component.annotations.Reference; import com.adobe.aemfd.docmanager.Document; import com.adobe.fd.forms.api.FormsService;
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.