Hi @tapasa4aem  If you already have an API then you don't need middleware/BFF. you can call API from clientside(fetch/ajax using javascript).In case you want to protect endpoints with secret, you can use CDN as proxy pattern.

Hi @PrachiAt1  Please check  https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/custom-validation-to-asset-metadata/td-p/397662 https://medium.com/@theopendle/aem-custom-metadata-forms-for-assets-8c6597205f9d   

Hi @AmitVishwakarma The git url format is not wrong, please check the documentation. Cloud you please also share the reference document for your reply?   I am adding the Repository URL format from official Adobe doc shared by @giuseppebag    Repository URLRequired. The URL of the repository.If you a...

Hi @Shankar_K  Could you please check dispatcher filter rule? Make sure this is not overriden by another rule at the bottom of the rules.   # Enable clientlibs proxy servlet/0012 { /type "allow" /method "GET" /url "/etc.clientlibs/*" }  

Hi @BhavaniBharani  I think you can run the post processing workflow as independent workflow as well. https://experienceleague.adobe.com/en/docs/experience-manager-learn/assets/configuring/auto-start-workflows   If you can't then you need to create a custom workflow with the same preprocessing logic...

Hi @PrachiAt1  You need to write either a clientlibs which will be act on either on tag field or on save to validate number of tag. Or create a custom metadata schema to change tag selector field property multiple to false.

Hi @vikkip1 Seems you are getting timeout.You are on the right track, please check the error logs. Seems issue with index. You can raise this with Adobe as well. 

Hi @tapasa4aem  You need a BFF or Middleware to perform any backend logic like sending an email etc.

Hi @TalariPr1  Could you please check the console error?

Hi @Darmien  If you use container component with responsive layout as a wrapper/container for the children component, then responsiveness will work