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.

Simplified section property panels in Pega Express

Valid from Pega Version 7.3

When you edit sections in Pega Express, the sections display a simplified properties panel. This panel presents the essential section properties in an intuitive way to streamline the editing process. To access this properties panel in Pega Express, click the Pencil icon next to an editable object. For more information, see Runtime editing of sections in Pega Express.

Full support for Unicode characters in Pega Express

Valid from Pega Version 7.3

Pega® Express now supports Unicode characters when you name properties, case types, and data types. Languages that use multibyte characters, such as Japanese and Hindi, are now fully supported. An administrator can enable Unicode support for Pega Express by configuring a Dynamic System Setting in Designer Studio.

For more information, see Enabling Unicode character support for object names.

Edit sections across Pega Express and Designer Studio

Valid from Pega Version 7.3

Sections created in Pega® Express can be edited in Designer Studio, saved, and then reopened in Pega Express. This allows developers to create more complex, feature-rich sections and make them accessible to Pega Express users. In the section rule, you can convert template-based sections to full sections that no longer use a template.

For more information, see Harness and Section forms - Adding a section.

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'

Support for following users in the Pega Express and Case Manager portals

Valid from Pega Version 7.3

You can now follow users in both the Pega Express and Case Manager portals. Posts that are made by users whom you are following are displayed in your Pulse activity feed in your dashboard. In addition, an icon indicates whether followed users are online.

For more information, see the following help topics:

Use Kafka data sets in Pega Decision Strategy Manager

Valid from Pega Version 7.3

You can create Kafka data set rules to connect to an external Apache Kafka server cluster and use this data set in decision management for processing real-time streaming data. Integrating Kafka data sets into complex event processing (CEP) as part of Event Strategy rules provides a fault-tolerant and scalable solution for processing real-time data feeds.

For more information, see Kafka data sets in decision management.

PEGA0055 alert detects clock drift in a multi-node clustered environment

Valid from Pega Version 7.1.8

Clocks in most of the hardware platforms run at different rates, and the PEGA0055 alert detects the clock drift on any of the nodes in a multi-node cluster. The alert is triggered when the clock drifts from the average time of the clocks in the cluster by an amount that exceeds the time threshold configured in the prconfig.xml file. You can use a network time protocol service or daemon to correct the clocks by referring to a standard external Internet time service, for example, nist.gov.

For more information, see PEGA0055 alert: Clock drift exceeded the configured time threshold.

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'

PEGA0056 alert monitors PR_SYS_LOCKS defragmentation performance

Valid from Pega Version 7.1.8

The System-Locks class contains information about locks, and the PR_SYS_LOCKS table can now be periodically de-fragmented. Accordingly, any increase in the time taken to defragment the table associated with this class results in an increase in the time taken by a requestor to acquire or release a lock.

The PEGA0056 alert indicates that the defragmentation exceeds the time threshold that is configured in the prconfig.xml file. When the alert is triggered, you can modify the defragmentation interval or disable defragmentation.

For more information, see PEGA0056 alert: Defragmentation of the table associated with class System-Locks exceeded the configured time threshold.

Improved data security for BIX extracts for Pega Cloud customers

Valid from Pega Version 7.3

Data security is improved for BIX extracts in the Pega Cloud. BIX extracts are now processed through the use of a HIPAA-compliant system. As a result of this improvement, the method for obtaining BIX extracts has changed. For more information, see Process for obtaining BIX extracts has changed for Pega Cloud customers.

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