Published Release Notes

API enhancements to Manage Recents list

The existing Recent(s) API has been enhanced to provide the following rules:

• pzClearRecentItem: Clears a specific item

• pzClearAllRecentItems: Clears all recent items

Specifying read-only formatting

Read-only fields may be marked as an email, URL, or phone number in the Read-Only Format
settings.

Sort and filter columns with section includes

Column Properties include the ability to sort and filter columns that contain a section includes. A property for sorting and filtering may be specified in the Sort/filter property field. A date format for date or date-time properties can be configured to display in the filter popup.

Align column heading with column data

When the Align column heading with column data check box is checked, column headings are aligned with the data. When unchecked, the header may be aligned to the left, right or middle.

DB2-LUW database logfile size increase

To avoid running out of logfile space due to large transaction sets during the rule base load of a Pega 7.1.x install, upgrade, or maintenance level update, systems supported by a DB2-LUW database platform should increase the LOGFILSIZ parameter to at least 4096 pages from the default size of 1000 pages.

After the size has been increased, restart the database to ensure that the new setting is loaded into the database correctly.

Unable to drop triggers for frameworks with custom rule tables

For PostgreSQL and z/OS systems, if your deployment includes a framework or application with custom rule tables (such as CPM or any applcation built on CPM), upgrading to Pega 7.1.x causes the DDL application to fail when it tries to drop the following stored procedures:

• z/OS
  • SPPR_RULE_VW_UPDATE
  • PRPC_UPDATESCACHE
• PostgreSQL
  • sppr_base_uc_del.sql
  • sppr_base_uc_ins.sql
  • sppr_base_uc_upd.sql
  • sppr4_fv_ins
  • sppr4_fv_upd

During an upgrade, a number of stored procedures must be dropped and re-added. If the framework or application has custom dependencies that call the stored procedure, this problem is likely to occur.

To correct this issue, drop the framework’s custom dependencies before upgrading and add back the dependencies following the upgrade.

For instructions about how to drop and add the dependencies for your framework and database when this problem occurs, see Troubleshooting: PRPC 7.1.6 upgrade does not drop PRPC_UPDATESCACHE stored procedure.

Limited access for end user portals

The following portals are only accessible from supported versions of Internet Explorer in “quirks” mode:

• WorkUser
• WorkManager

Cannot copy final section rules in UI Kit ruleset

You cannot copy section rules in the UI Kit ruleset (UI-Kit-71) that start with pz or px (final rules in the base PRPC rulesets).

Instead, to customize these rules, use the Copy/Merge Ruleset tool, available at Designer Studio >System > Tools > Refactor Rulesets, to copy all rules from the UI Kit into your application ruleset. You can then check the section rules in and out.

Nesting dynamic containers not supported

Do not include a section containing a dynamic container inside of another dynamic container. This configuration may cause performance issues resulting in unexpected behavior at runtime, and is not supported.

Text Input control number type does not validate

When a Text Input control type is set to "Number" in the Presentation tab:

• Validation does not trigger and the field is blanked out when a user submits the form.
• If a value other than a number is entered, the browser sends an empty value, and the value is not validated.
• In the Clipboard, the field value displays as empty.
• If the field is required, the validation displays.

This issue occurs when using both the Chrome and Safari web browsers, and is a result of browser behavior for the HTML5 type=“number”. To fix this issue when using these browsers, do not use the "Number" type in Presentation tab of a Text Input control. Instead, the type should be set to "Text".