Adobe Experience Manager

There may be times that minor touch ups to out-of-the-box submission actions for addressing business needs through Sling Resource overlaying may look an appealing option.  However, it was found in our environment that applying the concept of Sling Resource Merger in AEM against out-of-the-box submission actions doesn't always work.   When overlaying components in /libs with structure in /apps, it is not necessary to create 1:1 copy of the resource or node, however, in the case of AEM Forms submission action, it's not the case.  Doing so will end up a working submission action overlay but the Forms Authoring UIs will no longer present the overlaid actions in the form submission type drop down list.    After investigated, it turns out that the Forms Authoring UIs use following code from /libs/fd/af/components/commons/datasources/propertyprovider/propertyprovider.jsp to present the available submission action type:     optio

Hi,I have a template, which has a custom boolean property hideBreadcrumb checked by admin. Now, I'm creating new pages using template programatically. I want all the pages created from template to have hideBreadcrumb property checked by default. Do I need to add any configuration for this? My template property is currently checked but pages created from the template don't have hideBreadcrumb checked. Thanks in advance!

Hi,   We have core-components-examples folder in our crxde which has documentation on our aem core components. I want to implement similardocumentation folder in my project. But I have not got any details on how they created core-components-examples folder. Can anyone help me in understanding core-components-examples folder? Thank you.    

Hi All, We are doing REST API call integration. For this REST API call integration, we need to add a trusted SSL Certificate.We are exploring 2 approaches: 1. Add the certificate into AEM Truststore, and then get the truststore as a keystore object. Next, added the keystore object into SSLContext, and added the sslContext into HTTPClient to call the API. We are getting this "org.apache.sling.engine.impl.SlingMainServlet service: Uncaught Problem handling the request javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_required" exception.     2. The second approach is - to add the certificate to the java keystore (cacerts), restarted AEM instance and called the API using HTTPClient. We are still getting the same "org.apache.sling.engine.impl.SlingMainServlet service: Uncaught Problem handling the request javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_required" exception.   If anyone has done a similar implementation, please ad

Register at: https://adobe.ly/3mRcYEv  Session Details Join us for our virtual office hours - led by members of the inaugural 2022 Adobe Experience Manager Champion Program - as we discuss best practices, share tips, and engage in a live Q&A. Experience Manager Champions will answer pre-submitted and live questions about Adobe Experience Manager Sites functionality, your particular instance, and specific use cases. Whether you're new to AEM Sites or an experienced developer, you're sure to gain some valuable insights from our Experience Manager Champions. Pre-submit a question to our Champions by asking it here: https://forms.office.com/r/XSXw50bn1L  Session Schedule Thursday, March 16th, 7:30 AM (PST) OR 3:30 PM (CET) OR 8:00 PM (IST) Panelist(s) Brett Birschbach, Bounteous (Senior Vice President - Adobe Practice), Greg Dimeris, T. Rowe Price (Web Content Product Owner), Vengadesh Shanmugavelu, Qatar Airways (Senior AEM Architect), Rami El Gamal, RENY Consulti

Hello all, I would like to share a finding about the latest AEM Forms 6.5.16 Add-ons in hope that it would help those who experienced the same issue as well as an explanation as to what's happening.   In our server environment using AEM 6.5.15 + AEM Forms 6.5.15 with JDK 11.0.15.1, after upgrade to AEM 6.5.16 SP + AEM Forms 6.5.16 Add-ons + JDK 11.0.18, the out-of-the-box REST endpoint submission type starting to fail with following error in the log even when the upgrades were clean and successful: com.adobe.aemds.guide.utils.GuideSubmitUtils.getRedirectParameters(Lorg/apache/sling/api/SlingHttpServletRequest;)Ljava/util/Map; at org.apache.jsp.libs.fd.af.components.guidesubmittype.restendpoint.post_POST_jsp._jspService(post_POST_jsp.java:373) at org.apache.sling.scripting.jsp.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) [org.apache.sling.scripting.jsp:2.3.6] at javax.servlet.http.HttpServlet.service(HttpServlet.java:764) [org.apache.felix.http.servlet-api:1.2.0]​

Hi All   i have implemented a workflow model where we have dialog step and participant steps with multiple reviewers and approvers . when user initiating a workflow  to provide all the required inputs in dialog step and request for review the data. am trying to auto populate values from workflow history in dialog participant step when it got rejected by any of the reviewer for additional information. can someone advise how to achieve this.   Thanks in advance .      

Hi all, Am seeing this error when am trying to build my project . am trying to read the adaptive form’s submitted data is in xml format using  WorkitemUserMetadataService have imported the following package. import com.adobe.fd.workspace.service.external.WorkitemUserMetadataService;  added dependency as follows in main/core pom xmls as follows:   <dependency>     <groupId>com.adobe.aemfd</groupId>     <artifactId>aemfd-client-sdk</artifactId>     <version>6.3.0</version>     <scope>provided</scope> </dependency>                                                                                                       &nbs

Hello All,  We have noticed on several of our websites the response headers are duplicated:  Response Headers:  Content-Type: text/html; charset=UTF-8Date: Mon, 10 Feb 2020 14:17:19 GMTServer: Apache/2.4.6Strict-Transport-Security: max-age=63072000; includeSubdomains;Transfer-Encoding: chunkedVia: 1.1 ourinstancewebsite.comX-Content-Type-Options: nosniffX-Content-Type-Options: nosniffX-Frame-Options: SAMEORIGINX-Frame-Options: SAMEORIGIN I don't see anything wrong in the dispatcher file and replication agent for these websites.  Any idea whats wrong and how to resolve it? Thank you in advance. Ivo

Hello everyone I have configured the SAML2.0 following https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/saml-2-0-authenticationhandler.html the ipd login page loads and send the post, then when the  http://localhost:4503/content/xxx/saml_login is handled  gives me this response: 09.03.2023 19:46:02.576 *DEBUG* [qtp965154916-494780] org.apache.sling.auth.core.impl.SlingAuthenticator setAttributes: ResourceResolver stored as request attribute: user=admin 09.03.2023 19:46:33.765 *DEBUG* [qtp965154916-494880] org.apache.sling.auth.core.impl.HttpBasicAuthenticationHandler forceAuthentication: Not forcing authentication because request parameter sling:authRequestLogin is not set 09.03.2023 19:46:33.765 *DEBUG* [qtp965154916-494880] org.apache.sling.auth.core.impl.SlingAuthenticator getAuthenticationInfo: no handler could extract credentials; assuming anonymous 09.03.2023 19:46:33.766 *DEBUG* [qtp965154916-494880] org.apache.sling.

I am writing the ResourceChangeListener . I want current page path at  ResourceChangeListener.PATHS. PFB snippet where I want currentpage's path.@8220494(immediate = true, service = ResourceChangeListener.class, enabled = true, property = {"process.label = JSON Event Handler",ResourceChangeListener.PATHS+ "=CURRENTPAGEPATH",ResourceChangeListener.CHANGES + "=ADDED", ResourceChangeListener.CHANGES + "=CHANGED" })

Hi All, How can we dis-allow external emails in Asset Link Share popup. Is there an OOTB way to do it?    

We have this configuration - Apache Felix Jetty Based Http Service and we need to make few updates to it. We think keeping this xml configuration in the codebase will be risky in terms of security point of view and  System Admin or DevOps should manually control the entries in this configuration.   I am wondering what is the forum's recommendation and best practices about maintaining with some critical configurations in AEM?

I'm facing issues with some of my AEM DAM folders while trying to open them from the touch UI. It shows 'failed to load data' while opening the folder and the folder doesn't opens at all. This behaviour is observed with DAM folders with 'Adaptive Media Encoding'. The issue is only observed in the touch UI card view, while list and column views works perfectly. Also I'm able to access and add files to DAM using the classic UI as well.Any direction towards this issue would be appreciated. Thank you!

Hi All -I have extended the PDF viewer core component into our app : /apps/app-name/ and also created the "Content Aware configuration" under /conf/app-name/ and added the property "sling:configRef" that points to Context Aware Config path under /content/site/ but the pdf viewer component is still not visible. I have followed the exact steps provided by @asutosh_jena_ in the post https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/pdf-viewer-core-component-won-t-display-on-page/m-p/406069#M5381 but it's still not working. I verified and client id is correct and domain is also set as localhost as I am trying to configure on my local. The component div is getting created but it's empty.   Please advise

Hi, I have a requirement to allow particular component inside Parsys for Static Template. How can we achieve this? Whenever we create a page based on that template, it should allow to add that particular component in Parsys in edit mode.

I have caconfig editor package as a maven dependency   <dependency> <groupId>io.wcm</groupId> <artifactId>io.wcm.caconfig.editor.package</artifactId> <version>1.12.0</version> <type>zip</type></dependency>   The caconfig editor renders like this,  it looks a little different from what I've seen documented, so I do wonder if its configured correctly.      When I publish though, non of the resource nodes under the configuration are replicated into the publish environment.      

Hi All,I have been having trouble with datastore items not being refresh in the publish instance of aem. I can see the updated values within the author edit mode on a page where the data is displayed.. but the same page when published does not grab the updated data.The datastore is sitting on the path /content/websitename/datastore and is not visible in the actual author view.. I can only view it through the admin console.Is there a way I can force these items to republish? As I can't access them directly it's proving a little tough. 

SAML Authentication configured by following this guide: https://wttech.blog/blog/2019/how-to-setup-aem-publish-saml-authentication-using-okta   After logging in IDP the POST request to configured sign in URL enters into in a continuous loop from http://aem-publish-host/content/......./login.html to https://your-id.okta.com/home/your-id_aempublishlocalhost_1/0oa1ltmftpUq7m9X2357..../SAML ...   The end user is never directed to the requested landing page. I am not able to find anything in saml.logs, any advice for investigation?   Thanks,      

Hi,   We have a select dropdown field in our metadata schema which renders options dynamically with JSON path configuration. The list is configured in generic lists and configured the JSON path as per the ACS Commons documentation[https://adobe-consulting-services.github.io/acs-aem-commons/features/generic-lists/index.html].   This one specific field has about 350 items in list which in-turn will be rendered as dropdown options.   There are no issues when there is no value selected for the dropdown or if a value is selected at the beginning of the list and saved, the dropdown renders fine.   We're observing a strange issue when a value which is at the bottom or at the later point in the list is selected and saved. When the metadata editor is loaded again and we try to expand the select options it just flickers without opening the dropdown fully. The other dropdowns in the editor are working fine.   Please find below code snippet of the schema: <_x0031_555091

I’m relatively new to AEM development. I have recently had to extend one of the core components. Why is it that we extend the interfaces that those components implement, rather than extending the class itself, so that our child class has direct access to all the parents’ methods?   From my understanding, in order to access the parent component’s class methods, we have to instantiate the parent class as a field in the child class with @Self and @2434638, and mark it as a superclass. Why can we not just extend the parent class like any other java parent-child relationship?  For example, to extend the Core Form Options component, I had to create a child class that implements the Option interface instead of extending the  OptionsImpl class.  Then, I had to have a field within my child class that holds the parent component in order to access its public methods, instead of calling directly from the child. Why is that?    

Resolution | org.apache.sling.api.request,version=[2.6,3) -- Cannot be resolved   by Veena Vikraman Overview If you are building your Cloud project with latest archetype and your bundles are not resolving with below issue org.apache.sling.api.request,version=[2.6,3) -- Cannot be resolved , then please read more on how to resolve the issue Q&A Please use this thread to ask questions

if we see under conf/we-retail I want to create new folder to store other templates for same site, which I am not able to create? any work arounds or idea.

I'm trying to use hybrid editor for image cropping and need custom aspect ratios to crop the images.   I downloaded and installed the sample code provided by Adobe Marketing Cloud using hybrid editors from GitHub https://github.com/Adobe-Marketing-Cloud/aem-authoring-hybrideditors   I'm still able to see the default aspect ratio instead of custom aspect ratio.  Updated: Aspect ratios specified under Config node of inplaceEditing should appear instead of the default aspect ratio Also, we will be having Design Dialog so that author can add new Aspect ratios at the component level like below       Thanks in advance    

I have created around 15 groups and added permissions to the Dev environment in AEM(AEMaaCS). Now I want to move them to the production and staging environments. Can I create a package of this filter /libs/cq/core/content/nav/tools/security and use it in another environment? Can anyone tell me how to move group permissions from one environment to another in AEMaaCS?