Hi @agyrki ,Yes overlaying upload.js and then making a call to your servlet for validation is the right approach, adding a check for only your required filetypes.Thanks. 

Hi @arvindpandey , You can add it on the permissions dashboard via UI, I would suggest deny everything for the parent path and then selectively allow the paths which you want the user to have permission to.deny - jcr:all /apps & then jcr:read for /app/custom Or you can Use Netcentric tool to keep th...

Hi @SudarshanV1 ,You should not write your logics based on coral-id- , since it can change based on the number of coral items on the page or a dashboard - sites dashboard in your case, you should instead target a specific class which is only for the create button e.g. granite-collection-create and r...

Hi @djohn98390536 , Instead of registering the session object as an adapter, try a when/then to return the object  lenient().when(resourceResolver.adaptTo(Session.class)).thenReturn(session)   Regards,Anupam

Hi @bhavigoyal , Yes you can store an html file in AEM assets, but they may not be processed as an asset by default, since .html is not a valid asset type. You may want to update the DAM Update Asset Workflow (AEM on Prem) or Post processor (on cloud). Regards,Anupam

Hi @touseefk2181136 , try below :-Reference - https://github.com/paulrohrbeck/aem-links/blob/master/querybuilder_cheatsheet.md  type=nt:unstructured fulltext=test group.1_group.p.not=true group.1_group.path=/content/data/stores group.1_group.path.self=true path=/content/data 

Hi @vjleo94 , Not sure if you have already tried using this but you will need an external application for this (nodejs)- https://experienceleague.adobe.com/en/docs/experience-manager-learn/getting-started-with-aem-headless/authentication/overview Regards,Anupam Patra

Hi @JustinLe8 , There is no direct connector available for Kaltura to AEM integration, you will have to include it as part of your code and make a API call to connect to Kaltura service. Regards,Anupam

Hello All, I am looking for recommendations to read Asset metadata to determine if the asset is AI generated, as an example I have started with Adobe Firefly, it would be good incase it can be expanded to other AI tools which generate similar contents. (Lets keep it to Firefly for now) In reference ...

Hi @Himanshu_Jain , 1. Delete the existing asset on the target folder first2. Create a version of the asset to be moved3. Move the asset to the target folder Considering you will have all the necessary updates on the asset you intend to move, there would be no  change in metadata.