Full-text search overview
The search functionality in Pega Platform provides a convenient way of finding rules, work items, and the documents that you upload to your application. For example, you can search for a specific assignment, and then check the assignment status to determine the remaining workload.
Full-text search uses an external service hosted by Pega that continuously propagates changes to your application by using queue processors. The service propagates the changes automatically, with a short delay. To index your data, the external service requires a data model, which consists of the relevant application records and custom search properties.
For more information, see Understanding relevant records and Custom search properties.
The search functionality also provides the option to check the status of classes that you index.
Indexed classes for Embedded Elasticsearch
- Default indexes
- Typeless indexes for Rules-, Data-, and Work- classes.
- Dedicated indexes
- Indexes for specific classes that you can independently configure.
- Custom indexes
- Special purpose indexes that you create and manage outside of Dev Studio.
Indexed classes for Search and Reporting Service
The actions that you can perform on indexes depend on the type of the index. The following indexed class types are available:
- Rule- class instances
- Indexed rules that are available for search in Dev Studio. All Rule- type classes are indexed in the All Platform Rules class.
- Data- class instances
- Classes that are indexed in the All Platform Data class, or as independent classes.
- Work- class instances
- Classes that are specified in the data model that are indexed independently.
Work item search considerations
Using full-text search reduces the chances of work users entering a duplicate work item, and provides faster access than structured searches. Full-text search can affect system performance during indexing, and can produce many results that require further review and qualification.
If your application uses a composite portal, include the following standard sections: @baseclass.FindWork and @baseclass.SearchField.