Published Release Notes

DCO and PMF integration is unavailable

DCO and PMF integration functionality is not available in this release. Related project management controls have been removed from the following:

• System Settings landing page (Designer Studio > System > Settings > Project Management)
• Application Profile landing page (Designer Studio > Application > Profile > Specifications)
• Add/Edit Specification dialog

Restricted SMA access

System Management Application (SMA) remote connections are not supported on JBoss EAP 6.x. This means SMA users may only monitor locally connected systems. Ensure that the "Local JVM Connection..." option is selected when configuring PRPC nodes:

Stages and Steps may not appear as expected

There are some unique configurations of the newly enhanced pxDisplayStages gadget that can lead to case type "Stages and Steps" appearing more than once or not at all.  In the event that your application experiences one of these scenarios, the recommended work around is to relocate the gadget:

• Add pxDisplayStages to the pyCaseContainer section (or equivalent)
• Remove pxDisplayStages from the pyCaseActionArea section (or equivalent).

Text Input control number type does not validate

When a Text Input control type is set to "Number" in the Presentation tab:

• Validation does not trigger and the field is blanked out when a user submits the form.
• If a value other than a number is entered, the browser sends an empty value, and the value is not validated.
• In the Clipboard, the field value displays as empty.
• If the field is required, the validation displays.

This issue occurs when using both the Chrome and Safari web browsers, and is a result of browser behavior for the HTML5 type=“number”. To fix this issue when using these browsers, do not use the "Number" type in Presentation tab of a Text Input control. Instead, the type should be set to "Text".

Unclear error message when saving shared class instance in tenant layer

If you attempt to save a shared class instance from the tenant layer, Pega 7 displays this message:

This record has x errors. Save Failed: There was a problem saving an instance of class: Error Code: <none> SQL State: <none> Message: <none>

You cannot save a shared instance from the tenant layer if that instance cannot be overridden.

System starts slowly after upgrade or update on IBM DB2 for z/OS

Additional tables are added to upgraded and updated systems. If your system starts up very slowly after an upgrade or update, the database statistics on these new tables might not have generated correctly. To correct this issue and improve performance, your database administrator needs to manually rebuild the statistics for all tables in the rules schema.

Clustering equal to none might cause errors

Some Pega 7 Platform features might not work when theidentification/cluster/protocolsetting in the prconfig.xml file is set to none. Some features that might not work are remote tracing and management actions on the node from the Requestor Management and Agent Management landing pages. Setting the clustering protocol to none is not recommended and will not be supported in a future Pega 7 Platform release.

Disregard this startup error for Oracle Weblogic deployments

If you install, upgrade, or update your Oracle Weblogic application server to Pega 7.2.2, disregard the error stack that begins with text similar to the following:

ERROR - WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT 2014 1604337 Oracle WebLogic Server Module Dependencies 12.1 Tue Mar 11 15:35:15 MDT 2014 WebLogic Jersey Server Integration 3.0 Fri Feb 21 10:55:11 UTC 2014 must use JDK 1.8+ with WebSocket
2016-11-07 06:13:01,690 [ WIN-L3EEURCNCP1] [ STANDARD] (pr.DefaultAsyncSupportResolver) ERROR - Real error: Unable to configure jsr356 at that stage. ServerContainer is null

This message appears because the Pega 7.2.2 real-time notification feature initially tries to use WebSocket and then falls back to long polling. The Pega 7 Platform does not support WebSocket for Oracle Weblogic servers, and instead uses long polling for real-time notifications.

Disregard this Java script console message

Pega 7.2.2 introduced real-time notifications by using Comet technologies such as WebSocket and long polling. WebSocket provides the best results, but both WebSocket and non-blocking long polling must be supported by your application server. If your application server does not support WebSocket, you might see a JavaScript error that begins with text that is similar to the following text:

WebSocket connection to 'ws://vnbamdevapp01:8080/prweb/PRPushServlet/... Error during WebSocket handshake: Unexpected response code: 501_getWebSocket @ pzpega_ui_messaging_1802554968!!.js:1195 pzpega_ui_messaging_1802554968!!.js:3265 Websocket closed, reason: Connection was closed abnormally (that is, with no close frame being sent). - wasClean: falselog @ pzpega_ui_messaging_1802554968!!.js:3265 pzpega_ui_messaging_1802554968!!.js:3265 Websocket failed on first connection attempt. Downgrading to long-polling and resending

You can disregard this message.

However, to take advantage of the improvements to real-time notifications, enable support for WebSocket:

• For IBM WebSphere Application Server Liberty Core, see your deployment guide for instructions on configuring the application server.
• For Red Hat JBoss, see your deployment guide for instructions on enabling WebSocket support.
• For Apache Tomcat application servers, consider upgrading to Apache Tomcat 7.0.53 or later which supports WebSocket.

Empty properties are not included in snapshot

History records are smaller and more efficient, because empty properties are no longer included in the snapshot. However, as a result, the history snapshot for sections might present a distorted view of the section.