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.

DB2-LUW database logfile size increase

Valid from Pega Version 7.1.5

This issue applies to DB2-LUW database platforms only.
 

To avoid running out of logfile space due to large transaction sets during the rule base load of a Pega 7.1.x install, upgrade, or maintenance level update, systems supported by a DB2-LUW database platform should increase the LOGFILSIZ parameter to at least 4096 pages from the default size of 1000 pages.

After the size has been increased, restart the database to ensure that the new setting is loaded into the database correctly.

Need to run script before updating Multitenant systems

Valid from Pega Version 7.1.5

When updating or upgrading a Multitenant system from Pega 7.1.5 or 7.1.6 to Pega 7.1.7, if that system uses either an Oracle or a PostgreSQL database, you may encounter the error:

“Table must be empty to add column.”

The Multitenant architecture requires an additional column on a number of the PRPC database tables (“pzTenantID”). In Pega 7.1.7, two additional PRPC tables were tenant-qualified: pc_schedule_task and pr_index_schedule_task. The Multitenant column is added to these tables by the update/upgrade process. However, Oracle and PostgreSQL do not allow the addition of a non-null column to an existing table unless the table is empty, so updating or upgrading systems on those databases displays the error detailed above.

To avoid this error, before beginning the update or upgrade, it is necessary to run a script:

  • OracleOracleMTupgrade.sql
  • PostgreSQLPostgresMTupgrade.sql

For updates, these scripts are located in the /scripts/ddl directory.

For upgrades, these scripts are located in the /Resourcekit/AdditionalUpgradeScripts directory.

Node types renamed after upgrade from Pega 7.2.2 to Pega Platform 7.3

Valid from Pega Version 7.3

If you used node classification in Pega® 7.2.2, when you upgrade to Pega 7.3, node type names are automatically changed to a new name when you start a node with a node type.

  • UniversalNode becomes Universal
  • WebUserNode becomes WebUser
  • BackgroundProcessingNode becomes BackgroundProcessing
  • BIXNode becomes BIX
  • SearchNode becomes Search

If you created agents in Pega 7.2.2, agent schedules are also automatically updated with a new name during the upgrade. For more information, see Customized agent schedules for standard Pega Platform agents must be updated after Pega 7.2.2 to Pega Platform 7.3 upgrade and the appropriate Deployment Guide.

Rollover policy for log files

Valid from Pega Version 7.3

The rollover policy for log files is now based on time (daily) and file size (maximum file size is 250 MB). Log files are rolled over daily or when the maximum file size is reached. Current (not rolled over) log files do not have a time stamp. The time stamp is added when the log file is rolled over. In addition, the log file name for the current log file does not include the date. You can add the date to the current log file; however, the log file will not be rolled over. In addition, the web.temdir variable for setting the log file location is no longer supported; use the pega.logdir variable instead.

For more information, see Pega Platform logging with the Log4j 2 logging service.

Customized agent schedules for standard Pega Platform agents must be updated after Pega 7.2.2 to Pega Platform 7.3 upgrade

Valid from Pega Version 7.3

If you used node classification in Pega® 7.2.2, when you upgrade to Pega 7.3, node type names are automatically changed to a new name when you start a node with a node type. Agent schedules for standard Pega Platform agents are deleted and re-created with the new node type name, but any customization that you made in Pega 7.2.2 is not saved. You must manually update the agent schedules for standard Pega Platform agents in Pega 7.3.

For more information, see Node types renamed after upgrade from Pega 7.2.2 to Pega Platform 7.3 and the appropriate Deployment Guide.

Pulse Extension points are deprecated

Valid from Pega Version 7.3

Beginning with Pega® Platform 7.3, Pulse uses the notifications feature to send notifications. As a result, Pulse extension points for email body, subject, and recipient list have been deprecated. Preferences set for Pulse notifications in earlier versions are no longer valid.

Use the alternatives listed in the following table to configure your Pulse message and notification preferences.

Deprecated extension pointAlternative extension pointCorresponding notification rule
pyInstantPulseNotification (Correspondence)pyAddPulsePost (Correspondence)pyAddPulsePost
pyReplyPulseNotification (Correspondence)pyAddPulsePost (Correspondence)pyAddPulsePost
pyMentionsPulseNotification (Correspondence)pyAddUserMentionedPost (Correspondence)pyAddUserMentionedPost
pyMentionsInNonCaseContext (Correspondence)pyAddUserMentionedPost (Correspondence)pyAddUserMentionedPost
pyNewPulsePostSubject (Field Value)pyAddPulsePostEmailSubject (Field Value)pyAddPulsePost
pyNewPulseFilePostSubject (Field Value)pyAddPulsePostEmailSubject (Field Value)pyAddPulsePost
pyNewPulseReplySubject (Field Value)pyAddPulsePostEmailSubject (Field Value)pyAddPulsePost
pyMentionedUserSubject (Field Value)pyAddUserMentionedPostEmailSubject (Field Value)pyAddUserMentionedPost
pyMentionedFollowerSubject (Field Value)pyAddUserMentionedPostEmailSubject (Field Value)pyAddUserMentionedPost
pyMentionedFollowerWithFilePostSubject (Field Value)pyAddUserMentionedPostEmailSubject (Field Value)pyAddUserMentionedPost
pyGetListOfEmailReceivers (Activity)D_pxGetCaseFollowers (Data page)pyAddPulsePost

To continue using the deprecated extension points, override the pyInvokepxNotify when rule and set it to return false.

For more information, see Management of user notification preferences.

Deprecated survey APIs

Valid from Pega Version 7.3

APIs that were available in the PegaSurvey ruleset have been superseded by Pega® Platform APIs. Although older APIs continue to function in this release, it is recommended that you update your flows and flow actions to use the new APIs because they provide the latest survey capabilities, and deprecated features are not supported.

The following table maps deprecated APIs to their replacement APIs.

Deprecated APINew APIDescription
Work-.QuestionShapeWork-.pzQuestionShapeA flow that displays one simple question.
Work-.QuestionShapeScrWork-.pzQuestionShapeScrA screen flow that displays one simple question.
Work-.SurveyDriverWork-.pxSurveyDriver

A flow that displays questions in a survey, which can be simple or complex.

You can control whether the questions are displayed on one or multiple screens.
Work-.SurveySectionWork-.pxSurveySection

A section that displays questions in a survey.

You can reference this section from a user action, such as a flow action or connector flow action, in a flow.

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.

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.

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