Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Custom shortcuts for mobile apps

Valid from Pega Version 7.1.6

When using a mobile web browser to access your mobile app, you can create a shortcut to a specific URL by selecting "add to home screen" from your web browser's menu when on the page. The shortcut icon displays showing the Pega 7 mobile app icon by default, but the icon can be customized in Designer Studio. When you tap the icon, the mobile device's default web browser opens directly to the saved URL. 

See Using the Pega 7 mobile app.

Application Express and the Content Security Policy

Valid from Pega Version 7.1.7

Application Express copies (if defined) the Content Security Policy (CSP) name (pyContentSecurityPolicyName) from the built-on application in a new application. It also sets the CSP mode (pyContentSecurityPolicyMode) to report. The values appear in the Content Security area on the application rule's Integration & Security tab.

When checking an application in the DCO Compatibility tool, a warning appears if the CSP name is missing.

Remove frames for single document dynamic containers

Valid from Pega Version 7.1.6

New single document dynamic containers are created with iFrame mode disabled by
default. Legacy iFrame mode is still available, but must be enabled by clicking
the Use Legacy iFrame mode check box.

API enhancements to Manage Recents list

Valid from Pega Version 7.1.6

The existing Recent(s) API has been enhanced to provide the following rules:

  • pzClearRecentItem: Clears a specific item
  • pzClearAllRecentItems: Clears all recent items

Specifying read-only formatting

Valid from Pega Version 7.1.6

Read-only fields may be marked as an email, URL, or phone number in the Read-Only Format
settings.

Sort and filter columns with section includes

Valid from Pega Version 7.1.6

Column Properties include the ability to sort and filter columns that contain a section includes. A property for sorting and filtering may be specified in the Sort/filter property field. A date format for date or date-time properties can be configured to display in the filter popup.

Align column heading with column data

Valid from Pega Version 7.1.6

When the Align column heading with column data check box is checked, column headings are aligned with the data. When unchecked, the header may be aligned to the left, right or middle.

Geolocation tracking requires browser permission

Valid from Pega Version 7.1.6

When the geolocation tracking feature is enabled, a Map it link appears next to each requestor entry in the audit trail. When you click a link for the first time, the browser displays a notification asking whether you want to permit tracking. Make your yes/no selection in the prompt. Do not click "X" to close it, as doing so may render the session unresponsive. Refresh the browser if necessary and make your selection.

DB2-LUW database logfile size increase

Valid from Pega Version 7.1.5

This issue applies to DB2-LUW database platforms only.
 

To avoid running out of logfile space due to large transaction sets during the rule base load of a Pega 7.1.x install, upgrade, or maintenance level update, systems supported by a DB2-LUW database platform should increase the LOGFILSIZ parameter to at least 4096 pages from the default size of 1000 pages.

After the size has been increased, restart the database to ensure that the new setting is loaded into the database correctly.

Unable to drop triggers for frameworks with custom rule tables

Valid from Pega Version Pega Platform

For PostgreSQL and z/OS systems, if your deployment includes a framework or application with custom rule tables (such as CPM or any applcation built on CPM), upgrading to Pega 7.1.x causes the DDL application to fail when it tries to drop the following stored procedures:

  • z/OS
    • SPPR_RULE_VW_UPDATE
    • PRPC_UPDATESCACHE
  • PostgreSQL
    • sppr_base_uc_del.sql
    • sppr_base_uc_ins.sql
    • sppr_base_uc_upd.sql
    • sppr4_fv_ins
    • sppr4_fv_upd

During an upgrade, a number of stored procedures must be dropped and re-added. If the framework or application has custom dependencies that call the stored procedure, this problem is likely to occur.

To correct this issue, drop the framework’s custom dependencies before upgrading and add back the dependencies following the upgrade.

For instructions about how to drop and add the dependencies for your framework and database when this problem occurs, see Troubleshooting: PRPC 7.1.6 upgrade does not drop PRPC_UPDATESCACHE stored procedure.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us