As a best practice, specify a MaxRecords value to reduce the demand for database activity memory. If necessary, your activity can test the property pxMore on the results page to see whether additional rows were not returned because the MaxRecords limit was reached.

Enter the name of a property in the external table, or an expression involving one or more property names, that specifies the unique key of rows of the external table.

Select to have the embedded pages for the selected instances use lightweight lists for better performance. Leave unselected if the activity performs operations unsupported by lightweight lists, like forward chaining declarative processing, messaging, or value vetting. Refer to the Pega Community article About lightweight lists for more information.

As a best practice, select this check box. This can reduce memory requirements during processing.

Having the embedded pages use lightweight lists does not affect your ability to remove an embedded page completely (with the Obj-Filter or Page-Remove method).

Two dynamic system settings control the use of lightweight lists by the Obj-Browse method. There is a setting each for the Pega Platform and application rules:

• clipboard/lightWeightList/enableForCorePRPCRules - this is set to true by default.
• clipboard/lightWeightList/enableForCustomerRules - this is set to false by default.

When true, these dynamic system settings override the Use Lightweight List check box setting on the Activity rule form.

For example, A AND (B OR C OR (E AND F)).

If you leave this blank, the system assumes the AND operation applies to all rows of the array.

For an external class, complete at least one row of the array.

You can return any property — exposed as a column or not — in the results by setting the Condition field to Value Only. However, only Single Value properties exposed as database columns can be used as selection criteria.

Click the Open icon to open the property. Do not use the Gear icon.

To restrict the search to specific values of a property, enter a property reference that is exposed as a database column. You can review the database schema to determine which properties are exposed for a class. Consult your database administrator for information on the current database schema, or use the Modify Schema facility. See Property optimization.

Select a comparison, such as Is Equal or Is Less Than.

• Select Value Only if the search results are to include the property value, but the property value is not to be used as a selection criterion.
• Select Is Null to require that the field a have null value.
• Select Is Not Null to require that the field have a value.

Click the Open icon to open a property. Click the Open expression builder icon to start the Expression Builder.

• If you enter an expression involving function rules, Java, and properties on various clipboard pages, then at run time the expression is evaluated only once.
• If you enter a property (that is exposed as a column) that applies to the ObjClass class, the Value value is evaluated for each row.

For example, if the Field field contains a DateTime property ExpireDateTime, the Condition is IS GREATER THAN, and the Value field contains a function computing the current date and time, the function is evaluated only once, not once per row.

If the Condition is Value Only or Is Null, select No Sorting.

For list view reports that save results as an XML file in the lookup list cache, identifies the file name.

A Page List. Identifies the parameters that define search comparisons, for the Obj-List method:

• pyConditionFieldName — A property reference resulting in a single text value
• pyConditionOperation — A comparison operator, such as "<"
• pyConditionValue1 — An expression for the comparison value

For list view and summary view rules, identifies the value of the pyAction parameter to the ShowView activity, such as PREPARE or SHOW.

For list view and summary view rules, identifies the name of the window that is to hold the resulting display.

Elapsed time in seconds to process the RDB-List operation. Read-only.

Indicates whether there are more instances not returned. Values are true or false. Read-only.

Optional input to limit the number of rows returned.

Indicates the key of the first row (instance) not returned, if pxMore is true. Read-only.

Identifies the class containing the instances that are to be searched. This property is different from pxObjClass, the class of this page, which always has the value Code-Pega-List.

For list view or summary view rules that support report paging, the maximum number of results to presented on a page.

A DateTime value recording the start of the operation. Read-only.

A Page List containing pages with individual search results. each of the class defined in the pxObjClass property. (Not used for Obj-List methods that specify the lightweight results format.) Read-only.

Number of rows of data returned by the search. Read-only.

For the Obj-List method, indicates that the results are in a special format rather than in pxResults pages. Read-only.

For the Obj-List method, the SQL statement sent to the database before substitution. Read-only.

For the RDB-List method, SQL statements as sent to the SQL database. Appears only when requested through the {SQLPage} syntax. Read-only.

For the RDB-List method, SQL statements before substitution. Appears only when requested through the {SQLPage} syntax. Read-only.

For the Obj-List method, elapsed seconds taken for the method. Read-only.

For the RDB-List method, the total number of results returned by the query. This is set only if pyReturnTotalResultCount is true. (If pyReturnTotalResultCount is false, then this is zero.) Read-only.