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
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.
Use JDBC 4 compliant drivers for better performance
Valid from Pega Version 7.1.7
For better performance, ensure that you are using JDBC 4-compliant drivers. For more information on supported and non-supported JDBC drivers, please reference the Platform Support Guide.
Use Tomcat 7 for better performance
Valid from Pega Version 7.1.7
For better performance with a Tomcat web server, use Tomcat 7.
Tomcat 6 has a limitation that causes the server to treat the JDBC driver as if it were a JDBC 3-compliant driver, even if the system is using a JDBC 4-compliant driver. Customers using Tomcat will see better performance if they upgrade to Tomcat 7 and use a JDBC 4-compliant driver.
Engine will not start if the incorrect JDBC driver is used
Valid from Pega Version 7.1.7
The engine will not start up if the incorrect JDBC driver is used. The following configurations are unsupported:
- Using a Multi-tenant Oracle system with one of the Oracle JDBC drivers with issues (see the chart in the Platform Support Guide)
- Using a Multi-tenant system with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)
- Using Microsoft SQL Server with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)
When any of these unsupported configurations are encountered, Pega 7 will not start. Before this change, the engine would appear to start up properly, but would encounter issues during other parts of the engine startup or during actual use of the system.
List view and summary view reports might not display in HTML5-compliant browsers
Valid from Pega Version 7.1.7
List view and summary view reports use framesets to provide a view of drill-down reports. HTML5 does not support framesets, so these reports might not display well, or at all, in versions of browsers that are compliant with HTML5.
To prevent display issues, re-create the custom list view and summary view reports that you need as report definition reports. Standard management reports are already available as report definition reports.
As of Pega 7.2, list view and summary view rules are deprecated. For more information, see Discontinued support for list view and summary view rules.
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.
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.
Mobile optimized date and time controls
Valid from Pega Version 7.1.7
Date and time controls now support mobile browser-native date and time pickers on Android and iOS, making date and time selections easier for the end-user. This option is enabled in the Presentation tab of the Text input control Cell properties panel.
Native date and time selection on Android