Published Release Notes

Ability to annotate case attachments

Pega^® Platform application users can now add annotations to images that are attached to cases. For example, users can draw around an area of an image to highlight a faulty element of the device. Users can annotate all images, except for signature images or attachments that are stored in Pega Cloud or other external data stores. The annotated case attachments replace the original ones.

For more information, see Case attachment annotations.

New application document types capture features and user stories

Pega® Platform adds two new application document types based on features and stories:

• Use product overview documents to socialize the application development plan and progress.
• Use gap analysis documents to identify the gaps between the application and your needs to clarify which customizations to build.

For more information, see Real-time agile application document types.

HBase data set type becomes resumable

HBase data set has been enhanced to be resumable. As a result, data flow runs that reference the HBase data set as their primary data source are now resumable. You can pause and resume such data flow runs.

For more information, see the Resumability of data flow runs section in Data flow run updates.

Improved Back button support in custom mobile apps for Android

In a custom mobile app for Android, you can press the Back hardware button to go back, instead of exiting the app. Custom mobile apps now function in the same way as native Android apps. For example, you can close a dialog box, dismiss an overlay, or collapse an expanded section by pressing the Back hardware button. On the home screen, pressing the Back hardware button displays a confirmation message before you can exit the app.

New data tables are non-Pega formatted

All new data tables are created as non-Pega formatted tables, that is, they do not contain a BLOB column, a pzInsKey column, or a pxObjClass column. The table's primary key will be the key that you specify, not pzInsKey. Data table construction was changed to improve performance of the Obj-Save method during batch operations, such as data imports, to make it easier to replace the table with an external system of record and to make it easier to share data among applications.

Browser unresponsive when logging in to Designer Studio

The What's new in 7.4 widget on the Designer Studio home page uses WebGL to render its background animation. If your browser is running on a virtual machine without hardware acceleration, your browser might become unresponsive because of this widget. Click the Hide this until next release button to remove the widget. At your next login, the widget will not be displayed.

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.

Applications not working as expected when using fast processing for Connect REST and Service REST integration

In Pega^® Platform 7.3.1, the Use fast processing option on Connect REST and Service REST rule forms did not work. The functionality has been fixed for Pega 7.4; however, some data model guidelines must be followed. If you use this option in Pega 7.3.1, and you did not follow the guidelines, your application might not work as expected after upgrading. 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.

Upgrading Adaptive Decision Manager data mart tables might fail

Issue: Upgrade from 7.3 to 7.3.1 fails if the data contained in the pxInsName column of the PR_DATA_DM_ADMMART_PRED_FACT table is longer than 128 characters.

Reason: During the Pega Platform™ upgrade from 7.3 to 7.3.1, data in the Adaptive Decision Manager (ADM) data mart tables is migrated from the PR_DATA_DM_ADMMART_PRED_FACT table to the PR_DATA_DM_ADMMART_MDL_FACT table. In Pega 7.3.1, ADM uses only the PR_DATA_DM_ADMMART_MDL_FACT table where the pxInsName property can store values that are 128 characters long. In Pega Platform 7.3, the pxInsName property in the PR_DATA_DM_ADMMART_PRED_FACT table can store values that are 255 characters long. If the pxInsName property contains values that are longer that 128 characters, the upgrade fails.

Resolution: Issue an ALTER TABLE statement to change the pxInsName column size to 255 characters and resume the upgrade. For example:

ALTER TABLE rules.pr_data_dm_admmart_pred ALTER COLUMN pxInsName TYPE varchar(255);

For more information, see Adaptive Decision Manager data model.