Deprecated end user portals
Valid from Pega Version 7.1.1
The following portals are no longer be supported:
- SysAdmDD
- WorkUserDD
- WorkManagerDD
As a best practice, customize standard, supported portals rather than update your existing portals to include new features.
Limited access for end user portals
Valid from Pega Version 7.1.1
The following portals are only accessible from supported versions of Internet Explorer in “quirks” mode:
- WorkUser
- WorkManager
Nesting dynamic containers not supported
Valid from Pega Version 7.1.1
Do not include a section containing a dynamic container inside of another dynamic container. This configuration may cause performance issues resulting in unexpected behavior at runtime, and is not supported.
Drag-and-drop functionality for lists and tables
Valid from Pega Version 8.3
Lists and optimized tables now support the reorganization of their content by reordering items. By configuring repeating dynamic layouts and tables to support drag-and-drop modifications, you enable users to move items between lists and within lists and tables. This enhancement ensures that you can create a flexible and dynamic user interface that helps users display and manage data.
The drag-and-drop functionality can also include custom actions that automate the processes that run when users move items.
For more information, see Configuring drag-and-drop functionality for lists and Configuring drag-and-drop functionality for tables.
Automatic retries for the SAVE operation on records
Valid from Pega Version 8.3
Batch and real-time data flow runs now automatically retry the SAVE operation on records when an error occurs because of resource unavailability. This functionality ensures that the records are eventually saved if the target data set is only temporarily unavailable, for example, because of load or network issues.
You can configure the default number of retries for the entire system in a dynamic system setting. To adjust the setting to different resource allocations and operating environments, you can update that number for each data flow run.
For more information, see Changing the number of retries for SAVE operations, Creating a batch run for data flows, and Creating a real-time run for data flows.
Cassandra 3.11.3 support for Pega Platform
Valid from Pega Version 8.3
Increase your system's reliability and reduce its memory footprint by upgrading the internal Cassandra database to version 3.11.3.
For on-premises Pega Platform™ users, after you upgrade to Pega 8.3, it is recommended that you manually upgrade to Cassandra 3.11.3. You can upgrade to Cassandra 3.11.3 on all operating systems except IBM AIX. If you do not want to upgrade to Cassandra 3.11.3, you can continue to use Cassandra 2.1.20, which is still supported.
For Pega Cloud Services 2.13 and later versions, Cassandra automatically upgrades to version 3.11.3 after your environment is upgraded to Pega Platform 8.3.
For information on how to manually upgrade to Cassandra 3.11.3, see the Pega Platform 8.3 Upgrade Guide for your server and database at Deploy Pega Platform.
Upgrade impact
After an on-premises Pega Platform upgrade, you still have the older version of Cassandra and must manually upgrade.
What steps are required to update the application to be compatible with this change?
To upgrade Cassandra, you must create a prconfig setting or a dynamic system setting with the new Cassandra version and then do a rolling restart of all the Decision Data Store nodes to upgrade them to the latest version of Cassandra.
Usability improvements to Admin Studio
Valid from Pega Version 8.3
Admin Studio offers a variety of usability enhancements, including:
- New access groups to differentiate between full and read-only access to Admin Studio
- A Java class lookup utility
- A requestor list for the logged-on operator
- The ability to display system node type in the logs
Also, if your environment uses Predictive Diagnostic Cloud (PDC), the Admin Studio overview page now includes a link to PDC.
For more information, see Managing requestors.
REST API for monitoring DSM services
Valid from Pega Version 8.3
Decision Strategy Manager (DSM) now provides a REST API that you can use to monitor DSM services without having to access Pega Platform™. By integrating your daily monitoring tools with the management REST API, you can retrieve a list of DSM nodes, check the status of these nodes, and view details of a service from all nodes in the cluster.
For more information, see Getting started with Pega API for Pega Platform.
Create custom criteria for proposition filters by using the condition builder
Valid from Pega Version 8.3
Proposition filters now use the condition builder to define the criteria that a proposition or group of propositions must match in order to be offered to a customer. The condition builder provides a simple, flexible tool for selecting and grouping the entry criteria.
For more information, see Create custom criteria for Proposition Filter rules with the condition builder (8.3).
Table toolbar functions
Valid from Pega Version 8.3
Optimized tables now support a table toolbar, that provides application users with the ability to adjust the data display to their needs. The toolbar conveniently groups several standard functions and custom actions. By using the toolbar, users can change the visibility of columns, group table data by fields, adjust the height of rows, and then save their personalized view. The toolbar is generated automatically, which provides a consistent design throughout your application.
For more information, see Configuring the table toolbar.