Hi @annkitaaggarwal,Nested list shares the same name for the parsys of both the items (Migration and Distributed work in this case)Highlighted in bold is the cause, It should be unique.item1items1items2item2items1items2Provide some unique name to the same, something like below will produce the resou...

Hi @P_V_Nair,Thanks for the confirmation. If you would have tried to test functionality of that action, in the process of reviewing an asset -> In reviewtd/payload.html (on click of "Review" CTA), it will list all the siblings of the selected asset though the item url is just the asset path.In the s...

Hi @Ronnie09,Is it possible for you to share theexact old page and new page structure as is in the repocontent details from old that we are trying to extract. Example : Is it a single component. If yes, is it the same resourceType for all the 5-10 old pages.  

Hi @P_V_Nair,List of allowed action for an asset or for a folder happens based on a logic considering ACLs, conditions specific to an action and few other related criteria. Logic for the same is handled separately for folder and for asset.  For asset, it is exactly at this file - /libs/dam/gui/coral...

Hi @TB3dock,Could you please confirm if the PROD specific OSGi configs are created/available within one of these config foldersconfig.prod (PROD Service in general, applies to both author and publish)config.author.prod (PROD author)config.publish.prod (PROD publish)and dev resides in its respective ...

Hi @this-that-the-otter,For oak-run tool, we need to use the version same as that of the oak version of our AEM instance - https://jackrabbit.apache.org/oak/docs/command_line.html  For CRX2OAK tool (tool from Adobe), there is no explicit mention along these lines. You can use the next highest versio...

Hi @Shaheena_Sheikh,Based on the approach shared in one of the comments in that blog post, below works fine in my local 6.5.0. It won't work on the already applied text as we don't have an explicit feature for removal as part of this custom plugin (like we have unlink in case of Link Plugin)We might...

Hi @JakeCham,Small correction in the usage. It should be <a href="#" class="${properties.openinnewwindow ? properties.name : 'Default class'}">link</a>

Hi @Abhishekty,Getting it now. Since you are getting the results from nt:base in the query, you can amend the existing OOTB ntBaseLucene something like below. Lucene property index definition for the property named "identifier" and given that it is used for not null check, we need to make use of the...

Hi @Abhishekty,I saw your comment already, was just looking for exact query that is framed per the code snippet.Example : identifier that you are using. (property constraint) Also, query is framed based on certain conditions (example : could guess it is a "LIKE" string) In short, if you could print ...