Published Release Notes

WebSphere log error with Java 8 for Enterprise JavaBeans

For environments that are deployed by using Java 8 on IBM WebSphere Application Server version 8.5.5.9 through the last 8.5.5.x fix pack, the log might report that a class was not found when the application server attempts to start Enterprise JavaBeans. If Java EE functionality is not needed, no further action is required. However, to use Enterprise JavaBeans, see WebSphere log error with Java 8 for Enterprise JavaBeans.

Log file description in web.xml incorrect after upgrade to Apache Log4j 2

As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, it is recommended that you update the log file description in the web.xml file from location of prlogging.xml file to location of prlog4j2.xml file. The description indicates which log file is in use. Updating the description avoids confusion about which log file is current. Change the description as shown in the following example.

<resource-ref id="ResourceRef_5">
<description>location of prlog4j2.xml file</description>
<res-ref-name>url/pegarules.logging.configuration</res-ref-name>
<res-type>java.net.URL</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>

Apply logic to data import fields

When importing data from an external system, you can translate data fields into values that can be read by Pega^® Platform. From the Import wizard, you can do the following actions:

• Apply a decision tree or decision table to the data that is imported for a field.
• Use imported data for a field to look up a value in another record. For example, you can look up the key of a record that uses an external identifier to populate a foreign key field.
• Create templates that contain business logic, which eliminates the need to handle data transformations manually during preprocessing.

For more information, see Transforming data during import.

X-Forwarded-Host field is optional for HTTP proxy servers

Prior to Pega^® Platform 7.3, the X-Forwarded-Proto and X-Forwarded-Host fields were both required to deploy Pega Platform instances behind an HTTP proxy server. Some proxy servers or load balancers (for example, Amazon ELB) do not support the X-Forwarded-Hostfield. Starting with Pega 7.3, only the X-Forwarded-Proto field is required. For more information, see Deployment behind a reverse proxy.

Pega Cloud Services support for the AWS Canada (Central) region

Pega Cloud Services now supports deployment to the Amazon Web Services (AWS) Canada (Central) region. Deployment across multiple availability zones within a geographical region protects against zone faults and localized service disruptions, and ensures high availability.

For more information about regions and availability zones, see Pega Cloud Services capabilities.

This additional region is available as of QIII 2017.

Requestor pools management in Designer Studio

On the new Requestor Pools landing page, you can view and manage requestor pools across the cluster, including on the current node and remote nodes. By using this landing page, you can tune the requestor pools to improve the performance of services. You can clear the requestor pool for a service package and view the requestor pool basic metrics and configured thresholds.

For more information, see Requestor pools management, Clearing a requestor pool, Viewing details for a requestor pool, Tuning a requestor pool configuration.

Module version report generated from Designer Studio

From the new Class Management landing page, you can generate the module version report that provides information about classes in your system, module versions, and version creation dates. You can generate the report for all the nodes in the cluster or for a selected node that is either current or remote. The report is useful for debugging system problems because it helps identify the module version that is causing problems on a specific node.

For more information, see Module version report.

Ability to map JSON to clipboard properties by using a data transform

You can now map the entire JSON file or individual properties to and from the clipboard by using a data transform. Using a data transform makes it faster and easier to connect your Pega^® Platform to your system of record.

For more information, see Data transforms.

Pega Cloud Services support for the AWS EU (London) and US East (Ohio) regions

Pega Cloud Services now supports deployment to the Amazon Web Services (AWS) EU (London) and US East (Ohio) regions. Deployment across multiple availability zones within a geographical region protects against zone faults and localized service disruptions, and ensures high availability.

For more information about regions and availability zones, see Pega Cloud Services capabilities.

.

These additional regions are available as of QIV 2017.

Rules Assembly cache is deprecated

Rules Assembly (RA) cache and custom settings for its corresponding fua/assemblyCacheModeprconfig.xml file setting are deprecated because they are obsolete. A warning is logged at startup if a custom (non-default) value is specified for fua/assemblyCacheMode in the prconfig.xml file. The functional behavior of the system is not affected.