Custom search in AEM 6.3 | Community
Skip to main content
dhawanmayur
Level 2
January 19, 2018
Solved

Custom search in AEM 6.3

  • January 19, 2018
  • 13 replies
  • 6297 views

Hi,

I want to search the CRX (cq:Page and not DAM) based on some property like jcr:content/someId . How can it be acheived via the AEM search console. This functionality is to be given to non-technical people so that they can use it for searching pages with some particular someId.

Please share steps to implement such a solution and also how can it be tested.

Any help is appreciated.

Thanks

Mayur

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by VeenaVikraman

Mayur,

      Get in touch with your UI team and come up with a Mock HTML. Meanwhile , work on the usecases you need , like what you want to search, how the search should work, make all the decisions (I believe you already have an idea on what to develop) and once the HTML is ready you can start developing the page as you do a normal web page development. Is there something else you are specifically looking for ?

Thanks

Veena

13 replies

dhawanmayur
Level 2
February 1, 2018

Yes . The link Implementing a Custom Predicate Evaluator for the Query Builder  is helpful for that.

I want to know if there is any other way to build a custom search as mentioned by Veena

Thanks,

Mayur

VeenaVikraman
Community Advisor
VeenaVikramanCommunity AdvisorAccepted solution
Community Advisor
February 1, 2018

Mayur,

      Get in touch with your UI team and come up with a Mock HTML. Meanwhile , work on the usecases you need , like what you want to search, how the search should work, make all the decisions (I believe you already have an idea on what to develop) and once the HTML is ready you can start developing the page as you do a normal web page development. Is there something else you are specifically looking for ?

Thanks

Veena

edubey
Level 10
February 1, 2018

I am not sure why you are complicating it.

Treat it as one of the configuration page. Build a search component, (should be able to leverage from OOTB)

Put it on a template for author. Restrict the access to it and don't publish this page.

Thanks