Integrated Application Security Checklist helps you deploy a secure application
Valid from Pega Version 7.3.1
Pega® Platform now provides an Application Security Checklist that you can refer to when you prepare your application for deployment. By completing the recommended tasks in this checklist, you can track your progress, access instructional information for tasks, and verify that your configurations are secure.
For more information, see Preparing your application for secure deployment, Compliance Score tab, Designer Studio — Home page.
Requestor pools management in Designer Studio
Valid from Pega Version 7.3.1
On the new Requestor Pools landing page, you can view and manage requestor pools across the cluster, including on the current node and remote nodes. By using this landing page, you can tune the requestor pools to improve the performance of services. You can clear the requestor pool for a service package and view the requestor pool basic metrics and configured thresholds.
For more information, see Requestor pools management, Clearing a requestor pool, Viewing details for a requestor pool, Tuning a requestor pool configuration.
Generate an XSD file for XML format output
Valid from Pega Version 7.3.1
You can now use Business Intelligence Exchange (BIX) to generate an XSD file for existing XML output when the Get all properties check box is selected on the Definition tab of the Extract rule form. You can now validate the XML output and generate DDL statements by using the generated XSD file. Some tags might not be included in the generated XSD file because of missing values in the XML output.
For more information, see Generating an XSD file for XML output.
Class structure expanded for surveys and questions
Valid from Pega Version 7.3.1
You can now create surveys and questions at any class level. Because there is no longer a restriction on which class of flows can use the Survey and Question smart shapes, you can create more contextual surveys that reference embedded properties, or instances of classes, that you define outside the Work- class structure.
For more information about using the Survey or Question smart shapes in a flow, see Integration methods for surveys.
Import and export artifacts to and from a repository
Valid from Pega Version 7.3.1
You can import and export development artifacts to and from a repository. Use the Import wizard, the Export wizard, or the service-enabled system management command-line tool to move artifacts. For more information, see Tools for migrating rules and data.
Locatable pages are deprecated
Valid from Pega Version 7.3.1
Locatable pages are deprecated. Use a data page instead. Data pages provide improved performance. When you save a rule that has a Locate Page Activity or when you create an activity of type Locate page, a guardrail warning is displayed indicating that this feature has been deprecated.
For information about data pages, see Data pages.
Migrate DDS data across various schema versions
Valid from Pega Version 7.3.1
You can use multiple versions of a single Decision Data Store (DDS) data set type in different applications that run on the same Pega® Platform instance and efficiently move data across those versions even if the underlying data schema is different. This solution improves the data management process and simplifies the reuse of existing data.
For more information, see Decision Data Store migration.
Support for PMML version 4.3 in predictive models
Valid from Pega Version 7.3.1
You can now leverage predictive models in the Predictive Model Markup Language (PMML) version 4.3 by importing them into predictive models on Pega® Platform. Pega Platform utilizes a large part of the PMML standard with the exception of some PMML 4.3 features that are not supported in the Predictive Model rule.
For more information, see Support for PMML version 4.3 in predictive models and Creating a predictive model.
Module version report generated from Designer Studio
Valid from Pega Version 7.3.1
From the new Class Management landing page, you can generate the module version report that provides information about classes in your system, module versions, and version creation dates. You can generate the report for all the nodes in the cluster or for a selected node that is either current or remote. The report is useful for debugging system problems because it helps identify the module version that is causing problems on a specific node.
For more information, see Module version report.
Emit remaining event strategy data at the end of a data flow run
Valid from Pega Version 7.3.1
Data flows have been updated to prevent data loss in event strategies. By default, when a batch or a real-time data flow stops and it contains an event strategy with Tumbling windows, all of the events that are in the Tumbling windows are emitted. Event emission triggers further processing in the event strategy, like aggregations and joins.
For more information, see Enhancements to data flows that contain event strategies and Event Strategy rule form - Completing the Event Strategy tab.