Custom database (DB) triggers are dropped during upgrade
Valid from Pega Version 7.1.8
The latest version of Pega 7 improves performance by no longer using database triggers to assist with System Pulse and Data-Rule-Summary processing, which is now done within the Pega 7 engine. As a result, DB triggers are no longer installed on either the pr_sys_updatescache or pr4_rule_vw tables.
When upgrading to the latest version of Pega 7, if you had previously implemented a custom database (DB) trigger on these tables, or a custom DB trigger that refers to these tables, it is removed during the upgrade process. No custom triggers are removed unless they reference these tables.
If you have custom DB triggers that reference the pr_sys_updatescache or pr4_rule_vw tables and perform other processing, those triggers must be reimplemented. When doing so, you must be careful to not modify the pr_sys_updatescache or pr4_rule_vw tables.
For more information, see Startup check removes custom DB triggers.
End of support for Netscape Plugin API in Google Chrome 45
Valid from Pega Version 7.1.8
Beginning with Chrome 45, which is expected to be available in September 2015, Google is ending support for browser plug-ins that rely on the Netscape Plugin API (NPAPI) architecture. These plug-ins include Microsoft Silverlight, Adobe Flash Player, and Java.
The Pega 7 Platform includes several optional features that use these plug-ins. For a detailed overview of these features, see Client-side technologies.
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.
PegaDATA connection settings now required in the prconfig.xml file
Valid from Pega Version 7.4
If you use the default prconfig.xml file that is included with Pega® Platform, and you have not removed the PegaDATA connection settings, no action is required. If you use a custom prconfig.xml file, for example, for running tests, ensure that the database connection settings for PegaDATA are not blank.
For more information about the connection settings, see PegaDATA connection settings in the prconfig.xml file.