Hi @pharidoss, Well this could be a bug in Core components, if you compare v2 and v3 dialog implementation: v2 - https://github.com/adobe/aem-core-wcm-components/blob/main/content/src/content/jcr_root/apps/core/wcm/components/title/v2/title/_cq_dialog/.content.xmlv3 - https://github.com/adobe/aem-co...

Hi @Shiva-kumar, In general the problem is that you are trying to use RTE plugins with textarea - this is incorrect. Textarea support plain text only. Please use RTE resource type cq/gui/components/authoring/dialog/richtext. I would recommend you to have a look how Text component from Core component...

Hi @digarg, This is not possible OOTB. The main reason of this, is a fact that inbox is a unified view that can present different type of items and each item can be connected with different type of action. You can try to customize inbox view on your own (or create custom console), but I think this w...

Hi @Deleted Account, Please explore Dialog Participant Step option. It allows to include custom dialog code between Next step and Comment fields. So you should be able to achieve result like this, or any other that is need: Example step by step: https://lhotsetechnologies.com/blog/dialog-participan...

Hi @Blue-Dog, Yes this is possible to get annotation data using Reports from ACS Commons. Here is an example, for below crx structure . Report configuration, I have used following SQL query to get the data: SELECT child.* FROM [nt:base] AS parent INNER JOIN [nt:base] AS child ON ISCHILDNODE(child, p...

Hi @Mario248, You can try to use Container step: And the documentation: https://experienceleague.adobe.com/docs/experience-manager-65/developing/extending-aem/extending-workflows/workflows.html?lang=en#step

Hi @akshaybhujbale, In general all looks to work as expected. Please be aware that what you can see on this view It is not content that is part of this specific page it is content of following CF /content/dam/we-retail/en/experiences/arctic-surfing-in-lofoten/arctic-surfing-in-lofoten which is refe...

Hi @Ravi_Joshi, This is AEM issue. I was able to reproduce this on multiple different clear AEM versions. It seems that different css styles are applied on assets view and in asset browser. You can try to override css style, but I think better idea will be to raise Adobe support ticket - and ask Ado...

Hi @Mohammed_Zackriah, This is expected, and you can ignore this issue in context of Content Fragments. Below I will explain, why you do not need to worried but also why you can see an empty renditions folder for each CF. First of all CF are stored in DAM and they are kept as dam:Asset type. This me...

Hi @Shaheena_Sheikh, As far as I know there is no any char limit in AEM OOTB workflow comment section.