Discontinued support for list view and summary view rules
Valid from Pega Version 7.2
The list view rule and the summary view rule are deprecated, and support for these rules has been discontinued. Existing list view and summary view reports will continue to work on supported browsers. However, the last version of Internet Explorer that list view and summary view rules support is Internet Explorer 11.
You cannot create new list view or summary view reports. Instead, create list reports and summarized reports by using the report definition rule. To prevent display issues, re-create the custom list view and summary view reports that you need as report definition reports.
Process Outline view is unavailable
Valid from Pega Version 7.2
Process Outline view is no longer available as of this release. Use Case Designer instead to configure your processes. For advanced options, you can open the underlying flow for a process in Process Modeler.
For more information, see Designing a case type and Diagram tab on the Flow form.
Personalized views in table layouts
Valid from Pega Version 8.4
Table layouts now provide users with the option to save preferred run-time configurations, such as column visibility and filtering, as permanent profiles. This enhancement helps users create dedicated views for specific work scenarios, which reduces the need for repetitive adjustments to the user interface and improves productivity.
For more information, see Enabling table personalization.
Upgrade impact
After an upgrade to 8.4 and later, the default table toolbar styling and experience may be unexpectedly different for any customized tables in a client's application: if you enabled a tool bar action for a personalizable table and the 8.4 application overrides your customization, your application now displays the default 8.4 table toolbar.
What steps are required to update the application to be compatible with this change?
Existing clients that upgrade to Pega Platform 8.4 and later may need to update applications in some scenarios. Any custom actions present in the overridden section may need to be re-authored into this toolbar using the additional actions section.
Web portal reuse removed from the mobile channel
Valid from Pega Version 8.5
The reuse of web portals for creating mobile apps with a single web view is no longer supported. You can conveniently update your existing channels that reuse web portals to take advantage of the multiple-views experience and native mobile capabilities, such as native mobile list views or floating action buttons.
Upgrade impact
The Reuse web portal option is removed from Pega Platform 8.5 and later.
What steps are required to update the application to be compatible with this change?
App developers need to use the migration tool available on the mobile channel to move their apps to the recommended new navigation designer. When users open existing mobile channel with the Reuse web portal option configured, they are prompted to run through the wizard to upgrade the mobile channel to the latest Pega Mobile Client based configuration. When this is done, app developers should rebuild the app.
Increased visibility of strategy design changes with simulation batch tests
Valid from Pega Version 8.4
Improve your understanding of the impact that individual changes to strategy design have on the decision funnel by running batch simulation tests directly from the strategy canvas. With batch simulation tests, you can check that your strategy changes produce the expected results, and immediately see the results in context.
For more information, see Increase the real-time visibility of strategy design changes with simulation batch tests (8.4).
Upgrade impact
After an upgrade to 8.4 and later, simulation outputs produced from earlier versions cannot be used to view canvas counts.
What steps are required to update the application to be compatible with this change?
Following a software upgrade to 8.4 or later, clients must re-run existing simulations in Decision Funnel mode to view the counts in the canvas.
Existing collections are deprecated
Valid from Pega Version 7.1.7
The original implementation of the Collection form is deprecated. Legacy instances in your application remain functional; however, any new instance you create uses the redesigned Collection form. Use the Decision category in the Records Explorer to view all collections available to you.
For guidance on upgrade limitations, see the Deprecated Collection form.
External data flow rules are deprecated
Valid from Pega Version 8.5
External data flows are now deprecated and no longer supported. To improve your user experience with Pega Platform™, the user interface elements associated with these rules are hidden from view by default. Identifying unused features allows Pega to focus on developing and supporting the features that you need.
For more information, see Deprecated: External data flows.
External data flow rules are removed
Valid from Pega Version 8.6
In previous versions of Pega Platform™, you could configure data flows to run in an external Hadoop environment. The external data flows functionality was deprecated and hidden from view in Pega Platform 8.5. The functionality has been now removed and is no longer available in Pega Platform 8.6.
For more information, see External data flow rules are deprecated.
Conversion of single-step assignments is no longer required
Valid from Pega Version 7.2
You no longer need to create a single-step assignment in a case type and then convert it to another supported step type. Instead, you can use the + Add step option in Case Designer to add any step type directly to a process in a stage. This change delivers a more consistent experience to users who are working in Case Designer and Process Modeler.
The following table lists the step labels in Case Designer that were updated to support this change.
Step label in previous versions | Step label in Pega 7.2 |
|---|---|
| Single-step assignment | Collect information |
| Approval | Approve/Reject |
| Attachment | Attach Content |
| Case | Create Cases |
For more information, see Adding a step to a process in a stage.
pxFeed replaces pxContextFeed and pxActivityFeed Pulse gadgets
Valid from Pega Version 7.4
The pxContextFeed and pxActivityFeed gadgets have been replaced by the pxFeed gadget to integrate the functionalities of viewing and posting messages in the Pulse activity feed. You can include this gadget within a section or harness across your application, for example, in the dashboard of the Case Manager portal, to display the activity feed. You must add the latest UI Kit ruleset to ensure that your application uses the pxFeed gadget instead of the pxContextFeed and pxActivityFeed gadgets to generate the activity feed.
For more information, see Pulse gadget and custom APIs.