Skip to main content


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

Creating dedicated indexes

Updated on May 11, 2022

Dedicated indexes are property type-aware, per-class indexes that return the data type of each returned property. Default indexes are typeless, that is, all properties are of type string. Dedicated indexes let you execute queries with filters, date calculations, and aggregations directly in the query. Dedicated indexes are displayed on the Search landing page in the Dedicated indexes section.

Before you begin: To access the Search landing page, you must have the pxAccessSearchLP privilege, which is included in the PegaRULES:SysAdm4 role.
  1. In the header of Dev Studio, click ConfigureSystemSettingsSearch.
  2. In the Security section, select the Customize full text search and For specified properties check boxes.
  3. In the navigation panel, click RecordsSysAdminCustom Search Properties.
  4. Click the custom search property instance that you want to use as a dedicated index.
  5. In the custom search property rule form that appears, in the Properties section, select the Use dedicated index check box.
  6. Optional: To return properties as strings, in the Disable data types for dedicated index column, select the specific check boxes.
  7. In the upper-right corner of the rule form, click Save, and then click Create dedicated index.
    Note: After you create the dedicated index, you cannot clear Use dedicated index check box. You can delete the index on the Search landing page.
  • Dedicated search indexes

    Dedicated search indexes are property type-aware, per-class indexes that return the data type of each returned property. Default indexes are typeless, that is, all properties are of type string. Dedicated indexes let you execute queries with filters, date calculations, and aggregations directly in the query.

  • Deleting dedicated indexes

    You can delete dedicated indexes when you no longer need them. When you delete a class’s dedicated index, the instances of the class are indexed in the relevant typeless index ( Work- or Data- ). When you delete a class’s custom properties search instance, the instances of the class are indexed in the parent class’s dedicated index.

  • Resolving data type conflicts in dedicated indexes

    A data type conflict occurs when a dedicated index contains two fields with the same name that are of different data types. When a data type conflict occurs the status of the dedicated index changes to CONFLICTS FOUND on the Search landing page and in the Custom Search Properties page for that class. Click on Check Conflicts on the Custom Search Properties page to view the properties that are in conflict.

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