Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

Customized application overview documents in App Studio

Valid from Pega Version 8.3

Keep stakeholders notified of the status of an application by customizing and generating an application overview document in App Studio. The overview may include information such as case types, roles, features in your application, and more. Select the chapters that you want to include in the overview, and then highlight the most relevant information by ordering the chapters. In addition to the application overview document, you can generate a detailed data model, either in Microsoft Word or Excel format.

For more information, see Creating project documents for stakeholders in App StudioExporting a data model into a document.

New send email automations and enhancements

Valid from Pega Version 8.3

You can now configure cases, flows, and activities to compose and send guardrail-compliant emails that conform to the MIME standard by using email automations. Use the new Call-Automation method to call an automation from an activity without writing Java.

You can also now categorize error messages in automations to quickly understand the type of error that occurred. In addition, page list data types are now supported for inputs and outputs in automations.

For more information, see Calling an automation from an activity and Viewing automations.

Java injection vulnerability check

Valid from Pega Version 8.3

Pega Platform™ now notifies you of Java injection vulnerabilities in activities, functions, and stream rules at design time and at run time.  You can customize Pega Platform to check for additional vulnerabilities to ensure that your application runs without problems.

For more information, see Configuring the Java injection check.

Usability improvements to Admin Studio

Valid from Pega Version 8.3

Admin Studio offers a variety of usability enhancements, including:

  • New access groups to differentiate between full and read-only access to Admin Studio
  • A Java class lookup utility
  • A requestor list for the logged-on operator
  • The ability to display system node type in the logs

Also, if your environment uses Predictive Diagnostic Cloud (PDC), the Admin Studio overview page now includes a link to PDC.

For more information, see Managing requestors.

More efficient navigation between applications in App Studio

Valid from Pega Version 8.3

The new My Applications gadget helps you switch applications in App Studio more conveniently. You can also search applications by name instead of choosing an application from the list, and then select the access role that you want to use. In addition, you can see descriptions of your applications and create an application by going to the My Applications landing page. To use the My Applications gadget, ensure that you update the UI Kit to version 14.

For more information, see Adding the My Applications gadgetSwitching between applications in App Studio.

Guardrails compliance score

Valid from Pega Version 7.1.5

The Application Guardrails landing page has been enhanced to help you build more guardrail-compliant applications. Increase transparency and accountability on your projects by responding to the following compliance score metrics:

  • A weighted compliance score (0-100) based on warnings, severity, and justification
  • A percentage of compliant rules in your application
  • Total number of rules in your application
  • Total number of rules in your application with warnings (justified and unjustified)

Additional metrics include alert and interaction count trends over the last four weeks.

For more information, see Guardrails compliance score.

Access Manager portal

Valid from Pega Version 7.1.5

Changes to the Access Manager simplify the process of modifying the access rights of features for an application. The changes, including creation of an Access Manager portal, make it easier for non-technical users, such as business architects, to set access rights even if they may not have a deep understanding of Pega 7's security model and class inheritance structure.​

Directed inheritance view in Application Explorer

Valid from Pega Version 7.1.5

You can now specify which inheritance model is used to populate classes in the Application Explorer. From the top level menu, use the “Explorer Inheritance” option to choose between:

  • Pattern: only display class names whose prefix matches the root node class name.
  • Directed: first display classes that explicitly name the root node as the parent class; then display classes with pattern inheritance.

108936_ExplorerInheritance.png

By default, the Application Explorer loads using Pattern inheritance. 

Save Application Explorer filter selections

Valid from Pega Version 7.1.5

Application scoping control selections made in the Application Explorer are now persisted between sessions. These preferences are stored in an operator record on an access group level. If you delete (and later re-add) an access group on your operator form, the application scoping control defaults to all layers selected:

109056_AppScopingControl.png

External access control DASS

Valid from Pega Version 7.1.5

A new Dynamic Admin System Setting (DASS) controls the Designer Studio's access to external systems, specifically the PDN RSS feed found on the home page.

By default, Pega-Desktop.AllowAccessToExternalSystem is set to TRUE. Update this setting to FALSE to hide the PDN RSS feed and ensure that no RSS fetch is performed.

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