Thanks all - we did face the same issue with the latest SDK and JDK 21 - though this solves the issue it does require us to modify the connector config and re-package. We are facing sync issues with the latest connector cloud version as well. - https://github.com/brightcove/Adobe-AEM-Brightcove-Conn...

I am on the AEM as a cloud service and yes this could be a good OOTB feature as my client also requested the same.For now I provided a report of shared links using the OOTB Assets > Report (Shared Links report) which has more details than the OOTB UI.@BrettBirschbach 

Here is the update from Adobe: As the DirectBinary does not create(not a bug) the folders and the documentation specifically says the folder must exist - see [1]. The logic to create folders is included in the higher level FileSystemUpload wrapper - see https://github.com/adobe/aem-upload/blob/maste...

I am still working with Adobe on this @kautuk_sahni 

Thanks for the response - the folders are created dynamically based on the new products created and they are using a similar command as above.The aem upoad library recommended seems to have an issue so working with Adobe support on this as of now.

Hi all I have posted this on the github of the aem-upload library but would appreciate anyone here also can chime on this? https://github.com/adobe/aem-upload/issues/131

Javascript Use API is deprecated in AEM as A CS and Java Use API is the only recommended option for AEM as A CS. - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/release-notes/deprecated-removed-features?lang=en

I’m looking for guidance on implementing a production-ready User-Generated Content (UGC) solution in AEM as a Cloud Service (AEMaaCS).Could anyone share insights or patterns from their experience?Any advice or examples from real-world implementations would be greatly appreciated!

Thanks for getting back @arunpatidar  what we need is to create a custom schema with ALL the default tabs/fields AND additonally a custom tab with custom fields. We need to be able to do this for few different custom schemas and not just one. What we did was to copy the default schema and customised...

Thanks for sharing the screenshot @daniel-strmecki - We named our custom schema as <tenant_name>_schema and not used default as-is - I see above that you have modified or added  a custom tab within the default schema directly. Also we have multiple metadata schemas which are different to 'default'. ...