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.

Service Portlet rules are deprecated

Valid from Pega Version 8.2

Service Portlet rules are deprecated. Existing rules will continue to work, but you cannot create new ones. Use Pega Web Mashup instead. In addition, some changes might impact functionality. If you are using Portlet rules and plan to upgrade, contact your customer service representative.

For more information about Pega Web Mashup, see About Pega Web Mashup.

Deprecated metadata types in the Connector and Metadata wizard

Valid from Pega Version 8.2

The WSDL, SAP WSDL, and DTD metadata types have been deprecated in the Connector and Metadata wizard. For WSDL, use SOAP integration, and for DTD, use XSD.

For more information about SOAP connectors, see About Connect SOAP rules. For more information about XSD, see About the Connector and Metadata wizard.

Deprecated support for passing symbolic index as strings to value lists and page lists

Valid from Pega Version 8.2

Starting with the next release after Pega Platform™ 8.2, passing symbolic indexes as strings in parameters, properties, and string literals to both value lists and page lists will no longer be supported. The following examples show the syntax that still works in Pega 8.2, that will not work in the next release:

myPageList("<LAST>")

and

param.str = "<LAST>"
myPageList(param.str)

The following example shows syntax that currently is not supported and gives a validation error. This syntax will also not work in future releases.

param.str = <LAST>
myPageList(param.str)

To avoid issues after upgrading to Pega 8.3, refactor all occurrences of this syntax in your code. For instructions on how to find occurrences of this syntax in your code, see Refactoring unsupported symbolic index syntax for value lists and page lists.

For more information about the correct use of symbolic indexes, see Symbolic indexes – APPEND, CURRENT, INSERT, LAST, and PREPEND.

Changes in JSON results when checking the health of your system

Valid from Pega Version 8.2

Beginning with Pega Platform™ 8.2, the JSON results that are returned when you ping a Pega Platform instance have changed. JSON results now include node type and health information, including test name, status, state, and node ID. The following samples show JSON results from versions before 8.2 and as of 8.2.

JSON results for pre-Pega Platform 8.2:

{ "duration":"3954.448601", "count":"0" }

JSON results for Pega Platform 8.2 and later:

{"node_type":["WebUser"],"health":[{"last_reported_time":"2019-02-14T16:10:49.589Z","test_name":"Sample-Stream-Check","status":"success"}],"state":"healthy","node_id":"10.10.10_samplenode"}.

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