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.
Remote device log retrieval from online-only mobile apps
Valid from Pega Version 8.3
In addition to device logs from offline-enabled mobile apps, Pega Mobile Client™ can now upload device logs from online-only mobile apps. The upload to Pega Platform™ starts when a user restarts the mobile app. You retrieve device logs from a specific device to support remote users and troubleshoot mobile apps.
For more information, see Retrieving device logs.
Improved mobile user experience with spaces
Valid from Pega Version 8.3
Spaces in mobile apps have been enhanced to provide a wider screen area for navigation between content tabs such as Pulse, Boards, Subspaces, and Tasks. Mobile users can now use native selection controls to choose from the same space-specific actions that are available to users of desktop-based applications. The enhancement improves the usability of spaces and promotes collaboration between mobile users.
Spaces on mobile apps do not require any additional configuration.
For more information about spaces, see Collaborating with users by using spaces.
Increased display area in mobile apps
Valid from Pega Version 8.3
Mobile apps now support hiding the top and bottom bars when the user scrolls down. When the user scrolls up, the bars appear again. This enhancement improves the mobile user experience by presenting more data on the screen, for example, a longer list of items.
For more information, see Advanced layout options.
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.
Simple associations for quickly joining classes
Valid from Pega Version 8.3
Associations now have a simple mode. Use a simple association to quickly and easily join a class to another class. The simple association defines a left join, using a foreign key in the source class and the class key in the target class. Use an advanced association for all other conditions. In addition, simple associations are drawn in the Visual data model reporting mode to visualize the relationships that are available for reporting.
Upgrade impact
The new simple mode draws a map of where all the classes defined in the application rule are drawn as nodes. Relationships between the nodes that are defined by relevant properties are drawn as lines linking the two classes. This feature only includes Case and Data classes that are defined on the Application rule form's Cases and Data tab. It also only includes relevant fields for those classes in order to define the relationships from one class to another.
What steps are required to update the application to be compatible with this change?
After a successful upgrade, add the data and case type classes to the application rule in Dev Studio to have the selected classes appear as a node. In addition, if you want a relationship to display as relevant, set the properties (of the class that defines that relationship) as relevant.
For more information, see Exploring the data model.
Association changes after upgrade
Valid from Pega Version 8.3
Associations now have a simple mode. Simple associations are those that join to only one class, use a left join, and have one filter condition to a class key in the target class. Existing associations that define a simple foreign key relationship are upgraded to simple associations when opened; all others are treated as advanced associations. All associations continue to work in reporting.
Making an association simple changes only one piece of metadata; all other data on the association rule is not affected.
Upgrade impact
The new simple mode draws a map of where all the classes defined in the application rule are drawn as nodes. Relationships between the nodes that are defined by relevant properties are drawn as lines linking the two classes. This feature only includes Case and Data classes that are defined on the Application rule form's Cases and Data tab. It also only includes relevant fields for those classes in order to define the relationships from one class to another.
What steps are required to update the application to be compatible with this change?
After a successful upgrade, add the data and case type classes to the application rule in Dev Studio to have the selected classes appear as a node. In addition, if you want a relationship to display as relevant, set the properties (of the class that defines that relationship) as relevant.
For more information, see Associations.
Mobile apps display skeletons for the initial screen load
Valid from Pega Version 8.3
Android and iOS mobile apps now display a skeleton before the initial screen loads, which enhances user experience and provides faster response to user actions on complex mobile screens or over slow networks. Until the initial screen is ready to be displayed, Pega Platform™ displays an empty placeholder that imitates the actual user interface.
Skeletons for the initial screen in mobile apps do not require any additional configuration.
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).