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.

Enhanced date circumstancing option

Valid from Pega Version 7.2

The date range and as-of date circumstancing features have been merged into a single feature called date circumstancing. Accordingly, the new Property and Date circumstancing option provides more flexibility when you circumstance a rule. For more information, see Specializing a rule.

Renaming a system creates the required data requestors

Valid from Pega Version 7.2

When you rename a system, either from the System Name landing page or by updating the prconfig.xml file, any missing data requestors are automatically created by the Pega 7 Platform. The Data Admin System Setting is also created, if it is missing.

Case Manager option for searching only attachments

Valid from Pega Version 7.2

Case Manager search now has an option to search only case attachments. When you search attachments, a new column in the search results displays a paperclip icon with the number of attachments that match the search string. You can click the number to display a list of matching attachments for the selected case.

Configure Elasticsearch index nodes to ensure availability of index files

Valid from Pega Version 7.2

You can now configure Elasticsearch index host nodes in a Pega cluster outside of the Search landing page. This change ensures that search index files are always available by eliminating the need for manual configuration on the Search landing page. Use the new index.directory=<index_directory> command-line setting during JVM startup to indicate that this node is an index host node and to specify the directory where the index files will be hosted.

In addition, offline Elasticsearch index nodes can now be removed by using a new prpcUtils command-line option. For more information, see Managing Elasticsearch index host nodes outside of the Search landing page.

New Schema Tools and Query Inspector landing pages for Pega Cloud

Valid from Pega Version 7.2

Two landing pages have been added for advanced database administration tasks for Pega Cloud customers who use a Pega-hosted instance. These landing pages minimize the operations that need to be performed outside of the Pega 7 Platform. They are available only for customers who use a Postgres database.

From the new Schema Tools landing page, you can view PegaRULES and PegaDATA database schemas, increase the size of a column, add a composite or function index, update database statistics for a table, and defragment a table.

From the new Query Inspector landing page, you can enter an SQL query and generate an explain plan.

To use these landing pages, you must have the new PegaRULES:DatabaseAdministrator role. You access the landing pages by clicking Designer Studio > System > Database > Schema Tools or by clicking Designer Studio > System > Database > Query Inspector. The individual features that you can access are determined by the privileges that are assigned to you.

For more information, see Schema Tools and Query Inspector landing pages for tuning and maintaining databases in the Pega Cloud.

Custom properties can be passed to an Oracle database

Valid from Pega Version 7.2

You can pass a customizable set of property values to an Oracle database when a connection is established so that an SQL statement can be run. This feature provides the ability to implement object-level security for data access from a Pega 7 Platform application by defining Virtual Private Databases (VPDs) on class tables that reference the information passed. For example, you could pass in an operator's branch office into the context of every query run against the Oracle database to ensure that the operator has access only to data that is applicable to the operator's branch.

This feature is available only for Oracle databases and for a Data-Admin-DB-Name instance that is not PegaRULES or PegaDATA, and has the same connection metadata (JNDI, URL) as PegaData.

See Passing custom properties to an Oracle database.

The Declarative Network display is now cross-browser compatible

Valid from Pega Version 7.2

The Declarative Network display can now be displayed on all browsers.

Accessibility improvements

Valid from Pega Version 7.2

Several improvements are now available that enable application accessibility. These improvements affect the wait indicator, overlays, and collapsible layouts.

The wait indicator, or throbber, announces its status to an assistive technology such as JAWS.

  • When loading, the throbber announces “Loading content” or other text that can be edited in the pyThrobberLoadingText property.
  • When loading is completed, the throbber announces “Loading completed” or other text that can be edited in the pyThrobberLoadingCompletedText property.
  • The loading announcement is set by default to a three-second delay, which can be modified in the pyThrobberAnnouncementDelay property.

Overlays are announced by an assistive technology and overlay content can be tabbed through by using the Tab key without closing the overlay. Overlays can be closed by pressing the Esc key. This behavior applies to all overlays and modal dialog boxes that are opened as local actions and popovers that are part of the autogenerated UI.

All users, including those not using an assistive technology, can focus the expand and collapse feature of a layout by using the Tab key. The expanded or collapsed state is announced by screen readers.

Date control for past and future years

Valid from Pega Version 7.2

The Date control can be configured to show only past dates, only future dates, or any date range that includes the current year. The Display range can be set to include a configurable range of previous years or next years. The number of years is relative to the user’s date.

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