This data is not persisted OOTB anywhere. If I were to attempt this I would probably start by trying to inject Analytics code (by way of Launch) into the ClientLibrary used for Search. This custom JS would send the searched terms to Adobe Analytics (or whatever web analytics system you have) which w...

Can you simply deny read permissions on the folder for the user group that maps to this role?That will obviously result in these users not being able to browse (or in general, see) these assets, but it sounds like you might not want that anyhow? 

You're supposed to be directly referencing anything in the com.google.gson.internal package... that's why it's called "internal". See the big warning on the GSON JavaDocs site for these internal packages [1] that reads: Do NOT use any class in this package as they are meant for internal use in Gson....

Adding a depdency in your pom is NOT the same as embedding the dependency and deploying it as part of your package to AEM. You need to do the latter. You can do this in a similar fashion as you embed your Core OSGi bundle in your ui.apps content package.

After following the POM updates in the linked blog update, try the following maven commands: $ mvn clean package -DskipTests$ mvn test IIRC I would occasionally run into this issue if the OSGi SCR metadata XML files weren't generated when the tests ran; doing the `mvn clean package` would generate t...

You can overlay the menu node and add a rendition condition to it. Overlay: /libs/dam/gui/content/assets/jcr:content/actions/secondary/create/items/metadata at /apps/dam/gui/content/assets/jcr:content/actions/secondary/create/items/metadata Add a rendition condition at: /apps/dam/gui/content/assets/...

Use this thread to ask any questions related to the Authenticating to AEM as a Cloud Service from an external application on Experience League. Experts are monitoring this thread to ensure your questions are answered.

Try version 0.0.8+ of the repo modernizer plugin. The prior version exhibited this symptom, and the way to work around it was to perform a non-global install of @adobe\aem-cs-source-migration-repository-modernizer in the same folder in which you're running the aio plugin from. Ex.$ cd project-to-mod...

Thanks, @Taishi_Yamada  - I've asked the support team to take a look into these issues. Sorry for the inconvenience.

Just to avoid confusion for folks that might stumble upon this thread in the future ... Package Share has been replaced with Adobe Software Distribution: https://experience.adobe.com/#/downloads/content/software-distribution/en/general.htmlTo access Software Distribution, you must log in with your A...