Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Manage test ID access with an access group role

Valid from Pega Version 8.2

Test IDs for user interface components are available only to users who have the PegaRULES:TestID role added to their access group. This requirement allows administrators to limit access to test IDs to users who create or run tests. At run time, applications do not include the test ID data for users without the PegaRULES:TestID role, which reduces the amount of code that is downloaded to the client.

For more information see Managing Test ID access with an access group role

Improved clipboard performance for editable data pages

Valid from Pega Version 8.2

Improve clipboard performance for editable data page processing by using the new high-throughput mode option. This mode does not support all clipboard features.

For a list of supported and unsupported features, see Data page rules - Using the Definition tab.

Service Portlet rules are deprecated

Valid from Pega Version 8.2

Service Portlet rules are deprecated. Existing rules will continue to work, but you cannot create new ones. Use Pega Web Mashup instead. In addition, some changes might impact functionality. If you are using Portlet rules and plan to upgrade, contact your customer service representative.

For more information about Pega Web Mashup, see About Pega Web Mashup.

Deprecated metadata types in the Connector and Metadata wizard

Valid from Pega Version 8.2

The WSDL, SAP WSDL, and DTD metadata types have been deprecated in the Connector and Metadata wizard. For WSDL, use SOAP integration, and for DTD, use XSD.

For more information about SOAP connectors, see About Connect SOAP rules. For more information about XSD, see About the Connector and Metadata wizard.

Text file rules support the Google Closure Compiler

Valid from Pega Version 8.2

Text file rules support Google Closure Compiler as the default option for minification of JavaScript code. Minification reduces the size of JavaScript in text file rules for faster download. Access the Closure Compiler by selecting it in the Minification menu in a text file rule. For more information, see Text File rules - Completing the Main tab.

Support for the POST method in Integration Designer

Valid from Pega Version 8.2

From Integration Designer, you can now source data from any REST endpoint that requires a POST method to retrieve information. With the POST method, you can encrypt sensitive information in the body of the request.

For more information about using the POST method, see the POST method section on Service REST form - Completing the Methods tab.

Date range option added to DateTime control

Valid from Pega Version 8.2

The autogenerated DateTime control, used in forms, now features a custom date range option in the calendar picker. To specify a time period, click the From date and To date fields on an interactive calendar overlay. This input method is both convenient and mobile-friendly.

Enhancements to the AJAX container

Valid from Pega Version 8.2

It is now possible to set a document limit for an AJAX container, between 2 and 16 to control the number of documents opened by users. To reduce development time, you can also choose a new option to have no default view. The multidocument mode features tabbed navigation so that users can switch between open documents. A tabless container, on the other hand, includes an out-of-the-box navigation action for Home, which helps application users move within the portal.

For more information, see Configuring the AJAX container.

Moderate and severe guardrail warnings require justification

Valid from Pega Version 8.2

When checking in a rule, all moderate and severe warnings must be justified. Guardrail warnings now appear in a warning header when you save a rule that has warnings. Requiring justification encourages developers to address guardrail warnings. For more information see Application guardrails require justification.

 

Include region headers on forms

Valid from Pega Version 8.2

When you create or modify forms, you can now include region headers for sections that are based on design templates. You can enter a title for the region, select a container format for the header, add icons, and select styles. This greater flexibility enables you to create a more intuitive user interface.

For more information about modifying a design template, see Design templates.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us