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.

Upgrades and updates from Pega 7.3 on MSSQL fail with column name mismatch

Valid from Pega Version 7.3

This failure applies only to upgrades and updates from Pega® Platform 7.3 on systems running Microsoft® SQL Server®. In Pega 7.3, the capitalization for the column name pc_work_agile.pzPvStream is incorrect. The correct capitalization is pzPVStream. To prevent upgrade and update failures, before you upgrade or update, run the following command from the Microsoft SQL Server Management Studio (SSMS) to rename the column:

EXEC sp_rename ‘data-schema-name.pc_work_agile.pzPvStream', 'pzPVStream', 'COLUMN'

Reports on pc_work_agile table fail in Pega 7.3 on MSSQL

Valid from Pega Version 7.3

This failure applies only to Pega® Platform 7.3 on systems running Microsoft SQL Server. In Pega 7.3, the capitalization for the column name pc_work_agile.pzPvStream is incorrect. The correct capitalization is pzPVStream. To prevent reporting failures on the pc_work_agile table, run the following command from the Microsoft SQL Server Management Studio (SSMS) to rename the column after you install Pega 7.3:

EXEC sp_rename ‘data-schema-name.pc_work_agile.pzPvStream', 'pzPVStream', 'COLUMN'

Nodes in a cluster do not see each other for Docker, multiple VMs, or multiple NICs setup

Valid from Pega Version 7.3

If a cluster is set up in Docker, or uses separate virtual machines (VMs) or multiple network interfaces, you must set the public address in the prconfig.xml file for each Pega® Platform node to avoid problems with node clustering. Add the <env name=”identification/cluster/public/address” value=”IP address”/> setting to specify the public address that is used by each node.

Security fields in JFrog Artifactory repository do not work

Valid from Pega Version 7.3

The fields in the Security section of the JFrog Artifactory repository rule form, including the Secure protocol field, the Truststore field, and the Keystore field, were not implemented. In the Pega™ Platform 7.3 Designer Studio help, disregard the optional Security section in step 4 of the Configuring a JFrog Artifactory or Amazon S3 repository connection help topic, and disregard the optional Security section in step 5 of the Creating a repository configuration help topic in the 7.3.1 Designer Studio help.

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