Categorize repeating dynamic layouts
Valid from Pega Version 7.2.1
Rows of a repeating dynamic layout can be categorized by a property. Categorization is useful for creating date-based navigation or categorizing list items. You can also set the maximum height of a repeating dynamic layout in the Presentation tab of the repeating dynamic layout properties. You configure categorization on the Operations tab of the repeating dynamic layout.
For more information see Repeating dynamic layout - Operations tab.
Adaptive learning without using an interaction ID
Valid from Pega Version 7.2.1
When you configure the Strategy shape in a data flow to capture the response to previous decisions, you do not have to provide an interaction ID. Instead, during the process of adaptive learning, adaptive models can query the Event Store data set over a specified period of time to retrieve decisions that were made for each response. This way, you eliminate the need to store the interaction ID on the client side.
For more information, see Delayed learning of adaptive models.
Flexbox-based dynamic layouts not supported for Android 4.4 and earlier
Valid from Pega Version 7.2.1
Flexbox-based dynamic layouts are not supported in Android 4.4 and earlier. When developing applications to be used on devices running Android 4.4 and earlier, use the inline-block layout mode for dynamic layouts.
Improved engine startup times
Valid from Pega Version 7.2.1
Performance enhancements in this release decrease engine startup times for new Java virtual machines (JVMs) and improve rule assembly for libraries. JVM startup times are faster because rule utility libraries and functions are no longer generated at startup. For more information, see Extract marker file not created at startup.
MBean Javadocs download file
Valid from Pega Version 7.2.1
The Pega 7 Platform MBean Javadocs are no longer provided in the distribution image; however, you can download the 
MBeanJMXJavadoc.zip file that was previously provided in the distribution image.
You can also use JConsole, which is included with the Java Development Kit (JDK), to obtain MBean information. The JConsole MBean tab provides attributes, operations, notifications, and other information on all the MBeans that are registered with the MBean server.
Single point of entry for decision management services configuration
Valid from Pega Version 7.2.1
Use the Services landing page to configure and monitor the Decision Data Store, Adaptive Decision Manager, Data Flow, and Visual Business Director services. This method simplifies decision management configuration because you can manage these services in one place.
For more information, see Services landing page.
Adaptive Decision Manager service in the Pega 7 Platform
Valid from Pega Version 7.2.1
The Adaptive Decision Management (ADM) service is now native to the Pega 7 Platform and is supported by the Decision data node infrastructure. Because of this enhancement, you no longer need to manage the ADM service as an external service. In addition, the ADM service does not require dedicated hardware or operating system environments.
For more information, see Services landing page.
Data Flow service in the Pega 7 Platform
Valid from Pega Version 7.2.1
The Data Flow service configuration on the Services landing page now provides a single point of entry for enabling running data flows in batch and real-time modes. To configure the Data Flow service, you must add Decision data nodes on which to run data flows and specify the number of Pega 7 Platform threads that are assigned to process the data flow runs. Additionally, as part of the Data Flow service, you can view the number of active data flows on each node.
For more information, see Services landing page.
HTML5 Visual Business Director (VBD) Planner
Valid from Pega Version 7.2.1
Visual Business Director (VBD) planner has a new look and is now available as an HTML5 web-based application, which replaces the VBD applet version. The new user interface is more intuitive and improves the user experience. You can open the HTML5 version of the planner on all supported browsers (Chrome, Firefox, Internet Explorer 11, and Safari).
For more information, see Visual Business Director.
Dynamic System Setting for partitioning Interaction History
Valid from Pega Version 7.2.1
Partition keys are used to optimize the retrieval and reading of records that are stored in the Interaction History data set. To define the number of partitions and partition keys for interactions that are recorded in the Interaction History data set, provide a positive integer value for the interactionHistory/numberOfPartition Dynamic System Setting.
For more information, see Interaction History partitions.