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.
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.
Updated default system pulse processing settings
Valid from Pega Version 7.1.9
The default settings for system pulse processing have been updated in this release.
Upgrades to Pega 7.1.9 from a previous version of the Pega 7 Platform use database pulse by default. Database pulse synchronizes rule changes at a periodic interval across all nodes in a system.
New installations of Pega 7.1.9 use cluster-based pulse by default. Cluster-based pulse immediately updates rule changes across all nodes in a system after the changes are saved.
You can change the database pulse setting to the cluster-based pulse setting by updating the value attribute for initialization/pulse/transport
to "cluster" in the prconfig.xml file or in the Dynamic System Settings. Changing from database pulse to cluster-based pulse requires a full cluster restart after the changes are made.
For more information, see Pega-RULES agents.
Support for custom pre- and post-JavaScript processing for offline flow actions
Valid from Pega Version 7.1.9
Developers of an offline-enabled mobile app can execute basic business logic before and after a flow action is rendered by adding their own JavaScript code into a custom user scripts bundle. Its functions must be called within a try
/catch
clause. The JavaScript code, to be executed before a flow action is rendered, is always called afterClientCache is called and before DisplayHarness is called.
Conditional online and offline map display
Valid from Pega Version 7.1.9
The way an Address Map control behaves in a offline-enabled mobile app has changed. When a mobile app is online, a live Google map is loaded as expected. If the mobile app goes offline, a predefined image of a map is loaded instead.
Troubleshooting Pega Mobile Client on the login screen
Valid from Pega Version 7.1.9
An offline mobile developer can now troubleshoot issues that are not related to incorrect credentials when signing in to the Pega Mobile Client app. On the app login screen, an alert box displays where the user can click a link to examine current log files to troubleshoot the issue. The contents of the displayed log file can be filtered.
For more information, see Troubleshooting Pega Mobile Client.
New Pega Mobile Client debugging options
Valid from Pega Version 7.1.9
The Mobile tab on the Application form contains two new options: a check box for enabling debugging in the Pega Mobile Client app, and a drop-down field for setting the log level to one of the following levels: Silent, Error, Warning, Info, or Debug.
For more information, see Mobile settings reference.
Ability to view a PDF file while offline
Valid from Pega Version 7.1.9
Users of offline-enabled mobile apps can now tap a button to view a PDF file, regardless of whether the user is online or offline. The associated button, link, or icon must have a Run Script action defined that calls the pega.ui.pdf.view()
function with two parameters: applicationName
and pdfName
. The PDF file itself must be uploaded to a Rule-File-Binary rule.
For more information, see How to set up viewing of PDF file while offline.
Database storage used for passivation in High Availability mode
Valid from Pega Version 7.1.9
When an application is running in High Availability mode, the value attribute for initialization/persistrequestor/storage
in the prconfig.xml file or the Dynamic System Settings now defaults to "database."
Previously, applications running in High Availability mode required shared passivation, where either initialization/persistrequestor/storage
was set to “OnTimeout” or a custom passivation mechanism was used. The change to using database by default provides persistent storage for passivation, and provides control for the landing page for High Availability.
For more information, see Understanding passivation and requestor timeouts and the High Availability Administration Guide.