Just sharing one idea here if we do send required metadata of each asset to Solr for indexing and use this Solr search in external application.
Do you see any deficiency @arunpatidar with this approach?
We use @reference annotation to inject OSGi service.
You can define your Util class as similar to https://github.com/adobe/aem-core-wcm-components/blob/main/bundles/core/src/main/java/com/adobe/cq/wcm/core/components/internal/Utils.java
Then call the relevant static method using
Utils.methodname...
I feel if you add those users to OOTB content-authors user group as shown below then they will be able to use pick button as expected -
I have tested at my end. Please give a try.
Sharing few examples -
https://www.flexibledesigns.rs/creating-a-link-rewriter/
https://wttech.blog/blog/2019/how-to-use-sling-transformers-in-aem/
Here you could see, they have rewriter under /apps/APPNAME/config
While uploading asset via AEM Desktop app I am seeing INFO below -
05.02.2023 17:59:53.436 *INFO* [127.0.0.1 [1675600193357] HEAD /api/assets/we-retail/en/people/mens/aem-gems-012016-oak-lucene-indexes-async-local.pdf.json HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Res...