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.

Upgrading to the secure threading mechanism for email bots

Valid from Pega Version 8.1

In Pega Platform™ version 8.6, Pega Email Bot™ includes a more secure threading mechanism to help track emails from customers and other stakeholders in separate threads for an email triage case.

Upgrade impact

If you upgrade from Pega Platform version 8.5 or earlier, in which you configured an Email channel, perform the following steps to ensure that your system uses the new secure threading mechanism:

  • Update the service email rule that the system uses to send an email reply as the initial acknowledgment.
  • Update the email reply template in the data transform rule that the system uses when a customer service representative (CSR) sends the reply.

For more information about creating an initial acknowledgment email and email reply template, see Creating outbound email templates. For more information about the secure threading mechanism, see Use a secure threading mechanism in emails.

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

For the initial acknowledgment email used by your email bot, update the service method for your email listener rule. On the Response tab for this service email rule, expand the Message contents section. In the Message data section, you specify the rule that defines the structure of the content of the email body. In Pega Platform version 8.6, you use for this purpose the pyEmailAcknowledgement correspondence rule that takes into account the selected built-in template. This template includes the security code tag that the system uses for the secure threading mechanism. If your application uses a different rule in the Message data section, update this definition to match one of the built-in correspondence template rules, for example, EmailAckTemplate_Clear.

The pySetEmailBotReplyTemplate data transform rule sets the name of the email correspondence rule that the system uses as the email reply template. If you do not want to use the default approach using the Classic, Cobalt, or Clear outbound email template themes, override this data transform rule to set the email correspondence rule name for the Param.ReplyTemplate target in the Source column field.

For more information about how to update the service email rule and the data transform rule to ensure that your system uses the secure threading mechanism, see Upgrading to the threading mechanism available in the 8.6 version.

Requestor Management landing page access privileges

Valid from Pega Version 7.3

To access the Requestor Management landing page after upgrading to Pega® Platform 7.3, you need to add the appropriate privileges to the @baseclass and Pega-Landing access classes in the access roles. Apply these privileges to any application in which you want the operator to be able use the requestor management feature.

For more information, see the Requestor Management landing page 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.

Use of the @java function in expressions is deprecated

Valid from Pega Version 7.3.1

Use of the @java function in expressions is deprecated. Use a utility function or other product feature instead.

For more information about expressions, see Building expressions with the Expression Builder.

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.

DCO Compatibility tool is deprecated

Valid from Pega Version 8.1

The DCO Compatibility tool has been deprecated. Use the Application Guardrails landing page to see the compliance score and any warnings for your application.

For more information, see Application Guardrails landing page.

@java and locatable pages no longer supported

Valid from Pega Version 8.1

@java and locatable pages are no longer supported. Existing rules that use @java and locatable pages will continue to work; however, changes to these rules cannot be saved unless @java and locatable pages are replaced by supported functionality. Use a rule utility function (RUF) instead of an @java page, and use a data page instead of a locatable page. In addition, Pega Platform™ displays a guardrail warning when you open a rule that uses an @java page or a locatable 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