Adobe Experience Manager Sites & More

LinearGradient · 10/15/15

Hi,

Here, some of these options are used throughout the examples, but are they listed and documented somewhere?

Thanks,
Behrang

aanchal-sikka · 12/5/23

Please refer to following cheat sheets of Query builder

https://experienceleague.adobe.com/docs/experience-manager-65/assets/JCR_query_cheatsheet-v1.1.pdf?l...

https://github.com/paulrohrbeck/aem-links/blob/master/querybuilder_cheatsheet.md

Aanchal Sikka

View solution in original post

smacdonald2008 · 10/15/15

You referenced the main docs on this subject - if they are not up to your satisfaction - please file a ticket here:

http://helpx.adobe.com/marketing-cloud/experience-manager.html

Mshaji · 10/15/15

That is the official link from Adobe for querybuilder options, it includes all the options. However if you want more robust queries you can do jcr queries, it includes many options.

You can find more details here.

http://docs.adobe.com/docs/en/crx/current/developing/searching_in_crx.html

LinearGradient · 10/15/15

That page does not have the complete list of all the possible options. It only contains some examples that use one or more of the available options, and even the ones that are listed there are not explained in detail.

For example, what's the difference between:

query.index=true and query.index=false
orderby.index=true and orderby.index=false

Thanks,
Behrang

LinearGradient · 10/15/15

Do you know what's the purpose of orderby.index = true vs false?

Thanks,
Behrang

DarrenBiz · 10/15/15

Behrang - in general you wont find much useful documentation on this unless it lives on the QueryBuilder doc page you mentioned. I struggled to find how a lot of the query builder options worked and what the PredicateEvaluator properties did. I suggest looking through the PredicateEvaluator API as they sometimes give a meaningful description of the PredicateEvaluator and its options, but not always.

I found that using the local QueryBuilder debug page (http://localhost:4502/libs/cq/search/content/querydebug.html) and just playing with the options to see what Xpath is generated, then google what you see. All QueryBuilder searches evaluate to more meaningful Xpath that you have more documentation available on.

Cheers