Skip to main content

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.

Support Article

Obj-Browse Incorrect Behavior



On using the Obj-Browse method and passing the ObjClass parameter as a reference rather than a literal value, the Pega application runs a browse to determine which properties to include in the Select statement that is limited to 50 results.
As Skims are performed throughout the life of the application, copies of properties are created in the newer ruleset versions. As a result, more than 50 properties are found in the various versions. Pega does not always return all the properties which results in inconsistency and incorrect fields being returned.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a class mapped to an external table.
  2. Create 11 exposed properties.
  3. Perform five major Skims.
  4. Add a new property to the class.
  5. Write an activity that performs an Obj-Browse for the class.
  6. Pass the ObjClass parameter as a reference to Local Value or Parameter.
  7. Execute the activity and perform a Trace. Pega application runs a query before the Obj-Browse for the pr4_rule_property table with a limit of 50 records returned.

Root Cause

A defect in Pegasystems’ code or rules.
The limit of 50 results prevented the retrieval of the correct property.


This feature is implemented in Pega Platform 8.1.8.

Published August 12, 2020 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us