Content tab on the Summary View form

Optional. To assign a category to this report, select from the SmartPrompt list. This list shows field value rules with Rule-Obj-Report- as the first key part and pyCategory as the second key part. You can create field value rules in your application to define additional categories.

For example, enter A for the first row, B for the second row, and so on. The Logic field must mention each label.

If the type of this property is TextEncrypted, special instructions apply to the Condition , Value , and Edit Input fields. See Property rules — Implementing and using the TextEncrypted Type.

If you specify pxObjClass and the Applies To key part of this list view rule is a framework class, at run time the report can use the corresponding implementation class, not the framework class, for comparisons and report content. This feature eliminates the need to copy each framework class-based list view report into the implementation class. To enable this capability, select the Report on Descendant Class Instances check box on this tab.

You can specify only properties that correspond to optimized (exposed) columns in the PegaRULES database. By default, custom properties in your application are not optimized; they are stored in a Storage Stream (BLOB) column. If you need additional properties optimized, consult with your database administrator.

Pega Platform converts the Starts With, Ends With, and Contains comparison conditions to an SQL LIKE clause. Vendor-specific, non-standard optimizations such as the Oracle CONTAINS feature are not used. If your application contains a summary view report that requires such comparisons for tables with many rows, you can create a custom getContent activity that implements optimized SQL for retrieval.

• A literal constant, formatted in accordance with the property type. See Constants in expressions. To compare the Field value with multiple literal constants, surround each with quotation marks and separate each with a comma. Place a backslash character (\) before any quotation marks within the constant. You can click the icon to the right of the field to review current clipboard values for the property identified in the Field field.
• A fully qualified property reference to a Single Value property that is present on the clipboard at run time. The Type of this property must match the Type of the property in the Field field.
• A fully qualified property reference to a Value List or Value Group property present on the clipboard at run time. The Type of this property must match the Type of the property in the Field field. To compare the Field value with multiple Value List or Value Group properties, separate each property name with a comma.
• The keyword param followed by a period, followed by a parameter that is defined on the parameter page of the calling activity.
• A period followed by the name of a Single Value property that is optimized as a column. This option allows comparison of the values of two properties in the same instance (database row), if the types are identical or comparable.
• A symbolic date, for a Date or DateTime value. When the list value rule runs, this symbolic reference is converted to an actual date or date range based on the time zone of the user and the Condition value. For example, if the user selects Last Year and the Condition value is IS EQUAL TO, the result is a date range between January 1 and December 31 inclusive, of the previous calendar year.

If the Condition field is set to IS NULL or IS NOT NULL, leave this field blank.

Commas correspond to an OR test. If the Value field contains two or more entries separated by commas, the comparison is true at runtime if the value of the Field field equals (or is greater than, or is contained in, and so on) any one of the entries.

Similarly, when the Value field contains a Value List or Value Group property reference, the comparison is true at run time if the value of the Field field is true for any element in the list or group.

When evaluating either of the two Condition values Greater or Greater or Equal at run time, the result is the same as applying the test to the largest value in a list or group. Similarly, when evaluating the Condition values Less or Less or Equal at run time, the result is the same as applying the test to the smallest value in the group or list. The Value List and Value Group options are most useful for other condition values, such as Contains or Starts with.

Using the Select Values form

Click Select Values to display a form with with one or more of these tabs:

• Available values — The system searches the column in the database corresponding to the property in the Field field to collect and display up to 1,000 values for the Field property in a new window. To add literal values to the Value field, select one or more check boxes, and click Apply. (You can also type literal constants directly, whether or not they are listed.) This tab displays at run time only to users who hold the standard privilege @baseclass.ShowStoredValues. For such users, this tab is available at run time when the Display Available Values? box in the Prompt Settings area is selected.
• Valid values — The system presents values from the Table fields on the General tab of the property referenced in the Field field. To add literal values to the Value field, select one or more check boxes, and click Apply. This tab is available at run time when the Display Valid Values? box in the Prompt Settings area is selected.
• Compatible columns — The system lists optimized properties with the same Type as the property in the Field field, as candidates for this field. This tab is available at run time when the Display Compatible Columns? box in the Prompt Settings area is selected.
• Time Periods — For a property of type Date or DateTime, allows the selection of a symbolic date such as Yesterday or Current Year.

Click OK to accept the value you selected. Click Cancel to close the form without making a selection.

To enable localization, check the Localize? check box on the HTML tab.

Select the check box to test or compare the Field value and the Value value at run time after the system converts both to uppercase. In this situation, "a" matches "A" and is less than "B".

If this option is not selected, tests of the Field value and the Value value occur without case conversion. In this case, "a" is greater than "A" and also greater than "B"

In most cases, do not select this option. Select this option only when required to obtain the rows of the report. For example:

• If your PegaRULES database is hosted by Microsoft SQL Server, comparisons are always in uppercase, so selecting this option does not affect the report contents.
• If your PegaRULES database is hosted by Oracle, IBM Db2 or most other database vendor products, selecting this option can affect which rows are included in the report when values occur in mixed case. However, conversion to uppercase can significantly slow database processing.
• Case conversion is meaningful only for properties of type Text, Identifier or Password. Regardless of the database software, case conversion is not needed for numbers, dates, or text that contains only uppercase or lowercase characters.

For example, assume the criteria in a row is:

If this summary view rule runs when Param.Letter has the value "C", this criteria limits the report to contain only instances in which the Lastname property value starts with the letter C. However, if the same summary view rule runs again when the Param.Letter parameter has no value, this criteria is dropped, so instances with any Lastname value (or none) are selected.

If you do not want this default behavior, select the Use Null* check box to force the Condition value to become Is Null when the Value value is blank at run time. In this example, the criteria is transformed to "Lastname is null".

If this summary view rule runs on a web node as part of a composite application, the Use Null* setting is selected for all criteria.

For example, if the table contains four rows labeled A, B, C, and D, you can specify:

(A OR B OR C) AND D

This notation is the same as for the logic statement in when condition rules.

If you leave the Logic field blank, the system selects only instances for which all criteria rows are true.

If your application supports users in multiple locales, choose a noun or noun phrase for the caption of 64 characters or less, and select the Localize? check box on the HTML tab. Choose a caption already included in a language pack, to simplify localization. You can review or create the field value rule supporting localization. The pencil icon appears only after you select the Localize? check box on the HTML tab. See About the Localization wizard and Rules Inspector tool — Localizing forms and reports with the Field Value Inspector.

For example, if a property of type Text has hundreds of possible values from AAAAAA to ZZZZZ, you can truncate the value to the first character, to create a report with at most 26 top-level groups. Similarly, values of a DateTime property are precise to the millisecond, but you can group rows by day or month.

For the Text type, click the Details button to specify a string function that the system applies to the field before grouping. You can select a function that converts the field value to uppercase or lowercase, select a substring, or concatenate the value with another Text property value or with a literal constant.

For DateTime type, click the Details button to specify that a portion of the date is used in grouping. For example, you can specify the year only (in the format YYYY), a two-digit month code (as YYYY-MM or only MM), or the day (as DD or YYYY-MM-DD).

The Details button changes to a checkbox icon after you select a function.

• Count — Counts the number of rows for which this field is not blank.
• Count Distinct — Counts the number of distinct values of this field.
• Sum — Adds all instances of this field. Can only be used with Integer, Decimal, and Double property types.
• Average — Displays the average of this field. Can only be used with Integer, Decimal, and Double property types.
• Min — Displays the minimum of this field. Can only be used with Integer, Decimal, and Double property types.
• Max — Displays the maximum of this field. Can only be used with Integer, Decimal, and Double property types.

Leave blank to use a DateTime property with trend reporting.

Optional. The system can count instances based on the value of a DateTime property. To define trend fields, leave the Field field blank. Click Configure to complete the Trend Definition form.

If your application supports users in multiple locales, choose a noun or noun phrase for the caption of 64 characters or less, and select the Localize? check box on the HTML tab. Choose a caption already included in a language pack, to simplify localization. Click to review or create the field value rule supporting localization. The pencil icon appears only after you select the Localize? check box on the HTML tab. See About the Localization wizard and Rules Inspector tool — Localizing forms and reports with the Field Value Inspector.

Sorting follows the order of rows within this array. If this field is set to Ascending in the first row and also in the second row, values corresponding to the first row form the major sort, and values corresponding to the second row form a minor sort.

Many controls accept parameters. Click the gear icon to the right of the Control value to enter parameters for the control.

When you select Custom, the form changes. Identify on the Pages & Classes tab the class and page name of a page that can hold prompt values. Create and reference a section in that class to collect each prompt value. Use the standard control Reporting_SymbolicDates if you want to allow the user to select a symbolic date for a Date or DateTime property. You can also identify a section to hold report output and criteria values.

• No Access — No part of this row is displayed.
• Read Only — The criteria row is displayed but users cannot alter the criteria.
• All Access — The criteria displays. Users can change the Field , Condition , and Value fields.
• Value Only — The criteria displays. Users can change the Value field.

When this option is selected, at least one Criteria row must allow user input. The Prompt Mode for at least one row must not be No Access or Read Only.

Select this option if the report user is allowed to change report selection criteria. If not selected, the output for a single report might vary from user to user for no easily detected reason, because users saved different criteria.

User selections are recorded in the Value field for the current execution of the report. This check box is meaningful only when you selected Prompt user? , and one or more rows of the criteria allow users to enter values.

User selections are recorded in the Value field for the current execution of the report. This check box is meaningful only when Prompt user? is selected, and one or more rows of the criteria allow users to enter values.

User selections are recorded in the Value field for the current execution of the report. This check box is meaningful only when Prompt user? is selected, and one or more rows of the criteria allow users to enter property names.

If you implement a custom activity for unusual reporting needs, choose a name other than getContent and reference the name in this field. The custom activity can derive report contents from various means and sources, such as access to external databases through connector rules, calculations, and so on, but must place the results on the specified page and enforce the Maximum Value record count limit. A few summary view capabilities are disabled when an activity with a different name is used.

Found more than the maximum number of records (nnn)

where nnn is the Maximum Value limit. If all records are displayed, a record count displays.

Displaying nnnn records

If not selected, the message is disabled.

This option is enabled by default for new reports that you create, but disabled for reports created in versions prior to PRPC Version 5.5.

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.

Do not select this check box if the Edit In Excel option (on the Organize tab) is selected, or if your application requires processing of the embedded pages.

If this summary view uses the facilities of the Join tab, you must select this check box.

As a best practice, select this check box. This option 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. Pega Platform and application rules each have a setting:

• clipboard/lightWeightList/enableForCorePRPCRules - This setting is true by default.
• clipboard/lightWeightList/enableForCustomerRules - This setting is false by default.

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

Chose this option only if the Reports Database field is not blank and identifies a database table that is replicated from the production PegaRULES database. If the report uses JOIN operations that draw from multiple database tables, all tables must be in the same reports database.

When this option is selected, at run time the report uses data from the alternate database. Property pyUseAlternateDb is set to true on the top-level output Code-Pega-List page.

The system uses the Class and Privilege values with class inheritance to look for the privilege rule.