When you update settings on the Search landing page tab, be sure to scroll to the bottom of the display to locate and click the Submit button. Your settings do not take effect until you have clicked that button.Pega 7 incorporates a full-text search feature based on Elasticsearch. Depending on settings, developers can search for rules, data instances and work items, and application users can search for work items.
By default, the full-text search facility is enabled for rules, and is accessed by the Designer Studio search facility in the header bar.
This facility uses index files to provide full-text searching. Through settings in the Search landing page tab, you can enable or disable this facility and determine the directory where index files are stored. Indexes are updated in the background periodically, during the system pulse performed by the Pega-RULES agent — typically once a minute.
When you update settings on the Search landing page tab, be sure to scroll to the bottom of the display to locate and click the Submit button. Your settings do not take effect until you have clicked that button.
From the Search landing page tab, refer to the System Settings - Search tab help topic for more information about how to control and configure full-text searching on your system. Select 
> System > Settings > Search to access this tab.
Allowing application users to find work items or work item attachments using full-text search (in addition to structured searches based on owner, party, or status) has advantages and costs. Consider these factors:
If you choose to provide this facility, consider which work types are to be indexed. To exclude indexing for work items of one type, open and check the Exclude this class from search? on the Advanced tab of the Class form. (For an example, see PDN article How to limit text search to specific class instances.)
The standard sections @baseclass.FindWork and @baseclass.SearchField support full-text search. If your application uses a composite portal, include one of theses sections (or similar custom section) in your portal.
The traditional ("fixed") portal WorkUser does not directly support full-text search. To provide this capability, include the standard section @baseclass.SearchField in the New harness for each work type. For an example of this approach, select the PegaSample work pool (select Switch Work Pool > Sample Work from the application menu and start a Simple Task flow (
> Run Process > Simple Task) to open the user form defined by the sample harness PegaSample-SimpleTask.New.
You can copy and customize the standard list view rules Data-Work-Summary.SearchWorkInstanceList.ALL and Data-Rule-Summary.SearchRuleInstanceList.ALL, which present search results. These depend on a standard activity Embed-ListParams.getLuceneContent.
Ordinarily, the Pega-RULES agent rebuilds indexes for Data-, Work-, and Rule- objects continuously. Using the Search landing page tab, you can stop (disable) or start (enable) activities in the PegaRULES agent that performs this processing.
When enabled, the index engine component of Pega 7 maintains indexes automatically for every saved rule, data instance, and work item.
To minimize any impact on user response, indexing operations occur in the background (by the Pega-RULES agent) upon the next system pulse after an object is saved. So, depending on the system pulse setting, search results may reflect slightly stale information and may be incomplete. In multi-node systems, rule change information is automatically propagated to all nodes through the system pulse mechanism.
Some internal rules—instances of the Rule-System-Generated-Access class—are generated automatically as Pega 7 operates. When rule indexing is enabled, these are indexed at each system pulse and rules of these types may appear in search results.
|
Elasticsearch, pulse |
|
System category — Settings landing page
Designer Studio — Using the Search landing page tab Understanding the Pega-RULES agent |
Concepts