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.

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

Source field not displaying in data transform

Valid from Pega Version 7.1.4

On the Data Transform rule form when using the Update Page action, if the Relation value is updated to “with values from”, the Source field will not be displayed.

(Note that for existing data transforms where the Source field has already been completed, this situation should not occur.)

Workaround

  1. Below is a data transform that has been configured to use Update Page.
    DataTransform1.jpg
  2. If a user were to choose an alternate source by updating the ‘with values from’ Relation value, they would not be prompted to provide a page name in the Source field.
    DataTransform2.jpg
  3. At this point, to be able to enter the Source page value, the user has to save the rule, which results in an error because the source page value is blank. This causes the field to appear.
    DataTransform3.jpg
  4. Once the field has appeared, the Source page value can be provided, and the form can be saved successfully.
    DataTransform4.jpg

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.

Twitter data sets no longer supported

Valid from Pega Version 7.1.9

Twitter is deprecating several APIs, which will disrupt the Twitter data set functionality. Twitter data sets will not be able to fetch any tweets or direct messages. This issue affects all applications that use Twitter data sets to connect to social (mainly Pega Customer Service applications).

This change applies to the current and earlier releases of Pega Platform™ that make use of Twitter data sets and it impacts all environments, including Pixar, VM, and Pega Labs instances.

Twitter connectors will be fully functional at a later date. For now, the best practice is to de-emphasize social media in your data sets.

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