Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Search and Reporting Service overview

Updated on August 25, 2021

Search and Reporting Service is a feature that provides effective search capabilities by externalizing the full-text search functionalities into an independent microservice. The independence of the Search and Reporting Service improves maintenance because, for example, you can quickly add new service functionalities regardless of the Pega Platform release cycle.

Search and Reporting Service is a multi-tenant, cloud-based service, which means that multiple Pega Platform environments (tenants) can connect to the same instance of the service. The service provides options to receive requests, and store and segregate data from multiple tenants.

Search and Reporting Service indexes data by using specific queue processors that send information directly to the service. For more information, see Managing queue processors.

Functionalities of the service

By using Search and Reporting Service instead of the embedded Elasticsearch you gain the following benefits:

  • Convenient maintenance and data management by indexing data of specific classes.

    For example, you can save time by indexing specific data of the Work class instead of indexing the whole class.

  • Optimal usage of resources depending on your requirements.
  • Bug fixes and service upgrades regardless of the Pega Platform release cycle.
  • Immediate access to the search functionality, because the service is available by default.
  • Full support of row-level and partial support of property-level security of attribute-based access control (ABAC).

    Row-level security requires configuration. For more information, see Attribute-based access control.

  • Partial support of role-based access control (RBAC).

    Search returns objects restricted by RBAC, but they are inaccessible for users.

  • Search landing page overview

    The search landing page helps you control what data is available for the Search and Reporting Service (SRS). You can decide which classes of specific applications you want to index, to make them available for search. For example, you can index a class that contains data about resolved bugs to make bug resolution data searchable.

  • Indexing class data

    Control what data in your application is available for the Search and Reporting Service to include only the information that you require. You can index data of specific classes into the service to make them searchable for all users.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us