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.
BIX -I command-line option fails for unexposed properties
Valid from Pega Version 7.2.2
Business Intelligence Exchange (BIX) command-line extractions fail when the extract has a filter that uses unexposed property references that are passed in by the input file that you specified in the -I command-line option. Previously, the BIX extraction ignored the filter and the extraction did not fail.
Upgrade utility for Get Next Work performance
Valid from Pega Version 7.2.2
You can run a utility to upgrade Get Next Work processing to more quickly process assignments that were created in versions of the Pega 7 Platform earlier than 7.2.2. Performance is automatically improved on new installations.
For more information, see Upgrading Get Next Work performance.
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 point | Alternative extension point | Corresponding 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 API | New API | Description |
|---|---|---|
| Work-.QuestionShape | Work-.pzQuestionShape | A flow that displays one simple question. |
| Work-.QuestionShapeScr | Work-.pzQuestionShapeScr | A screen flow that displays one simple question. |
| Work-.SurveyDriver | Work-.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-.SurveySection | Work-.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. |