Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

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.

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.

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.

Behavior changes when reporting on descendant classes

Valid from Pega Version 7.3.1

Report Definitions that use the Report on descendant class instances option with the Include all descendant classes option apply only to the Applies to Class. Join classes are not included as they were in previous Pega® Platform versions. The following example shows what happens for each possible scenario for Report on descendant class instances when the report is defined on ClassA with a class join with Work-.

  • If Report on descendant class instances is disabled, the report runs against ClassA and the join happens with Work-. The behavior is the same in Pega 7.3.1 as it is in previous Pega Platform versions.
  • If Report on descendant class instances is enabled, and Include single implementation class is selected, the report runs against ClassA and the join happens with the MySampleClass implementation class. The behavior is the same in Pega 7.3.1 as it is in previous Pega Platform versions.
  • If Report on descendant class instances is enabled, and Include all descendant classes is selected, the report runs against ClassA and its descendants and the join happens with Work-. In previous Pega Platform versions, the join happened with the MySampleClass implementation class.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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