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
Harnessfrom 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.
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.
Search field type is deprecated
Valid from Pega Version 7.1.9
The search field type in Form Builder is deprecated. Use a data reference or user reference instead, both of which prompt users with an autocomplete field at run time.
For the full list of supported field types in Form Builder, see Supported display modes by field type.
PegaDISTRIBUTION Manager (PDM) is no longer available
Valid from Pega Version 7.1.9
The PegaDISTRIBUTION Manager (PDM) is no longer available in the Pega 7 Platform. The related PDN articles and help topics have been archived.
Discontinued support for list view and summary view rules
Valid from Pega Version 7.2
The list view rule and the summary view rule are deprecated, and support for these rules has been discontinued. Existing list view and summary view reports will continue to work on supported browsers. However, the last version of Internet Explorer that list view and summary view rules support is Internet Explorer 11.
You cannot create new list view or summary view reports. Instead, create list reports and summarized reports by using the report definition rule. To prevent display issues, re-create the custom list view and summary view reports that you need as report definition reports.
Label changes to field types in Case Designer
Valid from Pega Version 7.2
The following field types have been renamed in Case Designer to be consistent with Data Designer and other areas of the Pega 7 Platform.
| Label in previous versions | Label in Pega 7.2 |
|---|---|
| Text | Text (single line) |
| Text (multiple lines) | Text (paragraph) |
| Check box | Boolean |
| Date and time | Date & time |
| Date | Date only |
| Drop down | Picklist |
| Number (integer) | Integer |
| Number (decimal) | Decimal |
Users who upgrade from versions prior to Pega 7.2 do not have to take any action because the label changes are cosmetic and do not affect the underlying controls or property types that support form building.
For more information about the field types that you can use when building a form, see Storage and display of single-value fields.
Process Outline view is unavailable
Valid from Pega Version 7.2
Process Outline view is no longer available as of this release. Use Case Designer instead to configure your processes. For advanced options, you can open the underlying flow for a process in Process Modeler.
For more information, see Designing a case type and Diagram tab on the Flow form.
New location for case-type settings
Valid from Pega Version 7.2
The configuration options for case-type settings have been moved from the property panel to the Settings tab in Case Designer. This change separates behavioral settings from life-cycle settings so that you can stay focused as you design your case types.
For more information, see Configuring case-type behavior.
No private posts in new Pulse gadget
Valid from Pega Version 7.2
The new Pulse gadget does not support private posts. When you upgrade to the new gadget, any private posts of the following types that you created by using the previous version of the gadget become public.
- Operator posts
- Case posts
- Posts that used the generic pxPostMessage API with private posts enabled
- Posts that used the Pulse smart shape in PRPC 6.3 or earlier with private posts enabled
For more information about the new Pulse gadgets for developers, Pulse gadgets and custom APIs.
For more information about the using the new Pulse gadget, see Communicating with Pulse.