Published Release Notes

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.

Field value inspector in Live UI

Easily identify and translate field values with the field value inspector. You can also use the field value inspector to validate translations and update missing or incorrect translations. The field value inspector is on the Localize tab of Live UI.

For more information, see Field Value Inspector.

Categorize repeating dynamic layouts

Rows of a repeating dynamic layout can be categorized by a property. Categorization is useful for creating date-based navigation or categorizing list items. You can also set the maximum height of a repeating dynamic layout in the Presentation tab of the repeating dynamic layout properties. You configure categorization on the Operations tab of the repeating dynamic layout.

For more information see Repeating dynamic layout - Operations tab.

Adaptive learning without using an interaction ID

When you configure the Strategy shape in a data flow to capture the response to previous decisions, you do not have to provide an interaction ID. Instead, during the process of adaptive learning, adaptive models can query the Event Store data set over a specified period of time to retrieve decisions that were made for each response. This way, you eliminate the need to store the interaction ID on the client side.

For more information, see Delayed learning of adaptive models.

Flexbox-based dynamic layouts not supported for Android 4.4 and earlier

Flexbox-based dynamic layouts are not supported in Android 4.4 and earlier. When developing applications to be used on devices running Android 4.4 and earlier, use the inline-block layout mode for dynamic layouts.