sarath3​The usage of packages as a solution is not an ideal long-term solution. You can review the "Migrating between AEM instance" section in Assets Migration Guide for best practices. It's a fairly useful document for anyone looking to migrate assets between AEM instances. The reason you're likely...

Hello Vazahat,The approach suggested by Arun is the path forward.Just a note about the QueryBuilder functionality that when you search for a string like the following in querybuilder, it will perform a fulltext search for those two words separately in the same property. For example, imagine a proper...

Hello antond26624417​You can create a rep:policy node on your component to restrict this access. 1) Go to /useradmin2) Deny permissions for everyone group on the misctools under your RTEplugins node3) Admin user, and any member of administrator's group will have access to this node and therefore the...

Hello pankajg1611582​The following query structure should work for youselect * from [cq:PageContent] as s where isdescendantnode([/content/we-retail]) AND s.[*] = "Pankaj"Best Regards,Aneet Arora

Hello timr69563937​One main observation here is that you have a http mapping and you're hitting a https URL. Clearly the HTTPS is getting terminated at the Load Balancer but AEM doesn't know about it. Therefore, AEM tries to map it exactly and as it doesn't find a https mapping for https://aig-dev64...

rachelb88688093​This is a known issue with the inital release 6.3.3.0.AEM 6.3.3.0 was reuploaded. You can download it again and install this one instead to resolve the issue. https://www.adobeaemcloud.com/content/marketplace/marketplaceProxy.html?packagePath=/content/companies/public/adobe/pack… Bes...

Hello @bims_patel,The IDP initiated login basically takes away the "saml_request_path" cookie. AEM does support IDP Initiated SAML and while using IDP initiated Authentication, you must consult with your IDP to understand how to redirect the user back to the "source" page. One example is the usage o...

Hello Krishna,The error "Could not add record" typically indicates a permissions issue with the datastore. You may have started AEM with a user which doesn't have permissions to write to the datastore directory. Can you please check?Thanks,Aneet

ravitejakolla​I am not exactly clear on how you used to do it but you have a couple of options. 1) Create a workflow package and execute a workflow to Publish these Assets. -> Follow section "Creating a Workflow Package - Classic UI" in documentation Starting Workflows 2) Tree Activate Assets -> You...

trc41594544​You have to ensure that the dependency javax.servlet.http.httpservletrequest is available in AEM. For this, go to /system/console/depfinder and search for javax.servlet.http.httpservletrequest and see which bundle exports it. You can then update you dependency accordingly and try re-uplo...