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.

Required Oracle optimization parameter

Valid from Pega Version 7.1.3

To optimize performance, set the Oracle parameter optimizer_index_cost_adj to a value between 20 and 25. If this value is not set, the system can run exceedingly slowly, potentially blocking users from login.

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.

Synchronized database and application server settings

Valid from Pega Version 7.1.3

Configure your database and application server to use the same time zone and character encoding to avoid conflicts.

System Management

Valid from Pega Version 7.1.3

The PRPC installer has been enhanced to handle additional error conditions related to partial installs and duplicate keys; additionally, the hotfix rollback feature has been improved, and the Rulebase compare tool now supports HTTP(S) environments.

  • Rollback feature has been enhanced.
  • RuleBase Compare will work for secure (HTTPS) environments as well as  non-secure (HTTP) environments.
  • Install will gracefully handle the presence of a duplicate key during import.
  • When install fails, system will set tables back to original state.
  • Remote MBean methods will now work on multi-servant load-balancing systems.
  • Enhancements were made to harnesses in Split Schema systems.

PRServlet not required in PRPC URLs

Valid from Pega Version 7.1.6

PRServlet is no longer required in a URL when accessing PRPC. A URL typically written like this:

http://example.com/prweb/PRServlet?[QueryString]

Can instead be written like this:

http://example.com/prweb/?[QueryString]

This change is effective only for PRPC 7.1.6 and newer versions. Older versions of PRPC still require using PRServlet in a URL.

Add additional columns to customized work history tables

Valid from Pega Version 7.1.6

The standard work history table, pc_history_work, contains two new columns that return the latitude and longitude coordinate location of the action that prompted the history. Mobile devices can display this location as a street address. If you have a customized work history table, add these two columns to it:

  • <decimal name="pxLatitude" size="19" scale="9"/>
  • <decimal name="pxLongitude" size="19" scale="9"/>

Node description cannot match application server node name

Valid from Pega Version 6.3 SP1

A node's Short Description should not be the same value as the application server node name. If the node's Short Description is changed to be the same value as the application server node name, then the node description is automatically changed back to the original value after a system restart.

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.

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