Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

How to change the maximum number of records returned by the Lookup List

Updated on September 25, 2019


The Rule-Utility-Function LookupList getDefaultMax function is designed to always return a maximum of 2000 records from the database. This limit prevents performance degradation when thousands of records are returned for every list looked up. However, special situations might require overriding the default limit to satisfy certain business objectives. HFix-6240 for PRPC 6.2 SP1 provides functionality for this scenario. The Suggested Approach explains how to change the maximum number of records to be returned by the Lookup List library function.


Process Commander provides an activity, Code-Security.ApplicationProfileSetup, which is called during logon (after authentication) to perform application-specific initialization. HFix-6240 delivers a change whereby the Rule-Utility-Function LookupList getDefaultMax function reads the maximum number of records from the pyLookupListMaxRecords property in the pxThread page. After installing HFix-6240, you can adjust the default and specify the maximum number of records returned for Lookup Lists.

Suggested Approach

Caution: To avoid negative performance impact, change the maximum number of records returned for Lookup Lists only when necessary. As an alternative best practice, use a Report Definition as the data source for the Lookup List when feasible.

To adjust the default for the maximum number of records returned for Lookup Lists, perform the following steps for each application that calls the Code-Security.ApplicationProfileSetup activity.

 Prerequisite: To have each application define its own maximum number of records returned for Lookup Lists, be sure to define a different Code-Security.ApplicationProfileSetup activity for each application.

      1. Install HFix-6240 on your PRPC 6.2 SP1 server.
  • This hotfix delivers a Rule Utility Function; therefore, be sure to recompile the library for the hotfix to take effect.
  • You can recompile the Lookup List library from one of two forms:
    • Rule-Utility-Function form of the function getDefaultMax
    • Rule-Utility-Library form of the library LookupList.
  • Create or use an existing RuleSet and Version from your application.
  • Copy the (empty) standard extension point activity Code-Security.ApplicationProfileSetup to the new RuleSet version.

    Do not change the name or the Defined On class.

  • On the Pages & Classes tab, for Page Name specify pxThread and select the class Code-Pega-Thread for the page:

     Page Name pxThread for Thread Page Code-Pega-Thread

  • On the Steps tab, delete the placeholder Java step.
  • Add a Property-Set method and specify the property value for pyLookupListMaxRecords on the pxThread page to the desired integer value.

     set LookupListMaxRecords property on pxThread page of activity

  • Save and check in the activity.
  • Log out from your PRPC session.
  • Delete the Lookup List cache.
  • Log in and run your application.
  • Additional Information

    Lookup List cache-definition

    Atlas-Standard properties on search results pages (Code-Pega-List)

    Property-Set method

    Delete LookupList Cache to Refresh LookupList Features

    Understanding caching


    Pega Platform 6.2 SP1 Reporting Financial Services Healthcare and Life Sciences Insurance Communications and Media Government Healthcare and Life Sciences Consumer Services Consumer Services Manufacturing Consumer Services

    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