Split schema systems require additional privileges
Valid from Pega Version 7.1.2
On Oracle split schema systems, add the following database privileges:
- Grant DROP ANY INDEX to the Admin User.
- Grant UNLIMITED TABLESPACE to the Rules User.
Use the Oracle Enterprise Manager to add these privileges or refer to the 7.1.3 Upgrade and Installation guides for Oracle.
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.
Discontinued support for list view and summary view rules
Valid from Pega Version 7.2
The list view rule and the summary view rule are deprecated, and support for these rules has been discontinued. Existing list view and summary view reports will continue to work on supported browsers. However, the last version of Internet Explorer that list view and summary view rules support is Internet Explorer 11.
You cannot create new list view or summary view reports. Instead, create list reports and summarized reports by using the report definition rule. To prevent display issues, re-create the custom list view and summary view reports that you need as report definition reports.
Label changes to field types in Case Designer
Valid from Pega Version 7.2
The following field types have been renamed in Case Designer to be consistent with Data Designer and other areas of the Pega 7 Platform.
Label in previous versions | Label in Pega 7.2 |
---|---|
Text | Text (single line) |
Text (multiple lines) | Text (paragraph) |
Check box | Boolean |
Date and time | Date & time |
Date | Date only |
Drop down | Picklist |
Number (integer) | Integer |
Number (decimal) | Decimal |
Users who upgrade from versions prior to Pega 7.2 do not have to take any action because the label changes are cosmetic and do not affect the underlying controls or property types that support form building.
For more information about the field types that you can use when building a form, see Storage and display of single-value fields.
Process Outline view is unavailable
Valid from Pega Version 7.2
Process Outline view is no longer available as of this release. Use Case Designer instead to configure your processes. For advanced options, you can open the underlying flow for a process in Process Modeler.
For more information, see Designing a case type and Diagram tab on the Flow form.
New location for case-type settings
Valid from Pega Version 7.2
The configuration options for case-type settings have been moved from the property panel to the Settings tab in Case Designer. This change separates behavioral settings from life-cycle settings so that you can stay focused as you design your case types.
For more information, see Configuring case-type behavior.