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.

Data schema error on z/OS split schema upgrades from versions before Pega 7.1.8

Valid from Pega Version 4.1

When upgrading to a split schema on Pega 7.x with IBM DB2 for z/OS, you see an error during the data schema upgrade when the system tries to drop the PRPC_Updatescache procedure. Because triggers on rules tables use PRPC_Updatescache, you must use the ZOSDisableTriggerScripts to disable these triggers before you update the data schema.

  1. Follow the instructions in the Pega 7 Platform Upgrade Guide to upgrade the rules schema, but stop immediately before you upgrade the data schema with the upgrade.bat or upgrade.sh script. The Pega 7 Platform Upgrade Guide is on the Support > Deployment Guides page.
  2. Copy the contents of the <distribution>\ResourceKit\ZOSDisableTriggerScripts directory into the <distribution>\scripts\ directory.
  3. Run fixZosTriggers.bat or fixZosTriggers.sh with the following arguments:
    --action preupgrade
    --dataschema <data schema name>
    --oldrulesschema <old rules schema name. If you are upgrading from a single-schema system, this is the data schema name.>
    --newrulesschema <new rules schema name>
    --automaticddl <Optional. Set to true to automatically apply the disable trigger SQL scripts.>

    For example:
    fixZosTriggers --action preupgrade --dataschema pegadata --oldrulesschema pegarules --newrulesschema newrules --automaticddl false

  4. If you did not set --automaticddl to true in the previous step, run the <distribution>\schema/disable.sql script to manually disable the trigger SQL scripts.
  5. Run the data schema upgrade as described in the Pega 7 Platform Upgrade Guide.

Derby databases are no longer supported

Valid from Pega Version 7.1.8

Previously, an embedded Derby database could be used as a file system. This setup was configured by setting storage/class/<<filesystem>>/type to "embedded" in the prconfig file.

After upgrading, storage types that are specified as "embedded" now default to the local file system.

Custom database (DB) triggers are dropped during upgrade

Valid from Pega Version 7.1.8

The latest version of Pega 7 improves performance by no longer using database triggers to assist with System Pulse and Data-Rule-Summary processing, which is now done within the Pega 7 engine. As a result, DB triggers are no longer installed on either the pr_sys_updatescache or pr4_rule_vw tables.

When upgrading to the latest version of Pega 7, if you had previously implemented a custom database (DB) trigger on these tables, or a custom DB trigger that refers to these tables, it is removed during the upgrade process. No custom triggers are removed unless they reference these tables.

If you have custom DB triggers that reference the pr_sys_updatescache or pr4_rule_vw tables and perform other processing, those triggers must be reimplemented. When doing so, you must be careful to not modify the pr_sys_updatescache or pr4_rule_vw tables.

For more information, see Startup check removes custom DB triggers.

Convert data instances into decision parameter rules

Valid from Pega Version 7.1.8

The Convert groups wizard is available in the Hierarchy landing page when the list of your propositions include decision data records.

Click Convert groups at the top of the landing page to use the wizard and to convert data instances into decision parameter rules. This conversion is necessary to make the existing proposition data instances available for revision management.

Update to the Data Flows rule

Valid from Pega Version 7.1.8

It is now possible to collect statistics for each active data flow. These include the number of processed records, records that caused errors and last processed records per shape, as well as historical throughput measured for the entire data flow.

There are two new patterns in the Data Flow rule:

  • Event Strategy - define this pattern to use an event strategy in a data flow and to connect a data stream and static data sources to an event strategy.
  • Filter - specify filter conditions and apply them to each element of the input flow 

Apart from this, the Merge pattern was updated to execute the flow when there is no data on the secondary branches and the Strategy pattern allows you to specify the class where you want to store your strategy results.

New Dynamic System Setting for proposition management

Valid from Pega Version 7.1.8

A new Dynamic System Setting affects the process of creating new groups on the Proposition Management landing page.

When the PropositionManagement/isOnlyVersionedProposition parameter is set to true, users can only create the versioned propositions.

When the PropositionManagement/isOnlyVersionedProposition parameter is set to false, the Create Group dialog allows users to create either the versioned or unversioned propositions (the Create versioned proposition data check box and the Decision data rule section are both displayed).

Identify, install, and manage hotfixes with the Hotfix Manager

Valid from Pega Version 7.1.8

Hotfixes are packages of files that address issues in Pega 7 and in participating Industry Applications. With Hotfix Manager, you can:

  • Scan your system for installed and missing critical hotfixes and create a report that you can provide to Pegasystems Support for diagnostic purposes.
  • Review the descriptions and contents of hotfixes.
  • Install, rollback, and commit hotfixes.
  • Manage hotfixes that include schema changes or require other special handling.

The Hotfix Manager replaces the Update Manager Hotfix Installer and System Scanner, both of which are deprecated. For more information, see Hotfix Manager identifies, installs, and manages hotfixes to Pega 7 and participating Industry Applications.

New form of the HBase rule

Valid from Pega Version 7.1.8

There is a new form of the HBase rule. While you cannot create any new instances of the Pega 7.1.7 HBase rule, legacy instances in your application remain functional. You can still use the Pega 7.1.7 instances of the HBase rule, but you cannot make changes to them.

Enhanced product rule form for easy application packaging

Valid from Pega Version 7.1.8

The enhanced product rule form allows you to add applications in Delta mode, which includes only the patch version of the rulesets that comprise the application rule. You can also use Global exclusions to exclude one or more rules that are not associated with a ruleset version.

These enhancements allow easy packaging of non-versioned rules that are often deployed separately and reduce the need to manually add them later.

For more information, see Product rules - Completing the Contents tab.

New data sets

Valid from Pega Version 7.1.8

There are three new types of data sets:

  • HDFS Data Set, which reads and saves data from external, distributed Apache Hadoop file systems.
  • HBase Data Set, which supports HBase storage.
  • Stream Data Set, which processes the continuous data stream of events.

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