Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

Chrome support for editing specification descriptions in Word

Valid from Pega Version 7.2

If you use Google Chrome 42 and later, you can now create, save, and update specification descriptions even if you are not using the Microsoft Silverlight NPAPI plug-in.

The new Upload Word document as description option provides you with the functionality to upload a Word document that contains the specification description. In addition, you can use the Export to Word option to export the description that you entered in the rich text editor to a Word document.

Interact with cases from external applications

Valid from Pega Version 7.2

You can now achieve API case integration by using the Integration case-wide property to generate code that allows you to interact with cases from external applications. The Generate create case microservice code option for microservice APIs automatically generates code that is specific to your case type. This option complements the Generate mashup code option, which generates code that you can use to embed Pega 7 Platform content in another application's web page.

Connect to external REST APIs by using OAuth 2.0

Valid from Pega Version 7.2

You can now connect to external REST services that are provided by web applications, such as Twitter and Facebook, by using the OAuth 2.0 protocol client credentials grant. Your Pega 7 Platform application acts as an OAuth 2.0 client to access protected API resources. For example, you can connect to Twitter by using OAuth 2.0 to obtain a collection of tweets that match a specific query.

For more information, see Accessing protected API resources by using OAuth 2.0.

Access REST services and APIs by using OAuth 2.0

Valid from Pega Version 7.2

You can now allow external client applications to access REST services on your behalf by using the OAuth 2.0 protocol client credentials grant. The Pega 7 Platform acts as an OAuth 2.0 provider to grant trusted applications access to functions in Pega 7 Platform applications. Additionally, you can provide access to the Pega API by using OAuth 2.0.

Use multiple built-on applications to enhance ruleset reuse

Valid from Pega Version 7.2

Applications can now have multiple built-on applications, allowing rules to be reused as a part of a built-on application at run time while being developed independently at design time.

Previously, applications built in Pega 7.1 and earlier versions were assembled in a single linear application stack--one application built on top of another application, and so on. Attempting to reuse rulesets and frameworks across applications resulted in having to splice applications together, creating challenges when attempting to support the use of these custom created applications. Starting in Pega 7.2, applications are built on to other applications by using a hierarchical tree structure, and the Pega 7 Platform automatically converts this tree into a linear application stack.

For more information, see Using multiple built-on applications and the Ruleset behavior at design time section in Application stack hierarchy for multiple built-on applications.

Support for delegating map values, correspondence rules, and circumstances

Valid from Pega Version 7.2

You can now delegate map values and correspondence rules from the Actions > Delegate menu. In addition, you can delegate circumstanced types of the following supported rules and data types:

  • Map values
  • Correspondence rules
  • Paragraphs
  • Decision tables
  • Data types

Offline support for mobile applications

Valid from Pega Version 7.2

You can work on assignments and create cases while your mobile device is offline. By enabling offline support for a case type, you can move cases closer to resolution while your application is disconnected from the network.

For more information, see Enabling offline for support for a case type.

Relevant records to define reusable assets

Valid from Pega Version 7.2

Relevant records describe the collection of rules that refine the behavior, presentation, and definition of a case or data type. They are commonly used to designate records from an inherited class as important or reusable in a child class.

Use relevant records to define information displayed in certain Pega 7 Platform application screens and fields. The Pega 7 Platform provides a number of items marked as relevant records, and you can further manage relevant records for your own case and data types.

For more information, see Relevant records.

Current parameter page can now be passed into activities, collections, and data transforms

Valid from Pega Version 7.2

In collection rules, you can now pass the current parameter page into an activity, data transform, or another collection when you call the activity, data transform, or collection from either a primary or a response action instead of setting up parameters before you call one of these types of rules. The Pass current parameter page check box is now supported on the Collection rule form.

For more information, see Rules and methods supported by a collection.

View external data entities in one location

Valid from Pega Version 7.2

The External Data Entities landing page provides a consolidated view of all the existing data entities in your product. You can access this page by clicking Designer Studio > Data Model > View external data entities. Use this landing page to identify the data sources that are readily available to use and the sources that need to be replaced with production data sources.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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