Since 6.2, the UI page editor should be use for editing AEM Sites pages, and not the ClassicUI page editor. Since this feature directly supports extending the ClassicUI page editor’s content finder, it is deprecated.
Purpose
Use QueryBuilder HTTP API syntax to drive ContentFinder queries instead of more restrictive GQL.
How to Use
Install the ACS AEM Commons package
Create a new Content Finder Tab JS file
Update the contentfindertab config JS object to include:
url: “/bin/wcm/contentfinder/qb/view.json”
baseParams: { .. }
JS object representing the QueryBuilder API key/value pairs used to drive all of the ContentFinder Tab’s queries
If no baseParams are set then the suggestField will populate the query param
getParams: { .. }
JS object representing the dynamic QueryBuilder API key/value pairs used to drive all of the ContentFinder Tab’s queries (baseParams will be used in conjunction with these)
If no path keys are specified, the serlvet’s suffix will be used to scope the search
Query parameter query is translated to QueryBuilder param: fulltext