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.

Add the security checklist to applications created before 7.3.1

Valid from Pega Version 7.3.1

The security checklist is now automatically added to applications. You can manually add the security checklist to applications that were created in earlier versions.

You can improve the security of your application by completing the tasks on the checklist.

The following task reflects the procedure on how to manually add the security checklists to Designer Studio prior to 7.3.1:

  1. In the header of Designer Studio, click the name of the application, and then click Definition.
  2. Click the Documentation tab.
  3. In the Application guides section, click Add guide.
  4. In the Application guide& field, enter pxApplicationSecurityChecklist.
  5. Click the Configure icon in the Available in column and select the portals (App Studio and Dev Studio) that you want to add the security checklist to.
  6. Click Save.

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.

Deprecated rule types

Valid from Pega Version 7.1.8

The following rule types have been deprecated as of the Pega 7.1.8 release:

  • Form
  • Hierarchy
  • Service COM
  • Service BPEL
  • Connect BPEL
  • Parse Transform
  • Parse Transform Collection
  • Parse Infer

For more information, including suggested alternate rule types, see the help topic Deprecated features.

Configuration required for data operations on external schema when using a Postgres database

Valid from Pega Version 7.1.8

When you use the API for data operations on external schema in the Postgres database, you must update the prconfig.xml file. No other platform requires a prconfig.xml update.

To update the prconfig.xml file:

  1. Stop the server and add the following entry to the prconfig.xml file:
    env name="database/databases/postgres_ext/defaultSchema"
    value="externalschema"
    where postgres_ext is the external database that uses the external schema “externalschema”.
  2. Restart the server.

End of support for Netscape Plugin API in Google Chrome 45

Valid from Pega Version 7.1.8

Beginning with Chrome 45, which is expected to be available in September 2015, Google is ending support for browser plug-ins that rely on the Netscape Plugin API (NPAPI) architecture. These plug-ins include Microsoft Silverlight, Adobe Flash Player, and Java.

The Pega 7 Platform includes several optional features that use these plug-ins. For a detailed overview of these features, see Client-side technologies.

Locatable pages are deprecated

Valid from Pega Version 7.3.1

Locatable pages are deprecated. Use a data page instead. Data pages provide improved performance. When you save a rule that has a Locate Page Activity or when you create an activity of type Locate page, a guardrail warning is displayed indicating that this feature has been deprecated.

For information about data pages, see Data pages.

Rules Assembly cache is deprecated

Valid from Pega Version 7.3.1

Rules Assembly (RA) cache and custom settings for its corresponding fua/assemblyCacheModeprconfig.xml file setting are deprecated because they are obsolete. A warning is logged at startup if a custom (non-default) value is specified for fua/assemblyCacheMode in the prconfig.xml file. The functional behavior of the system is not affected.

Use of the @java function in expressions is deprecated

Valid from Pega Version 7.3.1

Use of the @java function in expressions is deprecated. Use a utility function or other product feature instead.

For more information about expressions, see Building expressions with the Expression Builder.

Interactions in flows are no longer supported by the Run Interaction shape

Valid from Pega Version 7.3.1

The Run Interaction shape in flows has been replaced by the Run Data Flow shape, which supports running a single case data flow with a strategy. Flows that include the Run Interaction shape continue to work; however, you must now use the Utility shape to reference any new interactions that you create.

For more information, see Running a decision strategy from a flow and About Interaction rules.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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