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.

Maintainable warning, error, and tip information

Valid from Pega Version 7.1.7

Use the redesigned Message form to define warning, error, tip, or custom category information in your application. Encapsulating these details in a message makes them easier to maintain and review. After you have created a new warning, you can quickly add it to a rule in your application using the new pxAddGuardrailMessage function.

For more information on the tabs and available fields on the Message form, see About Message rules.

Easy-to-browse warning catalog

Valid from Pega Version 7.1.7

All Pega 7 warnings have been converted to Rule-Message instances, each with a clearly written, risk mitigation path. This allows you to use the Records Explorer to browse through all warnings in the system, organized by category. To view warnings associated with specific rules in your application, refer to the Application Guardrails landing page.

Communicate guardrail compliance with the pxAddGuardrailMessage function

Valid from Pega Version 7.1.7

Now that guardrail warnings are in the model, you can easily attach them to rules in your application using the new pxAddGuardrailMessage function. Call this function to display warnings to your application users when they do not adhere to guardrails or best practices. Adopting this function in your application allows you to:

  • Use localizable Rule-Message instances that are categorized by severity and application impact.
  • Add dynamic warnings to your rules by passing parameters to a standard or custom message.
  • Stop using and maintaining hard coded strings.

Design time view of warning messages

Run time view of an attached warning

This function supersedes the addWarning function, which has been deprecated. You can continue to use the CheckForCustomWarnings extension point, but it is recommended that you convert hard coded strings to messages and migrate any dependencies on addWarning to pxAddGuardrailMessage.

For more information on message attaching techniques, see Working with messages.

Track custom details with extensible messages

Valid from Pega Version 7.1.7

The customizable Message form gives you the freedom to expand upon default categories, store application specific data in a message, and enforce specialized validation. Leveraging these options makes it easier for you to identify a specific variety of message and incorporate new properties into your existing message processing logic.

For more details on which rules to override, see How to extend the Message form.

Collections more effectively model business decisions

Valid from Pega Version 7.1.7

Use the redesigned Collection form to model business logic or implement rule engine patterns in your application. This form is now located in the Decision rule category.

You can add response actions to each collection step to process return values transparently, and simplify your implementation by calling a function alias or when condition instead of an activity. Use one of the supported Stop methods to cease processing in the current collection or all collections in the call stack.

For more information on the available features on this rule form, see About Collection rules.

Achieve traceability through mapped rule type parameters

Valid from Pega Version 7.1.7

Maintain thorough audit trails of rules processed in your application by mapping one or more function input parameters to key parts of rules called by a collection. Each association you define updates referencing rules by linking the specified rule and the collection that calls your function or an associated function alias.

For instructions on how create these mappings in the Rule Type Parameters section of the Function form, see Function form - Completing the Parameters tab.

Display read-only formatting

Valid from Pega Version 7.1.7

When an editable field is in focus, date and text inputs display unformatted numerical values if the Display value using read-only formatting check box is selected. Unformatted text allows users to enter numerical values without adding currency symbols or decimal separators. The read-only formatting option appears for the Currency, Date Time, Integer, Number and Percentage control types when the Editable field is not in focus.

Simplified parameter passing with functions and function aliases

Valid from Pega Version 7.1.7

After you have mapped a rule type on the Function form, you can pass a parameter page to it from a corresponding function alias. This simplifies your implementation by exposing parameter prompting to users anywhere that function aliases are supported, such as collections and when conditions.

For a procedure on how to pass parameter pages to mapped rule types, see How to use parameter pages with a function alias.

New menu design options with the auto-generated menu control

Valid from Pega Version 7.1.7

Usability and responsive capabilities have been enhanced with a new auto-generated menu control offering multiple design options and configurations. New display options include text, descriptions, badges, and responsive vertical in-line menus. Loading options include:

  • At screen load
  • Defer load
  • On first use
  • On every use

Show menu controls for existing applications can be upgraded using the Upgrade Show Menu button in the HTML5 Readiness feature.

Menu created using the auto-generated menu control

Dynamic container improvements

Valid from Pega Version 7.1.7

Dynamic containers no longer take up excessive screen space when placed in a dynamic layout or in a section. Dynamic containers placed in a layout inherit the styling and positioning of the dynamic layout. Dynamic containers can also be dragged and dropped or copied and pasted between layouts.

Selecting the Size To Content check box when configuring a dynamic container resizes the container at runtime to fit the harness content.

Enable Dynamic container responsiveness with the Size To Content setting.

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