@MaheshaGu You can use productlist component. It provides the details of all the products related to particular categoryhttps://github.com/adobe/aem-core-cif-components/tree/master/ui.apps/src/main/content/jcr_root/apps/core/cif/components/commerce/productlist/v1/productlist   

@AliSyed1 You can create an event listener which can update the year property, whenever start date property gets updatedhttps://medium.com/@toimrank/aem-handler-and-listener-12b6c8b5a3d3

@ramsaipavan Yes you can add the configuration as below in single config file and then you can set the environment variable in Cloud manager for each environment {"org.apache.sling.commons.log.names": ["com.adobe.aem.guides.wknd"],"org.apache.sling.commons.log.level":"$[env:LOG_LEVEL;default=ERROR]"...

@ramsaipavan Yes you can use single file under config folder for all runmodes and then set the desired log level value using environment variable  

@ramsaipavan You can create logger configuration in ui.config folder based on run modes. Environment variable can be used while defining the value of log level and it can be changed at runtime.{"org.apache.sling.commons.log.names": ["com.adobe.aem.guides.wknd"],"org.apache.sling.commons.log.level":"...

@RamaniBa You have to use AWS SDK dependency in your Core bundle to interact AWS KMS with AEMYou can use AEM sling servlets/ Services/ Sling models based on your requirements to interact KMS with AEMhttps://myaemlearnings.blogspot.com/2021/08/embedding-third-party-dependencyosgi.html 

@KannaKarthi You can do do this either from dispatcher using rewrite rules or using etc mapping Please refer the URL belowhttps://www.aemguide.in/2019/07/remove-html-extension-at-dispatcher.html?m=0https://www.albinsblog.com/2018/04/how-to-implement-extension-less-urls-in-adobe-experience-manager.ht...

@Keerthi0555 The application creation has to be done in Adobe Learning ManagerOnce application is created, It can be configured in AEM in Cloud services in Adobe Learning Manager configuration

@Prashardan You can use below repo init script to deny create folder and delete folder option under certain path{  "scripts": [    "set ACL on /content/dam/specific-folder\n    allow jcr:read by everyone\n    allow rep:write by everyone\n    deny jcr:addChildNodes on sling:Folder by everyone\n    de...

@cxasha One possible reason for this error could be the presence of a large number of assets in the /content/dam folder.Please try running this on a DAM folder with fewer assets.If the issue persists, check your error logs and share them here.