Understanding full-text search
PRPC incorporates a full-text search facility. 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.
Note: 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.
Use the Search landing page tab to control full-text searching on your system. Select 
> System > Settings > Search to access this tab. Indexing is enabled for rules and data, but not for work items or their attachments, when PRPC is initially installed.
Using the Search landing page tab or the System Management application, you can rebuild indexes completely, or consolidate and compact indexes for improved search performance.
In a multinode system, the indexes are usually maintained on only one node to save disk space and processing. Searches entered by users connected to another node are forwarded to the hosting node using Connect SOAP rules (with Data-RuleSearch as the Applies To class). Set the node to maintain the indexes in the Index Host Node Settings part of the Search landing page gadget.
You can exclude indexing for objects of individual concrete classes derived from Work-, Rule-, or Data- by checking the Exclude this class from search? on the Advanced tab of the Class form.
Allowing users to search work items
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:
- Full-text searches may reduce the chances that an application user enters a duplicate work item.
- Full-text searches do not depend on exposed columns; all the text is searched.
- Full-text searches can increase operator productivity by providing faster access than structured searches.
- Full-text searches may produce many "hits" that require further review and qualification.
- Full-text searches may disclose sensitive work item or work item attachment details to users who otherwise are not permitted to open or review such work.
- Indexing (performed in the background by an agent) and searching (performed on request) can impact system performance.
- Full text searching include hits found within file attachments in Acrobat PDF format or Microsoft Office formats (Word, Excel, PowerPoint), if these attachments are stored within the PegaRULES database.
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 25620 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.
Building and maintaining indexes
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.
To access the Search landing page tab, select > System > Settings > Search.
Operation of the indexing engine
When enabled, the index engine component of PRPC 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 multinode 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 PRPC operates. When rule indexing is enabled, these are indexed at each system pulse and rules of these types may appear in search results.
|
Lucene, pulse |
|
System category — Settings landing page
Designer Studio — Using the Search landing page tab Understanding the Pega-RULES agent |
Concepts