Published Release Notes

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".

Need to run script before updating Multitenant systems

When updating or upgrading a Multitenant system from Pega 7.1.5 or 7.1.6 to Pega 7.1.7, if that system uses either an Oracle or a PostgreSQL database, you may encounter the error:

“Table must be empty to add column.”

The Multitenant architecture requires an additional column on a number of the PRPC database tables (“pzTenantID”). In Pega 7.1.7, two additional PRPC tables were tenant-qualified: pc_schedule_task and pr_index_schedule_task. The Multitenant column is added to these tables by the update/upgrade process. However, Oracle and PostgreSQL do not allow the addition of a non-null column to an existing table unless the table is empty, so updating or upgrading systems on those databases displays the error detailed above.

To avoid this error, before beginning the update or upgrade, it is necessary to run a script:

• Oracle — OracleMTupgrade.sql
• PostgreSQL — PostgresMTupgrade.sql

For updates, these scripts are located in the /scripts/ddl directory.

For upgrades, these scripts are located in the /Resourcekit/AdditionalUpgradeScripts directory.

Unclear error message when saving shared class instance in tenant layer

If you attempt to save a shared class instance from the tenant layer, Pega 7 displays this message:

This record has x errors. Save Failed: There was a problem saving an instance of class: Error Code: <none> SQL State: <none> Message: <none>

You cannot save a shared instance from the tenant layer if that instance cannot be overridden.

Node description cannot match application server node name

A node's Short Description should not be the same value as the application server node name. If the node's Short Description is changed to be the same value as the application server node name, then the node description is automatically changed back to the original value after a system restart.

Twitter data sets no longer supported

Twitter is deprecating several APIs, which will disrupt the Twitter data set functionality. Twitter data sets will not be able to fetch any tweets or direct messages. This issue affects all applications that use Twitter data sets to connect to social (mainly Pega Customer Service applications).

This change applies to the current and earlier releases of Pega Platform™ that make use of Twitter data sets and it impacts all environments, including Pixar, VM, and Pega Labs instances.

Twitter connectors will be fully functional at a later date. For now, the best practice is to de-emphasize social media in your data sets.

Semantic URLs in Pega Platform

URL addresses for Pega Platform™ applications and application resources now appear as clear, meaningful paths. This enhancement helps users understand the structure of the application that they are using, which makes navigation quicker and more intuitive.

Default views for cases and data objects

Pega Platform™ now generates default views for new case types and data objects. Because of this feature, your application now automatically creates a case summary and case details view for every new case type, and a list view for each data object. The default views automate a common recurring task, and improve productivity by reducing development effort.

Improved view authoring

Case authoring in Cosmos React UI now features updated view authoring tools. The redesigned view tab and overlay provide a more intuitive interface for creating views, applying design templates, and adding fields and controls. This enhanced work environment improves the user experience and reduces context switching, which contributes to a lower development effort.

For more information, see Editing views in a case type.

Enhanced tables in Cosmos React UI

The Pega Platform™ Cosmos React UI environment now includes improved tables. The updated tables use a revamped graphic design and support a number of new run-time behaviors, including column freezing and advanced filtering. The added features improve the user experience by giving case workers more control over data in tables, while the revised architecture enhances efficiency and reliability.

More intuitive portal authoring

Pega Platform™ now features an updated portal authoring interface that provides you with tools to edit landing pages, case pages, and portal settings all in one place. The interface also includes a live preview section that speeds up prototyping, encourages experimentation, and makes the authoring experience more user-friendly.

For more information, see Enabling Cosmos React UI for landing pages.