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.

Organization Setup superseded by New Application Wizard

Valid from Pega Version 7.1.3

The Organization Setup Wizard has been retired in PRPC 7.1.3.  This feature was previously launched from the Designer Studio > Org & Security > Organization > Organization Setup menu. Users are encouraged to run the New Application Wizard (also known as Application Express) instead:

NewAppWizard.jpg

This tool quickly generates an application along with all of the artifacts previously offered by the Organization Setup Wizard. This includes, but is not limited to, the class hierarchy, application rule, organization/division/unit rules, and all relevant data instances.

See the following PDN article for more details on the New Application Wizard:

Create new applications quickly and easily with Application Express

Split schema upgrade instructions missing properties

Valid from Pega Version 7.1.3

If you upgraded from 5.x, 6.x, or 7.x using the instructions in previous versions of the upgrade guide, you may have neglected to set the properties below in your migrateSystem.properties file when you migrated your upgraded schema to the source system:

 

pega.rules.objects.generate=true

pega.rules.objects.apply=true

 

If these properties were not set during an upgrade that splits the schema, your environment does not have the indexes, triggers, and primary keys on the rules tables.

 

To check for this issue, see if the pr4_base and pr4_rule rules tables in your existing rules schema are missing primary keys. If they are, use the SQL scripts in the ResourceKit\MigrationRecoveryScripts directory of the release to cleanup duplicate rules that were created due to this issue. Follow the steps below to run the scripts.

To run the scripts on Microsoft SQL, Oracle, or PostgreSLQ

  1. Take down any app servers using the affected schema.
  2. Backup your database.
  3. Replace all instances of @RULES_SCHEMA in <database>_cleanDups.sql with the name of the schema that contains the pr4_base table.
  4. Run the <database>_cleanDups.sql script on the database with vendor tools (sqlPlus, SQL Server Management Studio, etc).
  5. Replace all instances of @RULES_SCHEMA in <database>_fix_vw_table.sql with the name of the schema that contains the pr4_base table.
  6. Run the <database>_fix_vw_table.sql script on the database with vendor tools (sqlPlus, SQL Server Management Studio, etc).
  7. Generate and apply the ddl using the command line generateDDL command. Check the installation guide for your database or the upgrade guide for details about how to use the generateDDL command line script.
  8. Rebuild the indexes for the tables in your rules schema using vendor tools. This is necessary so that your system runs at an optimum speed.
  9. Optionally upgrade to the latest release, at this point your database is ready to be upgraded or used depending on your needs.

      

To run the scripts on DB2 for LUW or z/OS

  1. Take down any app servers using the affected schema.
  2. Backup your database.
  3. Run the <database>_cleanDups.sql script on the database with vendor tools (UDB CLP, Data Studio, etc) to create the CLEANSE_RULES_DUPS stored procedure.
  4. Run the query Call CLEANSE_RULES_DUPS(‘<rulesSchema>’); where <rulesSchema> is the name of schema that contains the pr4_base table.
  5. After the previous step is complete drop the CLEANSE_RULES_DUPS procedure.
  6. Replace all instances of @RULES_SCHEMA in <database>_fix_vw_table.sql with the name of the schema that contains the pr4_base table.
  7. Run the <database>_fix_vw_table.sql script on the database with vendor tools (UDB CLP, Data Studio, etc).
  8. Generate and apply the ddl using the command line generateDDL command. Check the installation guide for your database or the upgrade guide for details about how to use the generateDDL command line script.
  9. Rebuild the indexes for the tables in your rules schema using vendor tools. This is necessary so that your system runs at an optimum speed.
  10. Optionally upgrade to the latest release. At this point your database is ready to be upgraded or used depending on your needs.

Updated Word merge support with Microsoft Silverlight plug-in

Valid from Pega Version 7.1.3

Starting in this release, Pega 7 features that integrate with the Word merge capability are now cross-browser. ActiveX controls (which are only compatible with Internet Explorer) have been replaced with Microsoft Silverlight. This plug-in must be downloaded separately from Microsoft because it is not shipped with Pega 7.

Common features that are affected by this change include the Specification form and Case Type landing page.

Prior to using these features, see the release note Word merge support with Microsoft Silverlight plug-in for more information about setting up their client systems.

Performance improvement to BLOB support in Postgres databases

Valid from Pega Version 7.2.2

New tables that contain BLOB columns now use external storage instead of expanded storage for Postgres databases. This improvement applies to tables that are created during installation, upgrade, or during DDL and schema generation. Using external storage improves database performance.

For more information, see BLOB storage in Postgres databases.

Automatically manage nodes in a System Management Application cluster

Valid from Pega Version 7.2.2

Instead of manually adding and deleting nodes in a cluster by using the System Management Application (SMA), you can now automatically manage nodes. You can enable Auto Node Discovery and configure it to get information about all the nodes in a cluster, add new nodes, and update the node list.

For more information, see Managing nodes automatically in a System Management Application cluster.

Run advanced agents on only one node in a cluster

Valid from Pega Version 7.2.2

You can now configure an advanced agent to run on only one node in a cluster at a specified time. In addition, you can specify the time interval within which an advanced agent runs on only one node in the cluster, which avoids having two advanced agents starting to run on the same node at the same time.

For more information, see Improved control for running advanced agents and Agents rules – Completing the Schedule tab.

Ability to test SELECT statements

Valid from Pega Version 7.2.2

When developing and debugging applications, you can test SELECT statements from the Query Runner landing page. You can run queries against non-BLOB columns in your database and view the results on the landing page or export the results to an Excel spreadsheet or PDF file. This functionality is available for Pega Cloud customers who use a Postgres database or for customers using an Oracle database on-premises or on the cloud.

To use this landing page, you must have the PegaRULES:DatabaseAdministrator role or the pxDBSelectQuery privilege in Data- and Rule- in your access group. You access the landing page by clicking Designer Studio > System > Database > Query runner.

For more information, see Query Runner landing page for testing SELECT statements.

Elasticsearch 2.4.0 upgrade

Valid from Pega Version 7.2.2

The Pega 7 Platform has been updated to use Elasticsearch 2.4.0. You do not have to reindex immediately. You can reindex at your convenience by using the FullTextindexer utility, which provides a smoother transition to the next Elasticsearch library upgrade.

Rolling upgrades are not supported. Instead, after the upgrade has been completed, shut down all the nodes in the cluster, and then restart them beginning with the indexing nodes. For more information, see the Pega 7 Platform Upgrade Guide on the Deployment Guides landing page.

Performance enhancements to StringBuilderFactory pooling

Valid from Pega Version 7.2.2

StringBuilderFactory has been enhanced to eliminate most scenarios where errors in calling application logic can accidentally cause StringBuilder data contamination within and across JVM thread boundaries. StringBuilderFactory pooling is now thread-specific, which prevents errors in one thread’s use of StringBuilder from contaminating StringBuilder objects in other threads. Debug messages were also added to help diagnose potential problems.

Roll back system changes by using restore points

Valid from Pega Version 7.2.2

Restore points save the state of your system, including all rule and data instances. You can roll back to this restore point later if there is a problem. The Pega 7 Platform automatically creates restore points before any archive import. You can also use the prpcServiceUtils command-line tool to create and manage restore points and to roll back changes to your application. For more information, see Restore points.

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