Hi @SHIBANI06 , Yes you can achieve this by customizing the console . Please refer Customizing the Consoles | Adobe Experience Manager . Also Page editor console is available at /libs/wcm/core/content/editor. Thanks,Nikita Garg
Hi @shams31 , Yes, you should consider migration first as AEM Assets instance should be only single source of assets so that there is no duplication. Please consider below link for planning and migration of assets from sites instance to assets instance.https://experienceleague.adobe.com/docs/experi...
Hi @supriya-hande , Maintenance update is available on the date mentioned in the link but it will get applied to your instance whenever you run pipeline after the update time. So that's why you are seeing the difference. You can check this by clicking on the activity tab. Thanks,Nikita Garg
Hi @supriya-hande , If your project is onboarded to release orchestrator, then the monthly release will get auto installed on the environments when you run the pipeline. You might have seen update available in cloud manager console. On the lower environment, you can choose to update the environment...
Hi @supriya-hande , You can check monthly release of AEM as a cloud service on Current Release Notes for Adobe Experience Manager as a Cloud Service. | Adobe Experience Manager and maintenance notes on Current Maintenance Release Notes of Adobe Experience Manager as a Cloud Service. | Adobe Experien...
Hi @Nandheswara , For path-based servlet, restriction based on extension would not be possible. If you want to restrict servlet based on extension, then you might need to use resource-type based. Please refer to below link for more detailed explanation.Apache Sling :: Servlets and Scripts You can a...
hi @anasustic , Could you please explain the customization you did on AEM DAM Update asset workflow. Also screenshot of step where it fails from UI. Thanks,Nikita Garg