@Johann_Lu  If your client is ok with creating a zip file of the folder structure that you want to upload, you can opt for the extract archive option. https://experienceleague.adobe.com/en/docs/experience-manager-learn/assets/advanced/extract-archive  

@Johann_Lu you can only upload files in AEM DAM from the assets console. However, this might be a possibility with the AEM desktop App (at least to some extent).   https://experienceleague.adobe.com/en/docs/experience-manager-desktop-app/using/archive/best-practices-for-v1  

@SUNITACH1 Just parse this json into a JSON object and then read it accordingly. Once you have the relevant json field, simply use any of the JCR APIs to set these as properties.   Something like this should work for reading the json atleast. I tried with the below mentioned version of org.json libr...

@SUNITACH1  There are 2 POCId fields, one is accessible like topicBody.pocId[0] and the second as topicBody.conceptBody.pocId[0] Which one are you trying to set as property on the metadata node ?

@MaheshMR28  A similar discussion on this topic - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/sightly-in-aem-6-3-org-apache-sling-api-request/m-p/267597  

@MaheshMR28 Can you share your HTL code as well just to see if there is anything that we can spot there?

@Divakarkp The possibilities are endless but let me share some that you can try to get hands on with key AEM concepts.   1. Update OOTB DAM asset update workflow and add a process step that publishes the asset once asset processing is finished. 2. Create a Event Listener that listens to all Page act...

@NicholasT2 You can use Apache FOP to encrypt and decrypt PDF content. https://xmlgraphics.apache.org/fop/2.3/pdfencryption.html  

@manikanthara  You need to check your dispatcher configurations wrt allowing query parameters. https://medium.com/@toimrank/aem-dispatcher-filter-section-a8c03a92c256  

@Starpuff  I agree this is a confusing at times. A way to read this would be that when a workflow instances moves to Failure with running status, that means there is atleast one process step that hasn't completed before the workflow instance goes into error state.