Derby databases are no longer supported
Valid from Pega Version 7.1.8
Previously, an embedded Derby database could be used as a file system. This setup was configured by setting storage/class/<<filesystem>>/type to "embedded" in the prconfig
file.
After upgrading, storage types that are specified as "embedded" now default to the local file system.
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.
Deprecated rule types
Valid from Pega Version 7.1.8
The following rule types have been deprecated as of the Pega 7.1.8 release:
- Form
- Hierarchy
- Service COM
- Service BPEL
- Connect BPEL
- Parse Transform
- Parse Transform Collection
- Parse Infer
For more information, including suggested alternate rule types, see the help topic Deprecated features.
Configuration required for data operations on external schema when using a Postgres database
Valid from Pega Version 7.1.8
When you use the API for data operations on external schema in the Postgres database, you must update the prconfig.xml file. No other platform requires a prconfig.xml update.
To update the prconfig.xml file:
- Stop the server and add the following entry to the prconfig.xml file:
env name="database/databases/postgres_ext/defaultSchema"
value="externalschema"
wherepostgres_ext
is the external database that uses the external schema “externalschema”. - Restart the server.
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.
Internal rules in search results and explorers
Valid from Pega Version 7.4
Using old: is no longer supported in search. You can include internal rules in search results and make them available in the Application and Records explorers. Include internal rules in search results either by adding the PegaDevelopmentruleset to your application or by clicking the Enable diagnostic features option in your operator preferences.
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.
pxFeed replaces pxContextFeed and pxActivityFeed Pulse gadgets
Valid from Pega Version 7.4
The pxContextFeed and pxActivityFeed gadgets have been replaced by the pxFeed gadget to integrate the functionalities of viewing and posting messages in the Pulse activity feed. You can include this gadget within a section or harness across your application, for example, in the dashboard of the Case Manager portal, to display the activity feed. You must add the latest UI Kit ruleset to ensure that your application uses the pxFeed gadget instead of the pxContextFeed and pxActivityFeed gadgets to generate the activity feed.
For more information, see Pulse gadget and custom APIs.
Survey rules are deprecated
Valid from Pega Version 7.4
Surveys that were created prior to version 7.4 of Pega Platform are now deprecated. As a best practice, recreate your survey by using the Survey Management landing page, and then reuse questions or question pages from your survey library.
For more information about creating surveys, see Improved survey authoring.
Questionnaire shape replaces Survey shape in legacy flows
Valid from Pega Version 7.4
In flows that reference deprecated surveys, the Questionnaire shape has replaced the Survey shape. Although legacy surveys continue to function in this release, update your flows to use the Survey shape because it provides the latest survey capabilities, and deprecated features are not supported.
For more information about the new survey authoring experience, see Improved survey authoring.