@skumari1 Did you find any root cause or solution for this issue?

@nibedita07 The issue is introduced by AEM service pack 10 and 12. The fix is part of Service Pack-13.

This article have the solution I am looking for and I implemented it successfully- Able to capture the component data via events. https://experienceleague.adobe.com/docs/experience-manager-learn/sites/integrations/analytics/track-clicked-component.html?lang=en

We don't have user action auditing. But versioning which helps us to compare content that's been modified. May be enable versioning and during multiple publishes, You can compare the web content.

@yuhuisg Thanks for your response. Based on the document you provided, I got the point till printing the output in console. Do you know how can we get this output in launch? Like how can we capture the dataObject in Launch that is printed in console? (want to capture this dataObject values in evars ...

We have implemented default adobe client data layer and trying to capture click events. Currently we are able to capture only eventinfo like path..etc. I can see we can capture component data using the path from event info by getting the component full state. Can anyone suggest how to capture compon...

Thanks. This information helps. !!

Yes I am getting the same issue. Based on your comment, I checked this document- https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-19376.html?lang=en. But this will have impact on existing content fragments which are already created. As cq:model property in content fragment ...

I am talking about content fragment model editor not content fragment creation. Below screenshot for reference.

When we create child configuration under another configuration in configuration browser and enabled content fragment models option, I am able to create content fragment model. But model is not showing options to add fields by drag and drop. It is empty when we try to edit.Same is working fine if we ...