Change logic does not work in Report Editor
Valid from Pega Version 7.1.2
The Report Editor change logic button does not work. As a workaround, use the rule form to change the logic.
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.
Real-time event processing
Valid from Pega Version 7.1.9
Real-time event processing is a mechanism that can be used to analyze a high velocity stream of events entering the system and derive conclusions from them. It is possible to define metrics, measurements, and conditions under which subsequent trigger events are generated.
For details, see Real-time event processing.
End of support for form-based rule forms in Pega 7.1.9
Valid from Pega Version 7.1.9
Rule forms that are configured to render as forms are no longer supported in Designer Studio or end-user applications. Form-based configurations are found on custom rule types that were created in earlier versions of Pega 7 and are characterized by pop-up windows that are rendered externally from Designer Studio.
Reconfigure Pega 7 applications that use such rule forms by using standard harnesses and sections.
- Open the class form.
- Click the Advanced tab.
- Select
Harness
from the menu. - Create a new harness and new sections that implement the logic of the custom rule, using standard user interface layouts and controls.
Migrating custom rule forms to harnesses and sections offers the following benefits:
- User interfaces become HTML5 WC3 compatible and responsive to different screen sizes.
- User interfaces become cross-browser compatible, rendered consistently in Google Chrome, Mozilla Firefox, Apple Safari, and recent versions of Microsoft Internet Explorer.
- Rendering performance on modern browsers is dramatically improved.
- User interface pop-up behavior is eliminated; all windows are rendered inside Designer Studio and end-user applications.
End of support for Microsoft Internet Explorer 8 and quirks mode applications in Pega 7.1.9
Valid from Pega Version 7.1.9
In accordance with Microsoft’s announcement to discontinue support for Internet Explorer 8 in January 2016, Pega 7.1.9 does not support Internet Explorer 8, nor does it support non-HTML5 standard user interfaces.
You must upgrade to Microsoft Internet Explorer 9 or later or use Google Chrome, Apple Safari, or Mozilla Firefox. If you are using Internet Explorer 9 or later, you must turn off compatibility mode by accessing the Compatibility View settings.
Note the following:
- Pega 7.1.9 does not support user interface rules that are not based on HTML5 standards (rules in quirks mode).
- If you use applications that are rendered in quirks mode, which enables Pega 7 to correctly display and render non-HTML5 standard user interfaces, you must update them to standards-based HTML5 user interfaces when you upgrade to Pega 7.1.9 or later. Pega 7 provides automated tools to help you migrate your applications.
- Pegasystems Global Customer Support will not investigate or fix any Pega 7.1.9 bugs or support requests that are exclusive to Internet Explorer 8 or quirks mode user interfaces.
You can quickly identify which components of your application user interface are not HTML5 standards-based by clicking
.Upgrading to Pega 7.1.9 and a newer browser offers the following benefits:
- These browsers are HTML5 and CSS3 compliant.
- New features are supported and existing features work as intended.
- The Pega 7 Platform user interface is displayed and rendered as intended.
- Browser security is enhanced.
If you have additional questions about browser support, see the Platform Support Guide or contact Pegasystems Global Customer Support.
Report Browser removed from Designer Studio
Valid from Pega Version 7.1.9
The Report Browser and Access landing page have been removed from Designer Studio. In Designer Studio, developers can create, edit, and test reports by using the Report Definition rule form.
The Report Browser is still available in the Case Manager portal.
Real-time pulse processing for multinode systems
Valid from Pega Version 7.1.9
Multinode development environments now use real-time pulse processing. Previously, when a change was made on one node, the pulse processing interval could take a minute or more for that change to be reflected on another node. Now, when a rule is changed on one node, that change is immediately reflected on all the other nodes in the cluster. This change helps to ensure that users are running a rule on the same node as where the rule was changed.
Verifying that a Pega 7 Platform instance is running
Valid from Pega Version 7.1.9
You can verify whether a Pega 7 Platform instance is up and running by entering this URL: http://<<hostName:port/contextName>>/PRRestService/monitor/pingservice/ping
The Pega 7 Platform Engine responds with HTTP Response Code 200 if the instance is available. The response contains JSON text in the format { "duration":"<time in milliseconds>" }. Any other response codes or timeout indicate that the instance is unavailable.