Tomcat log files moved to work directory
Valid from Pega Version 7.1.2
For Tomcat application server users, the default path for PRPC logs has been changed to the "work" directory for Catalina. For example:
<tomcat>\work\Catalina\localhost\prweb
This directory can be cleaned up during administration. To avoid loss of files, you can redirect logging to a different directory after installation:
- Navigate to the <tomcat-home>\webapps\prweb\WEB-INF\classes directory.
- Open the prlogging.xml file.
- Locate the "appender" definitions section that contains the "@{web.tmpdir}" string
- Update the FileNamePattern values to point to the new directory.
For more details, refer to the “Change the default path to PRPC logs” section in the Tomcat installation guide for your database.
Slow WebSphere performance on Mac platforms
Valid from Pega Version 7.1.2
Use the following JVM setting to improve WebSphere performance on Mac platforms:
-Djava.net.preferIPv4Stack=true
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.
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.
Identify, install, and manage hotfixes with the Hotfix Manager
Valid from Pega Version 7.1.8
Hotfixes are packages of files that address issues in Pega 7 and in participating Industry Applications. With Hotfix Manager, you can:
- Scan your system for installed and missing critical hotfixes and create a report that you can provide to Pegasystems Support for diagnostic purposes.
- Review the descriptions and contents of hotfixes.
- Install, rollback, and commit hotfixes.
- Manage hotfixes that include schema changes or require other special handling.
The Hotfix Manager replaces the Update Manager Hotfix Installer and System Scanner, both of which are deprecated. For more information, see Hotfix Manager identifies, installs, and manages hotfixes to Pega 7 and participating Industry Applications.
Enhanced product rule form for easy application packaging
Valid from Pega Version 7.1.8
The enhanced product rule form allows you to add applications in Delta mode, which includes only the patch version of the rulesets that comprise the application rule. You can also use Global exclusions to exclude one or more rules that are not associated with a ruleset version.
These enhancements allow easy packaging of non-versioned rules that are often deployed separately and reduce the need to manually add them later.
For more information, see Product rules - Completing the Contents tab.
Updated Rule-Utility-Function resolution
Valid from Pega Version 7.1.8
Rule-Utility-Function rules are now resolved based on ruleset.
Previously, if you had the same function @xyz() in different libraries in different rulesets, you could not call the function by using @xyz, because that would throw an exception.
The resolution process has since been updated so that rule resolution is now based on the highest ruleset in context. This update makes the function resolution process consistent with how rule resolution is performed for other rule types.
For more information, see Functions in expressions.
Define function input parameters on the Create or Save As forms
Valid from Pega Version 7.1.8
When creating or updating a Rule-Utility-Function ruleset in Designer Studio, use the Create or Save As forms to define or change parameters as a part of the form. The Parameters section on either of these forms allows you to set the function's name and Java type before opening the function.
Previously, you updated these fields on the Parameters tab for the function after the form was created. Moving these fields to the Create and Save As forms helps to proactively detect functions with the same signature in the same ruleset before saving the function.
For more information, see Defining function input parameters on the Create or Save As forms.
Support for Oracle TIMESTAMP data types
Valid from Pega Version 7.1.8
The Oracle TIMESTAMP data type is now fully supported throughout the Pega 7 data layer. The TIMESTAMP columns for data provide greater precision than the previously available DATE columns.
This release does not include any columns that use the TIMESTAMP data type at installation. However, after installation or upgrade:
- Any newly created columns (for example, those created when optimizing a property or defining a new table) use the TIMESTAMP column type.
- Any existing data still uses DATE values.
- Oracle users can manually convert any existing DATE column types to use a TIMESTAMP column type instead.
- Altering the column type for existing values in a column does not provide any greater precision for those values because they still use DATE values and not DATETIME values.
For more information, see DateTime property mapping in Oracle for Pega 7.
Updates to the Business Intelligence Exchange (BIX) product
Valid from Pega Version 7.1.8
The Business Intelligence Exchange (BIX) add-on has been updated with several new features. BIX 7.1.8 fully supports extraction of data from a Pega 7 multi-tenant instance. BIX can also now be run on Pega Cloud instances. Additionally, the new pxExtractDataWithArgs activity can be used by on-premises customers to schedule BIX runs by using Pega Platform agents.
For more information, see the BIX 7.1 User Guide.