Published Release Notes

Escalation actions removed from case-wide goals and deadlines

The option to define an escalation action for a case-wide goal and deadline has been removed from Case Designer because the standard actions, Notify assignee and Notify manager, apply to assignments, not cases. You can still define escalation actions for goals and deadlines that apply to an assignment.

For more information, see Defining an escalation action for an assignment.

Support for Twitter data recovery

You can configure a Twitter data set to use the new playback option to recover tweets that the system could not retrieve during a period of time in which tweets were unavailable, such as during a data flow failure. You can specify the time period for which you want to retrieve Twitter data and enter the maximum number of tweets that you want to retrieve.

For more information, see Improved Free Text Model rule type.

Verify ML Readiness error: Upgrades from Pega 7.1.0 through 7.1.8 do not replace nonversioned rules

Upgrading from any Pega 7 Platform version between Pega 7.1 and Pega 7.1.8 to Pega 7.2 does not automatically replace nonversioned rules. If you revalidated and saved a Pega 7.1.x rule after the timestamp on the Pega 7.2 version of the rule, upgrading to Pega 7.2 does not overwrite the saved rule. You might see either of the following behaviors:

• The upgrade fails with the following error message:
  Verify ML Readiness
• The upgrade succeeds, but you might be unable to open changed rule forms.

If the upgrade fails, see the Pega 7 Platform Upgrade Guide to force the upgrade.

This known issue does not affect Pega 7.1.9. After the upgrade has finished, apply Hotfix 27288. For information about obtaining and applying hotfixes, see Hotfix Manager.

Flexbox layout mode for dynamic layouts

The flexbox layout mode is available for dynamic layouts and is now the default layout mode for newly created dynamic layouts. In a flexbox layout, sections contained within the layout can grow or shrink to fit the available space, providing a more efficient way to distribute space between items in a container. Existing dynamic layouts can be converted to the flexbox layout mode. You can configure the layout mode on the Presentation tab of the Dynamic Layout property panel.

For more information, see Dynamic Layout Properties — Presentation tab.

Harness settings container format includes option for no markup

The harness container format includes a No markup option. This option removes the non-semantic table tags from the container header, making it more consistent with current UX best practices. The No markup option is required for the new flexbox-based dynamic layouts to work correctly in Internet Explorer 11.

For more information, see Harness form — Adding a container.

Deprecation of override rulesets in run-time ruleset lists

Pega 7.2.1 is the last release where override rulesets can be incorporated in the run-time ruleset list. The ability to create override rulesets was originally deprecated in Pega 7.1. However, any override rulesets that were created in releases prior to Pega 7.1 in the application ruleset lists were still incorporated into the run-time ruleset lists at the appropriate location. In releases after Pega 7.2.1, override rulesets will be ignored and will not be incorporated in the run-time ruleset list. Therefore, it is recommended that you use production rulesets in access groups instead of override rulesets.

Time-based retrieval of Facebook posts

You can now control the amount of data that is retrieved from Facebook data sets by using the new search functionality for Facebook data set records. You can limit the retrieval of posts to any number of past weeks, days, hours, or minutes to get only the data that is relevant to your business objective or that you lost as a result of a system outage or failure.

For more information, see: Improved Free Text Model rule type.

Improved monitoring of data flow runs

To monitor the status, progress, and statistics of a data flow run, open it on the Data Flows landing page. Use the run and distribution details to report on data flow progress and possible service-level agreement (SLA) breaches. Run details are available at the node and partition level. Component-level statistics are available for the run, nodes, and partitions.

For more information, see the Data Flows landing page.

Support for advanced validation conditions for fields on a form

You can now create complex conditions to validate fields on a form to ensure that a step proceeds only when user input meets expected values. Use the AND and OR operators inside conditions so that the conditions can reference more than one field.

For more information, see Advanced validation conditions for fields on a form.

Support for advanced conditions on processes in a stage

You can now configure advanced conditions on a process in a stage to ensure that the process starts only when user input matches expected values. Use the AND and OR operators inside conditions so that the conditions can reference more than one field.

For more information, see Advanced conditions on processes in a stage.