Hi AEM Community,   We have developed custom buttons and links in the standard AEM Assets Console for the assets which our business team should use for their day to day operations.However, they are navigating to the Assets Essentials console which has a personalized workspace with some add-ons such ...

Request for Feature Enhancement (RFE) Summary:OTB Workflow triggering Email service as assets are pushed from Brand Portal to AEM are incorrect.Use-case:The default workflow when pushing assets from Brand Portal to AEM has the following status - 1.  The contribution folder asset-sourcing-test is que...

Hi All,   Just posting this answer for posterity - the issue was because of the permissions in Brand Portal. A viewer access in Brand Portal will not be able to push the assets to AEM. The users who are admin/editor in Brand Portal are able to do so. The documentation for Asset Sourcing in Brand Por...

Hi AEM Community,   We are running Asset Sourcing Workflow to pull in assets from Brand Portal to AEM Instance. But the same is not happening. We ran the workflow multiple times and compared it with the only time it worked from the logs to come up with the below findings -    1. com.day.cq.dam.asset...

Hi @arunpatidar, this actually happened for only 3/10 indexes we updated. For the others the new index definition was available without the new version specification as well. But yes new version should always be added to the index. Thanks!

@aanchal-sikka - Thanks for your response! No there were no updates other than the one which we wanted to originally deploy.Using the same name without a version number has apparently led to this issue. The reindexing was not complete even after 6h post deployment which was weird. We tried the below...

Hi AEM Community,   We are pushing some custom indexes (updating) via code to Stage and Prod. But for some reason couple of indexes are not getting updated.   We have tried couple of builds but nothing worked until we tried the below- We installed an empty package to remove the indexing and then tri...

@Jörg_Hoh - The git commit from 5th Oct was picked up instead of 31st Oct & it was deployed to PROD as well

Hi @aanchal-sikka, thanks for the response! We have raised the Adobe ticket as well but just wanted to get an idea if the issue's been seen before. It came up only in this release when the AEM instances got upgraded to 2023.10.14029.20231020T111912Z.

Hi AEM Community,   We had a trigger on our release/production pipeline by the AEM Maintenance Update. The weird issue was that the pipeline was triggered with an old git tag and Commit ID.   The auto update picked up the Git Tag and Commit ID in the release branch from October 5, 2023. The most rec...