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.
Existing collections are deprecated
Valid from Pega Version 7.1.7
The original implementation of the Collection form is deprecated. Legacy instances in your application remain functional; however, any new instance you create uses the redesigned Collection form. Use the Decision category in the Records Explorer to view all collections available to you.
For guidance on upgrade limitations, see the Deprecated Collection form.
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.
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.
ShowWarningOnForm is no longer processed
Valid from Pega Version 7.1.7
Rule forms now display all warnings, independent of category or type. The standard decision tree Embed-Warning.ShowWarningOnForm is no longer used to determine which warnings are visible.
You can safely remove any specialized versions of this rule in your application.
Messages are rule resolved by class
Valid from Pega Version 7.1.7
As part of the Message form redesign, a class key part was introduced. While this key part is automatically handled as part of an upgrade or migration, it does change the available options you see in message SmartPrompts and how Rule-Message instances are rule resolved.
See Upgrade considerations for existing messages for more information.
The most current version of the engine code is used by default
Valid from Pega Version 7.1.7
Beginning in Pega 7.1.7, the "com.pega.pegarules.bootstrap.codeset.version.Pega-EngineCode" setting is removed from the prbootstrap.properties file. By default, Pega 7.1.7 uses the most current version of the code present in the system.
Improved cross-browser support
Valid from Pega Version 7.1.7
All rule forms are now harness-based and open in the work area of Designer Studio. This means that you can develop in the browser of your choice, free from pop-up distractions and incompatibility messages. Many rule forms have been upgraded to use the latest layouts, styles, and design best practices, giving you a consistent development experience.
Viewing a Word Template in Pega 7.1.7 compared with Pega 7.1.6
Previous restrictions still apply to any deprecated or custom rule forms in your application that remain form-based. Refer to the Deprecated features list for guidance on how to upgrade these forms and recommended alternatives.
Changes to archive.info in Pega 7.1.7
Valid from Pega Version 7.1.7
In Pega 7.1.7, the contents of the archive.info file have changed.
- In versions Pega 7.1.6 and earlier, the archive.info file displays the build number of the Pega installation.
- As of Pega 7.1.7, the build number no longer appears in the archive.info file.
In Pega 7.1.7, the archive.info file only displays a status message indicating whether or not the system is running, and the build number no longer appears. Instead, if the system is operational, the message “status=Running” displays in the archive.info file.
If there are any automated tests, scripts, or applications that rely on the archive.info file displaying the build number, those may fail and produce an error. It is recommended that any automation that relies on the build number displaying in the archive.info file be changed to look for the “status=Running” message.
Quickly see what's new in Pega 7.1.7
Valid from Pega Version 7.1.7
A new home page panel gives you centralized access to Help and the PDN, eliminating the need to leave Designer Studio. Use the buttons in this panel to learn about new features quickly and stay connected to product announcements.
What’s new panel as it appears on the Designer Studio home page
After you are finished reviewing new features and enhancements, you can dismiss the What’s new panel. This hides the panel from your operator in future sessions without impacting the home page for other application users.