Custom database (DB) triggers are dropped during upgrade
Valid from Pega Version 7.1.8
The latest version of Pega 7 improves performance by no longer using database triggers to assist with System Pulse and Data-Rule-Summary processing, which is now done within the Pega 7 engine. As a result, DB triggers are no longer installed on either the pr_sys_updatescache or pr4_rule_vw tables.
When upgrading to the latest version of Pega 7, if you had previously implemented a custom database (DB) trigger on these tables, or a custom DB trigger that refers to these tables, it is removed during the upgrade process. No custom triggers are removed unless they reference these tables.
If you have custom DB triggers that reference the pr_sys_updatescache or pr4_rule_vw tables and perform other processing, those triggers must be reimplemented. When doing so, you must be careful to not modify the pr_sys_updatescache or pr4_rule_vw tables.
For more information, see Startup check removes custom DB triggers.
Identify, install, and manage hotfixes with the Hotfix Manager
Valid from Pega Version 7.1.8
Hotfixes are packages of files that address issues in Pega 7 and in participating Industry Applications. With Hotfix Manager, you can:
- Scan your system for installed and missing critical hotfixes and create a report that you can provide to Pegasystems Support for diagnostic purposes.
- Review the descriptions and contents of hotfixes.
- Install, rollback, and commit hotfixes.
- Manage hotfixes that include schema changes or require other special handling.
The Hotfix Manager replaces the Update Manager Hotfix Installer and System Scanner, both of which are deprecated. For more information, see Hotfix Manager identifies, installs, and manages hotfixes to Pega 7 and participating Industry Applications.
Enhanced product rule form for easy application packaging
Valid from Pega Version 7.1.8
The enhanced product rule form allows you to add applications in Delta mode, which includes only the patch version of the rulesets that comprise the application rule. You can also use Global exclusions to exclude one or more rules that are not associated with a ruleset version.
These enhancements allow easy packaging of non-versioned rules that are often deployed separately and reduce the need to manually add them later.
For more information, see Product rules - Completing the Contents tab.
Grid cascading filtering
Valid from Pega Version 7.1.8
At run time, filtering a grid by column yields accurate results as filter criteria cascade down when filtering by column heading. The filter panel displays only those values that apply based on other filter criteria. Values are filtered on both value and range.
Internet Application Composer mashup code generation
Valid from Pega Version 7.1.8
Case types can be added to an external web page by using the mashup code created in Case Designer. The mashup code is custom HTML that can be added to Internet Application Composer (IAC) codes.
The Actions menu in Case Designer includes the ability to automatically generate IAC HTML from a case type. The HTML is then copied and pasted into the target web page through standard IAC options.
The generated code is optimized for responsive web sites and responsive Pega applications. See Generating a mashup code in case configuration.
Edit application elements at run time by using Live UI
Valid from Pega Version 7.1.8
Live UI supports the addition, deletion, or reordering of UI elements within the run-time portal. Move elements by dragging and dropping within the tree. Elements can be added, deleted, and moved within or between dynamic layouts at run time by using Live UI.
Full-screen menus improve mobile navigation
Valid from Pega Version 7.1.8
A new full-screen menu setting for enhanced mobile functionality provides a smooth and seamless mobile navigation experience. Previously, regular drop-down menus were difficult to navigate on a mobile device. Select Component styles > Menus > Menu Bar > Display "Show Menu" as full screen menu to enable and configure this setting in a Skin form.
Personalize your dashboard with widgets and templates
Valid from Pega Version 7.1.8
New personalized dashboards can be customized and shared by end users. Select a default template or create your own. Choose from one of several default widgets or design a configurable widget to provide core business metrics to your users. From the new Settings tab, you can select whether a section is a template or widget.
Updated Rule-Utility-Function resolution
Valid from Pega Version 7.1.8
Rule-Utility-Function rules are now resolved based on ruleset.
Previously, if you had the same function @xyz() in different libraries in different rulesets, you could not call the function by using @xyz, because that would throw an exception.
The resolution process has since been updated so that rule resolution is now based on the highest ruleset in context. This update makes the function resolution process consistent with how rule resolution is performed for other rule types.
For more information, see Functions in expressions.
Define function input parameters on the Create or Save As forms
Valid from Pega Version 7.1.8
When creating or updating a Rule-Utility-Function ruleset in Designer Studio, use the Create or Save As forms to define or change parameters as a part of the form. The Parameters section on either of these forms allows you to set the function's name and Java type before opening the function.
Previously, you updated these fields on the Parameters tab for the function after the form was created. Moving these fields to the Create and Save As forms helps to proactively detect functions with the same signature in the same ruleset before saving the function.
For more information, see Defining function input parameters on the Create or Save As forms.