Published Release Notes

Apply logic to data import fields

When importing data from an external system, you can translate data fields into values that can be read by Pega^® Platform. From the Import wizard, you can do the following actions:

• Apply a decision tree or decision table to the data that is imported for a field.
• Use imported data for a field to look up a value in another record. For example, you can look up the key of a record that uses an external identifier to populate a foreign key field.
• Create templates that contain business logic, which eliminates the need to handle data transformations manually during preprocessing.

For more information, see Transforming data during import.

The Scratch Pad tool is no longer available

The Scratch Pad tool is no longer available. To add properties to a report from an end user portal, use the Data Explorer. The Data Explorer provides an efficient way to find a property or calculation to include as a column in a report.

For more information, see Data Explorer.

Ability to map JSON to clipboard properties by using a data transform

You can now map the entire JSON file or individual properties to and from the clipboard by using a data transform. Using a data transform makes it faster and easier to connect your Pega^® Platform to your system of record.

For more information, see Data transforms.

Data validation before importing

Data imported into a data type is now validated before it is imported. Validating data before importing it ensures that the data is valid and reduces the amount of time required to manually analyze and validate your data.

For more information about importing data into a data type, see Importing data for a data type.

Enable different REST service rules for distinct resource URIs

You can now specify different service REST rules for distinct resource URIs. This functionality provides different processing options, request handling, and response handling for each distinct resource URI. Additionally, it eliminates the need to develop and maintain complex logic to handle all possible resource URI paths.

For more information, see Distinct URI specification for service REST rules.

Custom scaling on x-axis for bubble charts

Bubble charts now support custom scaling for the x-axis as well as the y-axis. For example, you can now configure a fixed range for the x-axis.

For information about including a chart in a report, see Adding or editing charts from the Report Definition rule form.

Enable users to save charts as .png files

You can now enable users to save a report chart as a .png file. On the Chart tab of the Report Definition rule form, click General settings and select the Export chart to image check box. When you select this option, users are provided with the Save as image option, which they can use to save an image of the chart to include in a Word document or email.

For information about including a chart in a report, see Adding or editing charts from the Report Definition rule form.

Enhancements to exporting reports to Excel

When you export report results to Microsoft Excel, the process now creates a Data sheet and an Info sheet in the Excel file. By default, the Info sheet contains the report title, filters used to generate the report, the date when the report was generated, and the number of results returned.

If you want the report title and filters to display in the first sheet instead of the Info sheet, you can disable the default functionality. For more information, see Disabling the creation of an Info sheet in Excel output.

Use fast processing option does not work

The Use fast processing option on Connect REST and Service REST rule forms does not work unless you obtain the HFix-43000 hotfix from Global Customer Service.

Use the following data model guidelines when using fast processing:

• The JSON property names and the clipboard property names must match.
• The JSON tree structure and the clipboard tree structure must be similar.
• The scalar arrays in JSON must be mapped to the clipboard as page lists.
• Multi-dimensional arrays must be mapped into page lists of page lists with the same embedded property names.

​In addition, page groups, value groups, and Java objects are not supported by fast processing.

Behavior changes when reporting on descendant classes

Report Definitions that use the Report on descendant class instances option with the Include all descendant classes option apply only to the Applies to Class. Join classes are not included as they were in previous Pega^® Platform versions. The following example shows what happens for each possible scenario for Report on descendant class instances when the report is defined on ClassA with a class join with Work-.

• If Report on descendant class instances is disabled, the report runs against ClassA and the join happens with Work-. The behavior is the same in Pega 7.3.1 as it is in previous Pega Platform versions.
• If Report on descendant class instances is enabled, and Include single implementation class is selected, the report runs against ClassA and the join happens with the MySampleClass implementation class. The behavior is the same in Pega 7.3.1 as it is in previous Pega Platform versions.
• If Report on descendant class instances is enabled, and Include all descendant classes is selected, the report runs against ClassA and its descendants and the join happens with Work-. In previous Pega Platform versions, the join happened with the MySampleClass implementation class.