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

Tomcat log files moved to work directory

Valid from Pega Version 7.1.2

For Tomcat application server users, the default path for PRPC logs has been changed to the "work" directory for Catalina. For example:

<tomcat>\work\Catalina\localhost\prweb

This directory can be cleaned up during administration. To avoid loss of files, you can redirect logging to a different directory after installation:

  1. Navigate to the <tomcat-home>\webapps\prweb\WEB-INF\classes directory.
  2. Open the prlogging.xml file.
  3. Locate the "appender" definitions section that contains the "@{web.tmpdir}" string
  4. Update the FileNamePattern values to point to the new directory.

For more details, refer to the “Change the default path to PRPC logs” section in the Tomcat installation guide for your database.

Additional upgrade scripts for new columns

Valid from Pega Version 7.1.4

In Version 6.2, additional columns (Major, Minor, and Patch) containing ruleset Version information were added to 15 tables in the PRPC database. When upgrading from a pre-Pega 7 release, scripts must be manually run after the upgrade to populate these columns.

These scripts are located in the Resource Kit, under Additional Upgrade Scripts.

  • If upgrading to a single schema, run both scripts.
  • If upgrading to a split schema, run the _data script against the data schema and run the _rules script against the rules schema.
  Depending upon your database type (platform) and the size of your database, these scripts may require significant time and system resources to run.

Choose the scripts for your database type:

  • db2zos_rulesetversion_columns_data.sql
  • db2zos_rulesetversion_columns_rules.sql

 

  • mssql_rulesetversion_columns_data.sql
  • mssql_rulesetversion_columns_rules.sql

 

  • oracle_rulesetversion_columns_data.sql
  • oracle_rulesetversion_columns_rules.sql

 

  • postgres_rulesetversion_columns_data.sql
  • postgres_rulesetversion_columns_rules.sql

 

  • udb_rulesetversion_columns_data.sql
  • udb_rulesetversion_columns_rules.sql

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.

Split schema systems require additional privileges

Valid from Pega Version 7.1.2

On Oracle split schema systems, add the following database privileges:

  • Grant DROP ANY INDEX to the Admin User.
  • Grant UNLIMITED TABLESPACE to the Rules User.

Use the Oracle Enterprise Manager to add these privileges or refer to the 7.1.3 Upgrade and Installation guides for Oracle.

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.

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.

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.

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