Report Definitions
Completing the Query tab

Specify a Single Value property, which may be a top-level or embedded scalar property, identified by a property reference.

Instead of an existing single value, you can use the Calculation Builder to select a function template and provide database columns for it to operate on. The column in the report displays the result of the SQL function.

If your application has declare index rules, you can choose one of the properties in the declare index as a column. Type part of the declare index name and click the down-arrow. The rule appears as one of the Best Bets.

When using a Report Definition to query the search index, you may need to modify the list of filterable and returnable properties for that class. See How class instances are stored in the search index and Specifying custom search properties.

If you enter the name of property that has not been optimized, your system might experience a performance slowdown when running the report. You might want to use unoptimized properties while working out the report's structure and contents, but optimize all properties before moving the code to a production system.

In many situations, you can use a linked property to populate a column (or the right side of a filter condition; see below). If you are building a report on unresolved work items, you can include a column with the access group of the creator of the work item by using the linked property .pxCreateOperator.pyAccessGroup.

You cannot reference data page properties that take parameters (such as D_page1[companyName:D_page2[param2:Param.P1],param2:pxRequestor.pyUserIdentifier].pyLabel). Although, you can directly reference properties in a data page (such as D_page1.companyName).

Enter a column heading to be used for this column on the report. By default, the label defined for the selected property appears as the column heading.

This field is required for most columns, but is not required when the Summary function field has a value.

Optional. For each sorted column, you specify one of the following options:

• Ascending (default): Values for the column are sorted in ascending order, from lowest to highest.
• Descending: Values for the column are sorted in descending order, from highest to lowest.

Specify a letter (or letters) that uniquely identifies this row. This condition is used to reference this row in the Logic field, and can be as simple as A for the first row, B for the second row, and so on. Conditions can have letters and numbers, but no spaces, and you cannot use the words "And" or "Or", as they are used to relate the various filters.

Optional: Provide a caption to identify the filter condition in the Filters list that displays above the data when the report runs.

Depending on which option you selected for Filter caption settings at the bottom of the section, the caption you set for each condition applies to the column within the condition (if the caption is "customer", then "customer = 'brown'"), or to the entire condition ("customer").

Specify a property reference for the conditions. The property referenced must be exposed as a database column in the Applies To class for the report value, or else be a fully qualified value to a clipboard page that is always present on the clipboard, such as the requestor page or process page.

Caution: You can specify only Single Value properties that are either top-level or scalar embedded properties in the Column field. Each property you identify for selection criteria must be exposed as a column in the database table.

You can specify single value properties that are produced by an SQL function. To use the result of an SQL function query, click the Calculation Builder icon to the right of the field. The Calculation Builder opens, and you can select an SQL function and specify parameters.

Note: If the type of this property is TextEncrypted, special instructions apply to the Condition and Value fields.

If you enter .pxObjClass and the Applies To class of this report definition is a framework class, and if the developer has checked the Report on descendant class instances check box in the Report Definition form, 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 report definition into the implementation class.

When you specify an embedded property in a page list or page group, you must enter an index or name for each page list or age group; for example, pyproductList(1).pyProdName. However, this index is ignored at run time, which results in an ANY-type filter being generated that is satisfied if any value in the page list or page group satisfies the condition.

Specify one of the following options as a comparison value:

• A literal constant, formatted in accordance with the property type. To compare the Column value with multiple literal constants, surround each with quotation marks and separate each with a comma. Place a backslash character \ before any quotation mark that appears within the constant. In some situations, you can click the Select values button to review current clipboard values for the property identified in the Column 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 Column 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 Column field. To compare the Column value with multiple Value List or Value Group properties, separate each property name with a comma.
• A reference to a parameter that is defined in the report's rule, in the format param.name.
• The name of another Single Value property that is exposed as a column. This allows comparison of the values of two properties in the same instance (database row), if the types are identical or comparable.
• A calculation. To compare with the result of a calculation, click the Calculation Builder icon to the right of the field. The Calculation Builder opens, and you can select an SQL function and specify parameters.
• A symbolic date, for a Date or DateTime value. When the list value rule executes, 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 Relationship 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 run time if the value of the Column field equals (or is greater than, or is contained in, and so on) any one of the entries.

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 Column 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 window

The Select values window provides one or more of the following tabs:

• Available values — The system searches the column in the database corresponding to the property in the Column field to collect and display up to 1,000 values for the Column property in a new window. To add literal values to the Value field, check one or more boxes and click  OK. (You can also type literal constants directly, whether or not they appear on this list.) This tab appears at run time only to users who hold the standard privilege @baseclass.ShowStoredValues. For such users, it is visible at run time when the Display available values? box in the Prompt settings area is selected.
• Valid values — The system presents values determined by the Table type specification on the General tab of the property referenced in the Column field. To add literal values to the Value field, check one or more boxes and click  Apply . This tab appears at run time when the Display valid values? box in the Prompt settings area is selected.
• Compatible columns — The system lists exposed properties with the same Type as the property in the Column field, as candidates for this field. This tab appears 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.
• Calendar — Allows selection of a date by using a calendar interface.

Select a value to determine how a user of this report can modify the condition in this row when the report is run and displayed in the Report Viewer.

• Allow any changes- This is the default. The condition appears in the Filtered by link of the report, and in the Report Editor the Change Logic button is displayed. The user can change any column, relationship, or value in the filter.
• Allow changes to values only - The condition appears in the Filtered by link of the report, and in the Report Editor the View Logic button is displayed. The user can change only the Value field within the condition.
• Read only, allow no changes - The condition appears in the Filtered by link of the report, and in the Report Editor the View Logic button is displayed. The filter cannot be changed by users.
• Filter not visible in Viewer - The condition is not displayed in the Filtered by link of the report, and a button is not displayed in the Report Editor. The filter cannot be changed by users.

This option is important only when there is no value at run time specified in the Value field. By default, when the Value field is empty at run time, the criteria defined by this row is ignored, and processing is the same as if this row is not present.

For example, assume the criteria is that the customer's last name starts with a given letter, and the value set in the Value field is param.Letter. If this report runs at a time 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 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.

In situations where this default behavior is not desirable, 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 the above example, the criteria is transformed to "Lastname is null" — which is different from having no restriction on Lastname.

Select this option to have run time comparisons of the Field value and the Value value be case-insensitive. For example, "Smith" matches "SMITH" and also matches "sMiTH".

If selected, at run time "a" matches "A" and is less than "B".

When you do not select this option, tests of the Field value and the Value value occur without case conversion. In this case, "a" is greater than both "A" and also greater than "B".

Caution: In most cases, do not select this option. Select this box only when necessary to obtain the rows of the report:

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

For report definitions that are defined on the Rule- class, or a class derived from Rule-, select this check box to restrict the rule instances included to those that satisfy the rule resolution procedures. Circumstancing is ignored.

For report definitions that are defined on the Rule-class, or a class derived from Rule-, select this check box to restrict report coverage to those in a certain application context. When you select this check box, additional fields are available so that you can set application context filters:

When using the application context filtering option, you can add and sort report results by the values in a hidden column like pyRulesetVersion.