Hi @surya3    Would you please elaborate more on your use case? Do you want to generate Document of Record in .txt file?

Hi @tushaar_srivastava    There is no need to use PageManager API as you are dealing with assets. As @aanchal-sikka has mentioned, use that code snippet to unpublish and delete the assets. Session object also provides you the option to remove the item.   session.removeItem("/content/dam/nextgen/Ehub...

Hi @avni27    Have you tried to use the Sling Logging console (http://localhost:4502/system/console/slinglog (in the navigation: System Console =>Sling => Log Support)?

Refer to the following link to use workflow models to perform bulk processing of promoted Launches pages:    https://experienceleague.adobe.com/docs/experience-manager-65/authoring/launches/launches-promoting.html?lang=en#processing-promoted-pages-using-aem-workflow    Also, there is workflow model ...

Thanks @ChetanyaJain!

Hi @kayest    1. To edit a template, use tools>General>Template. It's showing you this warning because this template is already enabled and pages are built using this template. If you change anything on this template, it will affect all other pages built using this template.   2. Can you elaborate m...

Hi @satoshi1    You would have to write two servlets. One for the reading of the spreadsheet or Json in AEM and second for exporting it as JSON.   Import: You can read both types of file either spreadsheet or Json from the file system or placing it inside DAM.   1. Create a POST servlet 2. Write the...

Hi @Arulprakash07    I don't think there is any OOB feature available in AEP to transform your source JSON. You would have to write your own custom utility in java to transform the JSON. Various methods are available like Google GSON, Jackson in java that you can use to transform the JSON.   https:/...

Hi @Lavita    You can restrict the access of user for this path /libs/wcm/core/content/sites/promotelaunchwizard. This is the quickest solution. It will restrict the end user to access the promote wizard and publish the changes.     Hope this helps.

You can restrict the other page content selectors like infinity, tidy  using the below dispatcher filter rule:   # Deny content grabbing for greedy queries and prevent un-intended self DOS attacks/0017 { /type "deny" /selectors '(feed|rss|pages|languages|blueprint|infinity|tidy|sysview|docview|query...