Skip to main content

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

Checking search index status

Updated on August 25, 2021

Ensure that the data that you index into Search and Reporting Service is free of issues and fully searchable by checking the indexing status. For example, when you make changes in assignments, you can index that data, and then check the index status to ensure that your information is available to searches.

Before you begin: Ensure that you have the pxAccessSearchLP privilege to access the Search landing page.
Note: The PegaRULES:SysAdm4 role includes the privilege.
  1. In the header of Dev Studio, click ConfigureSystemSettingsSearch.
  2. In the Indexing section, click the tab of the specific class type whose classes' status you want to view.
  3. In the Status column, review the class index status.

    For more information, see Statuses of data indexing.

    For example, if the system displays the CONFLICTS FOUND status, you can analyze and fix the issues.

  • Search indexes

    The Pega-RULES agent rebuilds indexes for Rules-, Data-, and Work- objects continuously. You can disable or enable indexing for these classes based on your system performance. For example, building and maintaining search indexes for work objects typically has a larger effect on performance than building and maintaining search indexes for rules or data instances.

  • Statuses of data indexing

    The search landing page provides an option to verify the status of classes for which you index their data into the search functionality. You can analyze the index status to verify whether specific data is searchable in your application.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us