Hi @goyalkritika ,Your use case is not very clear from your question.is the POST API hosted on AEM itself? or is it external to AEM? How is the page where you want to display the user information related to the post call?

@kautuk_sahni , thank you Kautuk, I have already gone through these articles. These articles provide information and instructions on how to use out of box tokenizers and filters to achieve a given requirement. However, I am using AEM 6.5.10 with Lucene version 4.7.1. which doesn't have any out of th...

Hi @Shashi_Mulugu , there is no filter that supports lemmatization for English, hence trying to implement a custom one.

I am just trying to implement lemmatization for plural word search and implemented it via a Lucene custom token filter. However, AEM doesn't recognize the token filter which is part of the core bundle. Can someone help with an example of how to register a custom Lucene Token filter with AEM? 

@workflowuser This is news to me, could you point me to the documentation or the release notes of an AEM version since when it has been marked only for demo purposes.

@Rohan_Garg , The trick is to create a sample theme on the clean install of 6.5.0 and then install the SP 10. This way you will able to create a test theme with bare minimum detail and then use to create a AF form. The theme editor is broken by some service pack between SP 1 and SP  6 which is again...

Hi @Pulkit_Jain_ @workflowuser The forms add-on comes at a price, and we don't even need all those features forms add-on provides hence we stuck to the basic AEM install as it exactly caters for the basic forms that we create.We are able to create and use themes with our adaptive forms so far until ...

@Rohan_Garg , I am not sure about installing AEM Forms 6.5.11 that is breaking the functionality in question, but I can confirm that SP 11 install on the normal AEM 6.5 is also breaking the functionality. Installing the forms add might resolve the issue but my organization is not willing to pay for ...

Yes @Rohan_Garg , that is exactly what I am referring to.

Hi @Rohan_Garg, I did a little more troubleshooting and it looks like the issue got introducted with 6.5.11. It is mentioned in the known issues of that release.