I think you want to retrieve the applied CSS classes, you might want to take a look at ComponentStyleInfo API https://developer.adobe.com/experience-manager/reference-materials/cloud-service/javadoc/com/adobe/cq/wcm/style/ComponentStyleInfo.html Sample : https://github.com/adobe/aem-core-wcm-compone...

I have also not worked on this plugin, but I think the datsource implementation is generally done in a different way. Something like   protected void doGet(final SlingHttpServletRequest req, final SlingHttpServletResponse resp) throws IOException { ResourceResolver ...

This I believe is a known limitation for Rich text editor https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/operations/rich-text-editor#known-limitations If it is really required then some custom javascript would probably be required.

Can you try adapting from request:@Model(adaptables = SlingHttpServletRequest.class)

By multi tenant solution, I meant multiple solutions deployed on the same AEM instance. But as I mentioned earlier, there could be different reasons for inconsistency depending on how show/hide logic is implemented.And if you are using acs commons then you can utilize their show/hide feature https:/...

I think it should be the other way i.e fields should be hidden initially and when the show/hide logic kicks in the fields should become visible. You can add the hide class to those fields so they are hidden initially. And regarding the inconsistency, it could be due to different factors depending on...

Well, I think you can achieve it using Xpath as well.Something like /jcr:root/content/pb/us//* [ (jcr:like(fn:lower-case(@topicCategory), '%Financial_Adjustments_and_Payments%')) ]