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.
Service Portlet rules are deprecated
Valid from Pega Version 8.2
Service Portlet rules are deprecated. Existing rules will continue to work, but you cannot create new ones. Use Pega Web Mashup instead. In addition, some changes might impact functionality. If you are using Portlet rules and plan to upgrade, contact your customer service representative.
For more information about Pega Web Mashup, see About Pega Web Mashup.
Deprecated metadata types in the Connector and Metadata wizard
Valid from Pega Version 8.2
The WSDL, SAP WSDL, and DTD metadata types have been deprecated in the Connector and Metadata wizard. For WSDL, use SOAP integration, and for DTD, use XSD.
For more information about SOAP connectors, see About Connect SOAP rules. For more information about XSD, see About the Connector and Metadata wizard.
Deprecated support for passing symbolic index as strings to value lists and page lists
Valid from Pega Version 8.2
Starting with the next release after Pega Platform™ 8.2, passing symbolic indexes as strings in parameters, properties, and string literals to both value lists and page lists will no longer be supported. The following examples show the syntax that still works in Pega 8.2, that will not work in the next release:
myPageList("<LAST>")
and
param.str = "<LAST>" myPageList(param.str)
The following example shows syntax that currently is not supported and gives a validation error. This syntax will also not work in future releases.
param.str = <LAST> myPageList(param.str)
To avoid issues after upgrading to Pega 8.3, refactor all occurrences of this syntax in your code. For instructions on how to find occurrences of this syntax in your code, see Refactoring unsupported symbolic index syntax for value lists and page lists.
For more information about the correct use of symbolic indexes, see Symbolic indexes – APPEND, CURRENT, INSERT, LAST, and PREPEND.
Changes in JSON results when checking the health of your system
Valid from Pega Version 8.2
Beginning with Pega Platform™ 8.2, the JSON results that are returned when you ping a Pega Platform instance have changed. JSON results now include node type and health information, including test name, status, state, and node ID. The following samples show JSON results from versions before 8.2 and as of 8.2.
JSON results for pre-Pega Platform 8.2:
{ "duration":"3954.448601", "count":"0" }
JSON results for Pega Platform 8.2 and later:
{"node_type":["WebUser"],"health":[{"last_reported_time":"2019-02-14T16:10:49.589Z","test_name":"Sample-Stream-Check","status":"success"}],"state":"healthy","node_id":"10.10.10_samplenode"}.