Product Communities

Hi,I am using coral datepicker. But when i am authoring the date and time in datepicker, and picking it in current timezone in Java, it is changing the timezone to UTC and changing the date and time according to UTC time. Is there any way to set any default timezone in AEM ? OR to provide the dropdown for author to select which timezone he wants to use?Thanks,Priya

Session Details Your favorite Summit session has gone virtual! Adobe Analytics Rockstar customers share their smoking-hot tips, tricks, and power strategies. This year, the virtual house will be brought down in a whole new way - via our Analytics Rockstars... Session Schedule Tuesday, Apr 27 | 1:00 PM - 1:30 PM MDT Speaker(s) @ericmatisoff, Senior Evangelist, Analytics & Platform, Adobe Meghan Powers, Manager, Web Strategy, CarMax Halee Kotara, Principal Analytics Consultant, Blast Analytics & Marketing Till Buettner, Head of Web Analytics, DHL Full Schedule Check Here Q&A Please use this thread to ask the question related to this Session. Don't forget to register yourself for this session @ Adobe Summit 2021. 

Hi Everyone! Some of you might be familiar with the innovation lab request asking for the ability to "populate or copy request from" old request. We are currently researching different approaches to address the problem described in this request. We would like to listen to your feedback on some of the ideas that we have as well as get your perspective on the behaviours that would arise as a result of introducing the functionality. If you would like to participate please book a half an hour meeting here . Thanks as always for your participation!

It happens several times, but not happens every time.When I export the metadata profile for a folder, some columns are missing, the columns look like random missing.. but when my colleague export again after me, it works fine again..Checked in error.log, nothing special found..Thanks.

Hello, I am working on adding video to a website, and I am using AEM's video viewer presets to essentially embed the video in. The video has to be looped and auto-played. The issue I am having is that every video viewer I work with (I've made several now) makes about the first 6 seconds of the video really blurry, and then the rest (16 second long video) is completely fine.  Does anyone know why this may be happening? Is there anything I can do about it? I'm guessing it has to do with looping and auto-playing the video because the .mp4 video is not blurry when I view it locally on my desktop. I have also tried exporting this video with high bitrate, adaptive high bitrate, low bitrate and a bunch of other random settings. It doesn't change how it looks in AEM and ultimately on the site when I embed it in. Any help or guidance on this would be really appreciated. Thanks!

The Active profiles report section under Managing Profiles section has been furnished with more information. Pease check out here for more details: Active Profiles   Feel free to reach out for any questions through below comment section or through community Q and A section.

Major Announcements from Adobe Summit 2021 by Faizan Thange Abstract Adobe Summit 2021 was held virtually April 27-29, 2021. It was a grand virtual event that allowed everyone to experience more than 400 sessions and interact with inspiring leaders and speakers within the industry. Each day of the Summit was loaded with great content to help you and guide you to win in your industry by virtue of digital content. If you missed something and would like to be informed about the Summit, you can visit the Summit page and get the updates. Mr. Shantanu Narayen, Adobe CEO, opened the keynote and shared the key takeaways from the Summit. He even highlighted some of their major key partnerships with the global brands and how Adobe is helping those businesses to excel. The keynote saw some of the great industry leaders and influential speakers who shared the industry insights and their experiences. Mr. Anil Chakravarthy, Adobe’s EVP, GM Digital Experience Business, shared his view by stating th

Adobe Experience Manager (AEM) - Taking Application Security to the Next Level by DAVID TRUCHE Abstract During one of our latest AEM projects here at 3|SHARE, we exposed our digital environment to an "Invasion Test" - an activity conducted to simulate an attacker looking to: 1. Identify the technical vulnerabilities of the application; 2. Determine the impact of compromising the confidentiality of internal data, integrity and availability of the application and its information; The attacks were carried out in the Black-Box mode, in which the attacker has no information about the environment, simulating a hacker. Define and Implement Security Headers HTTP security headers can increase the security of your application. Once defined, these HTTP response headers can prevent certain vulnerabilities when running in modern browsers. Enable Content Security Policy (CSP) on your Web Server Content-Security-Policy is the name of an HTTP response header that modern browsers use to enhance the

The Headless CMS Adventure: More than a trend? by MICHAEL GROB Abstract The CMS world goes through a revolution during which it reinvents itself every few years. Currently, the latest trend is the so-called ‘headless’ CMS, which completely separates the management of content from its presentation. As a result, a question arises from website owners and web developers: do we need a headless CMS? Headless CMS offer many advantages compared to traditional CMS, but the added value is also dependent on the context, the number of channels, and what you are trying to achieve with your content. In one of our projects, we followed a headless approach and learned a lot from it. Today, we would like to share our learnings with you and hopefully, this will help you decide which direction is best for your future web project. What are the advantages of a headless CMS? A headless CMS differs from a traditional one, often described as ‘monolithic’ CMS. In a headless fashion, the content and prese

Using Adobe Experience Platform to Convert Subscribers from Free to Paid by Allan Witts Abstract As consumers, we are all familiar with this kind of offer when signing up for a subscription service. It is an attractive offer, giving us the chance to try out and assess the value of the product or service before we commit to paying. From the business perspective, the logic is also clear — gain subscribers by postponing the payment barrier and attempt to convince the consumer that the product or service is worth paying for, such that the free subscribers go on to become paid subscribers. When running such a promotion, the key factor to make it successful is the free-to-paid conversion rate. If this is too low, then you are just giving away your product for nothing during the trial period with no benefit, but if you can make it high enough, then the free trial period becomes a very useful customer acquisition tool. This means that delivering a good product or service in the trial period

Adobe partners with governments in all 50 states to accelerate digital modernization by Jonathan Benett Abstract Digital modernization in government has been picking up steam over the last decade. In normal years, government agencies would often grapple with shifting technology priorities and budgets. This has led to some uneven improvements in the past. However, the need for agencies to quickly support the public due to the COVID-19 pandemic was a driving force and intensified the focus on delivering digital services. This dedication and commitment to expanding digital government has led to the most significant digital modernization effort across all levels of government in our history. The accelerated adoption of new technologies to improve digital customer experience (CX), ensure government mission continuity and support the government’s workforce, was made possible due to dedicated public servants and strong public-private partnerships. Read Full Blog Adobe partners with governm

Photoshop and Adobe Experience Manager: Accelerating creativity through APIs by Pam Clark Abstract Today, we are thrilled to announce that we have created the most powerful connection yet between Creative Cloud and Experience Cloud by integrating Adobe Photoshop and Lightroom’s world-class imaging technology natively into Adobe Experience Manager Assets, a platform used by the world’s top brands to manage and store hundreds of millions of assets. By bringing the power of Photoshop directly to where the assets live, creative and marketing teams can now automate image editing on a massive scale, applying complex operations such as background removal, smart object replacement and even scripting through Photoshop Actions to thousands of files with a single click. Imagine you’re an art director responsible for creating a myriad of product images for online and print catalogs. Instead of having to manage multiple workflows for different audiences and deliverables, you can now create all of

Few users under a group(A group of users under a specific market) are getting not enough rights to manage publications error when trying to Publish Later . We have given complete permissions for etc/workflows and still I receive the same error. We do not want to give administrative access to these groups, since they should have rights to publish later pages only under their market.  What permissions are required for Publish Later ?

situation/problemI have a template (let's call it templateX) and and I have configured the ACS commons marketo component. This is working fine. I can see all the forms in the Marketo environment.I have another template (let's call it templateY) and I again configured the ACS commons marketo component. This is not working fine. All I see in the error.log is "No Marketo configure found for resource...". For whatever reason, it cannot read my Marketo config.Things I've checked:The cloud services (Settings => Cloud Services => Marketo) is set correctly. In CRXDE, this settings is stored on this path => /conf/myapp/settings/cloudconfigs/MarketoAs expected, the pages created using templateX produces no such error in the logs. As a further test, I've created several pages on the working template and no problems at all.I've created several pages using templateY and they all produce the error.Any ideas on how to fix? Thanks

AEM creates additional version of a media assets when you revert between different versions of the asset. This is functionality as design, as the system: expects that the image version that is currently active may have some work in progress changes and may require saving those before moving to another version so it creates a branch version before moving to the selected version   In case this behavior is not desired, you have following options: Option 1: update the “XML Writeback Process” step of “DAM Metadata Writeback” workflow to turn off version creation – refer [1]. Use this option if you don't need the version creation only, but do need other metadata writeback features Option 2: Disable the launcher for workflow “DAM Metadata Writeback”, refer [2]. With this option the metadata writeback is turned off, use this option in case none of the features of writeback are required to know more on why this workflow is required refer this link and to

Dear Team,  . How I can incoperate case sensitive search in AEM 6.2 with predicates.I have tried below mentioned code unfortunately it doesn't work for me.But it is working fine in  5.6.1Predicate authorNamePredicate = new Predicate("@authorName", "property");authorNamePredicate.set(JcrPropertyPredicateEvaluator.OPERATION, JcrPropertyPredicateEvaluator.OP_LIKE);                 authorNamePredicate                     .set("property", "@fn:lower-case(@" + JcrConstants.JCR_CONTENT + "/" + "authorName" + ")");                 authorNamePredicate.set("value", "%" + author.toLowerCase() + "%");                 authorgroup.add(authorNamePredicate); @fn:lower-case(" - is converted to fn:lower-case_x0028_  this is creating issue in AEM 6.2 "/jcr:root/content/geo//*[@jcr:primaryType = 'cq:Page' and not(jcr:content/@hideInNav) and jcr:content/@jcr:title != 'Master Article' and jcr:like(fn:lower-case_x0028_/jcr:content/@authorName_x0029_, 'soumik dey')]/rep:excerpt(.) order by jcr:content/@cq:las

Is it true or false guys?

Release 21.2 - June 2021 Release Environment updates happen in waves, during the indicated timeframes below. Exact dates are communicated by email to each customer. Detailed information about this release is available in the Release Notes Environment Dates Stage June 7-8, 2021 Production June 14-21, 2021   New capabilities included in the release Landing pages validation - You can now add a mandatory agreement option to your landing pages. The Email size section has been updated with information on the maximum size of an email, which is now set to 100 MB by default.  Other documentation updates coming with the release Information has been added on how to change the target mapping in a transactional push notification.  For detailed update on Improvements, Other changes, Technical evolutions, Patches and Fixes, check here: Release 21.2 - June 2021   If you have any further questions, please feel free to post them in the below comm

Easiest way is to make use of translation=no attribute. Authors can insert the additional attribute as 'translation=no' on the paragraphs that they do not want to translate. The translation vendor needs to be informed and they can do configuration at their end to ignore the text with this attribute. The OOTB machine translation (with trial Microsoft Translation connector) showcase the same behavior. Here are few screenshots and steps that would help in better understanding:  Testing with Microsoft Translation : if you define translate=no attribute at paragraph level then it doesn’t translate the complete paragraph. This attribute can be defined at any element and the content inside that element will not be translated. Example : Source Content   Translated Content in Spanish  

Using Adobe Experience Platform to Convert Subscribers from Free to Paid by Eric Knee Abstract This blog details a single implementation for a publishing customer on Adobe Experience Platform. Not all aspects are guaranteed as general availability. If you need professional guidance on how to proceed, please reach out to Adobe Consulting Services on this topic. “30-day free trial! 7-day trial period! First month free!” As consumers, we are all familiar with this kind of offer when signing up for a subscription service. It is an attractive offer, giving us the chance to try out and assess the value of the product or service before we commit to paying. From the business perspective, the logic is also clear — gain subscribers by postponing the payment barrier and attempt to convince the consumer that the product or service is worth paying for, such that the free subscribers go on to become paid subscribers. When running such a promotion, the key factor to make it successful is the free-

Why is nobody clicking your website? Adobe’s brutally honest new AI can tell you by Fastcompany Abstract I’ve written dozens of stories about Adobe over the years, and not to brag, but I’ve never needed an AI to edit any of them. But today, the company is debuting its latest Sneak, or a tease of a new tool to come. It’s called Project Catchy Content, and it’s an AI that can analyze online content, from the photography to the written tone, and tell you if people will engage with it or not—and why. Project Catchy Content promises to analyze blog posts and store listings, suggesting everything from better colors to tweaked copywriting, in order to get the best possible response from your audience. Put differently, Adobe isn’t content with helping you make your website pretty anymore. It wants to help ensure that the design is effective too. As Steve Hammond, a VP of Adobe Experience Cloud who leads the Sneaks program, explains, the work stems from years of Adobe’s AI research. The co

Moving to AEM as a Cloud Service by Adobe Docs Abstract Benefits of Moving to AEM as a Cloud Service AEM as a Cloud Service provides a scalable, secure, and agile technology foundation for Experience Manager Sites and Assets, enabling marketers and IT to focus on delivering impactful experiences at scale. With AEM as a Cloud Service, your teams can focus on innovating instead of planning for product upgrades. New product features are thoroughly tested and delivered to your teams without any interruption so that they always have access to the state-of-the art application. Understanding the Transition to Cloud Service Process The transition journey to Cloud Service involves three phases - Planning, Execution, and Post Go-live. For a successful and smooth transition, you should ensure proper planning and adhere to best practices outlined in this Guide. The figure below shows a pictorial representation of the recommended transition journey to Cloud Service. Read Full Blog Moving to AE

AEM - Install Adobe Experience Manager desktop app by Adobe Docs Abstract Using the Adobe Experience Manager desktop app, the assets within Experience Manager are easily available on your local desktop and can be used in any native desktop applications. Assets can be previewed, opened in native desktop applications, revealed in Mac Finder or Windows Explorer for placing in other documents, and changed locally – the changes are saved back to Experience Manager when you upload and a new version is created in the repository. Such an integration allows various roles in the organization to, 1. Manage the assets centrally in Experience Manager Assets. 2. Access the assets in any native desktop applications, including third-party applications and in Adobe Creative Cloud. While doing so, users can easily adhere to the various standards including branding. Read Full Blog AEM - Install Adobe Experience Manager desktop app Q&A Please use this thread to ask the related questions.

Understand Java API Best Practices by Adobe Docs Abstract Adobe Experience Manager (AEM) is built on a rich open-source software stack that exposes many Java APIs for use during development. This article explores the major APIs and when and why they should be used. AEM is built on 4 primary Java API sets. 1. Adobe Experience Manager (AEM) 2. Product abstractions such as pages, assets, workflows, etc. Apache Sling Web Framework 3. REST and resource-based abstractions such as resources, value maps, and HTTP requests. JCR (Apache Jackrabbit Oak) 4. Data and content abstractions such as node, properties and sessions. OSGi (Apache Felix) OSGi application container abstractions such as services and (OSGi) components. AEM APIs AEM API JavaDocs AEM APIs provide abstractions and functionality specific to productized use cases. For example, AEM’s PageManager and Page APIs provide abstractions for cq:Page nodes in AEM that represent web pages. While these nodes are available via Sling AP

Set up a Local AEM Development Environment by Adobe Docs Abstract Guide to setting up a local development for Adobe Experience Manager, AEM. Covers important topics of local installation, Apache Maven, integrated development environments and debugging/troubleshooting. Development with Eclipse IDE, CRXDE Lite, Visual Studio Code and IntelliJ are discussed. Overview Setting up a local development environment is the first step when developing for Adobe Experience Manager or AEM. Take the time to set up a quality development environment to increase your productivity and write better code, faster. We can break an AEM local development environment into 4 areas: 1. Local AEM instances 2. Apache Maven project 3. Integrated Development Environments (IDE) 4. Troubleshooting Install local AEM Instances When we refer to a local AEM instance, we are talking about a copy of Adobe Experience Manager that is running on a developer’s personal machine. All AEM development should start by writing and