Extract data from Pega Cloud to an on-premises database
Valid from Pega Version 7.4
You can now use Pega® Business Intelligence Exchange (BIX) to extract data from Pega Cloud to an on-premises relational database management system. Extracting data from Pega Cloud directly to an on-premises database improves efficiency by eliminating the need for file extraction and the development of a file extraction infrastructure.
For more information, see Extracting data from Pega Cloud to an on-premises database.
Support for additional health metrics on the Application Quality landing page
Valid from Pega Version 7.4
On the Application Quality landing page, you can monitor the health of your current application to identify areas that need improvement before deployment. The landing page provides application metrics such as the number of executable rules, the guardrail score, the number of guardrail warnings, the test coverage percentage, and the pass rate of PegaUnit tests. From this landing page, you can also view data for the entire application, for each of its cases, and for rules that are not part of any case type.
For more information, see Application Quality landing page.
View the configuration settings for Pega Platform nodes in Designer Studio
Valid from Pega Version 7.4
On the new Configuration Settings landing page, you can view a list of the configuration settings for a specific node, current or remote, or for an entire cluster. From this landing page you can diagnose settings issues, determine whether settings are loaded correctly, and review the settings' purposes. You can also download the prconfig.xml file for any node in a cluster to modify the settings. The ability to view settings for all nodes in the Cluster from a single landing page makes diagnosing configuration issues across the cluster simpler and easier than logging on to each node individually to view its system settings. For example, if a started agent does not run, you can check if agents are enabled on your system; or if some of your caches are too big, you can check the setting for the cache size. You can also determine if settings are loaded correctly, and identify discrepancies in the settings across the nodes.
For more information, see Viewing the current configuration settings of a node or the whole cluster, Downloading and viewing the prconfig.xml file for a specific node, REST APIs for viewing the configuration settings for Pega Platform.
Improved connection pooling performance
Valid from Pega Version 7.4
HikariCP is now used for connection pooling for databases that are configured by using a URL. HikariCP improves connection pooling performance; however, more database connections might be used than in previous versions of Pega® Platform.
As a result of the switch to HikariCP, you cannot use the System Management Application (SMA) to get diagnostic data from your application. For instructions about how to get diagnostic data by using REST services, see Obtaining connection pool diagnostic data by using REST services.
Support for templated auto responses during email triaging of interaction cases
Valid from Pega Version 7.4
When you triage an interaction case by email, you can now select a predefined email response to provide feedback to a customer more quickly. The category that is associated with this email determines the type of responses that you can select. You can create an email response template or use an existing template.
For more information, see Defining suggested replies for the Email channel.
No longer supported translator configuration options
Valid from Pega Version 7.4
The following translator configuration options are not needed and are no longer supported. If you previously configured any of these system settings, remove them from the system settings to avoid a warning message. For example, if you set translator/useparserfamily, the following message is displayed at startup: "Translator option, 'translator/useparserfamily' is not needed and no longer supported. Remove this from the system settings."
- translator/useparserfamily
- translator/usecodegenerator
- translator/usenativedouble
- translator/optimization/use71BlockAnalysis
- translator/optimization/use71ConstantFolding
- translator/optimization/use71AssignmentTypeSimplification
- translator/optimization/use71IntrinsicFunctions
- translator/use71PropSetGeneration
- translator/use71ParserAssignment
- assembly/model/useBlock4ContiguousSets
- /translator/pandc/comparepandcalgorithms
- /translator/pandc/use6xalgorithms
- /Compatibility/CheckForTopLevelClassMismatch
In addition, the com.pega.pegarules.generation.parseoverride bootstrap option is no longer supported. Remove this option from the system settings.
Submit application changes made in Pega Express to a continuous integration and delivery pipeline
Valid from Pega Version 7.4
After you make changes to your application in Pega® Express, you can submit these changes into a continuous integration and delivery pipeline that is configured in Deployment Manager. By using Pega Express to submit your application changes into staging, preproduction, and production systems, you can quickly start builds without involvement from IT.
For more information, see Starting a continuous delivery build.
System state data is saved for 90 days
Valid from Pega Version 7.4
System state data is now saved to the database for 90 days and can be downloaded as a JSON file. Having previous system state data available is useful for debugging system problems. Operators with the pzSystemOperationsObserver privilege can download system state data from the Cluster Management landing page for either the entire cluster or a single node. In addition, the PersistClusterState and PersistNodeState agents have been added to the Pega-RulesEngine ruleset for persisting system state data to the database.
For more information, see Downloading the system state.
Ability to run report definitions against an Elasticsearch index
Valid from Pega Version 7.4
To improve report generation performance, you can now run report definitions against Elasticsearch indexes instead of using SQL queries directly against the database. This feature is disabled by default and does not apply to reports that have features that are not supported by Elasticsearch. If a report query cannot be run against Elasticsearch indexes, Pega® Platform automatically uses an SQL query.
For information about enabling and using this feature, see Configuring a report definition to run against an Elasticsearch index.
Search index fields can retain the original property type
Valid from Pega Version 7.4
You can now configure fields in the search index to retain the property type of the original property. By default, properties in an indexed class are converted to a string before they are placed in fields in the search index, referred to as a typeless index. Type-aware search indexes let you run report queries with filters, date calculations, and aggregations directly in the query. To configure a class to have type-aware properties, use a dedicated index.
For more information, refer to Custom search properties.