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.

Simple associations for quickly joining classes

Valid from Pega Version 8.3

Associations now have a simple mode. Use a simple association to quickly and easily join a class to another class. The simple association defines a left join, using a foreign key in the source class and the class key in the target class. Use an advanced association for all other conditions. In addition, simple associations are drawn in the Visual data model reporting mode to visualize the relationships that are available for reporting.

Upgrade impact

The new simple mode draws a map of where all the classes defined in the application rule are drawn as nodes. Relationships between the nodes that are defined by relevant properties are drawn as lines linking the two classes. This feature only includes Case and Data classes that are defined on the Application rule form's Cases and Data tab. It also only includes relevant fields for those classes in order to define the relationships from one class to another.

What steps are required to update the application to be compatible with this change?

After a successful upgrade, add the data and case type classes to the application rule in Dev Studio to have the selected classes appear as a node. In addition, if you want a relationship to display as relevant, set the properties (of the class that defines that relationship) as relevant.

 

For more information, see Exploring the data model.

Association changes after upgrade

Valid from Pega Version 8.3

Associations now have a simple mode. Simple associations are those that join to only one class, use a left join, and have one filter condition to a class key in the target class. Existing associations that define a simple foreign key relationship are upgraded to simple associations when opened; all others are treated as advanced associations. All associations continue to work in reporting.

Making an association simple changes only one piece of metadata; all other data on the association rule is not affected.

Upgrade impact

The new simple mode draws a map of where all the classes defined in the application rule are drawn as nodes. Relationships between the nodes that are defined by relevant properties are drawn as lines linking the two classes. This feature only includes Case and Data classes that are defined on the Application rule form's Cases and Data tab. It also only includes relevant fields for those classes in order to define the relationships from one class to another. 

What steps are required to update the application to be compatible with this change?

After a successful upgrade, add the data and case type classes to the application rule in Dev Studio to have the selected classes appear as a node. In addition, if you want a relationship to display as relevant, set the properties (of the class that defines that relationship) as relevant.

 

For more information, see Associations.

 

Search field type is deprecated

Valid from Pega Version 7.1.9

The search field type in Form Builder is deprecated. Use a data reference or user reference instead, both of which prompt users with an autocomplete field at run time.

For the full list of supported field types in Form Builder, see Supported display modes by field type.

New process for Pega Cloud customers to obtain BIX extract files

Valid from Pega Version 7.3

The process for obtaining Business Intelligence Exchange (BIX) extract and manifest files for Pega® Cloud customers has changed as a result of data security enhancements for HIPAA compliance. By default, after upgrading to Pega 7.3, you must obtain the BIX extract and manifest files from the Pega SFTP server. From within Designer Studio, you can configure the BIX extract and manifest files to be sent to a remote SFTP server by a file listener. For Pega Cloud customers who have purchased a Pega Cloud SFTP Server subscription, you can configure BIX to send the BIX extract and manifest files to the SFTP server's folders for remote SFTP client download.

For more information about obtaining files from the Pega SFTP server, see Obtaining BIX extract files from the Pega SFTP server.

For more information about having files sent to your SFTP server, see Defining SFTP-related data instances.

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.

BIX ruleset is now included with Pega Platform

Valid from Pega Version 8.3

The Pega Business Intelligence Exchange™ (BIX) ruleset is now included with Pega Platform™, which eliminates the need for additional provisioning for Pega Cloud customers and for a separate BIX installation for on-premises customers. To add BIX to your application, add the Pega-BIX:<version> ruleset to your application rulesets.

For more information, see Data extraction.

Upgrade impact

After a successful upgrade, the BIX ruleset is available within Pega Platform. You should synchronize the BIX ruleset and Pega rules to avoid extraction errors.

What steps are required to update the application to be compatible with this change?

After the upgrade is complete, change the ruleset version for Pega Platform and BIX to use the same, latest version.

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