Published Release Notes

Additional multistep forms in Cosmos UI

The Cosmos design system now supports horizontal, vertical, and standard multistep forms. Multistep forms help you break a single assignment that captures many fields into multiple focused and concise screens. By providing a greater variety of formatting options, this enhancement gives developers more flexibility in UI design.

For more information, see Adding a multistep form to a stage.

Updated preview panel in Cosmos UI

The updated Cosmos design system now provides users with the tools to run common actions in the preview panel, without the need to open the case. In addition, you can now modify the preview panel in App Studio to adjust the buttons and tabs in the header. This enhancement creates a better user experience and accelerates case processing by reducing context switching.

For more information, see Adding tabs to the case details section. 

Improved case auditing in App Studio

In Cosmos UI, App Studio now supports expandable case steps. This enhancement helps users quickly navigate a case and provides deeper insight into the case flow. In addition, Cosmos UI also introduces an improved history view that helps you better meet your business auditing requirements.

For more information, see Managing Cosmos UI settings in case designer.

Upgrade impact

After an upgrade to Pega Platform 8.5 or later, the history and chevron designs change automatically. However, applications with custom history settings might still display the styling that you defined in the override.

What steps are required to update the application to be compatible with this change?

If your application uses custom settings and you want to use the updated history, remove the overrides from the pyWorkCommonActions rule.

Automatic separation of date input

Date fields in Date Time controls now automatically divide strings of input into days, months, and years. In single fields, the system adds slashes (/) as the user types the value. For example, an input string of 10102020 becomes 10/10/2020. In separate day/month/year fields, the system automatically switches from one field to the next as the user types the value. This enhancement improves the user experience by helping to users provide input in a more convenient and time-efficient manner.

For more information, see Configuring a Date Time control.

Spell-check support for multiple locales

The spell checker in rich text editors now supports selection of the language of input. In previous releases, the locale of the user determined the language that the spell checker supported. In this release, you can change the default language support by adding locales to the appropriate decision table. This enhancement increases versatility and convenience for users by ensuring grammatical correctness for the language of their choice without the need for external tools.

For more information, see Extending the spell checker to other languages.

Limits on active data flow runs

You can now configure a maximum number of concurrent active data flow runs for a node type. Set limits to ensure that you do not run out of system resources and that you have a reasonable processing throughput. If a limit is reached, the system queues subsequent runs and waits for active runs to stop or finish before queued runs can be initiated, starting with the oldest.

For more information see, Limit the number of active runs in data flow services (8.5).

Upgrade impact

If you have many data flow runs active at the same time, you might notice that some of the runs are queued and waiting to be executed.

What steps are required to update the application to be compatible with this change?

You do not have to take any action. After the active runs stop or finish, the queued runs start automatically. The default limits are intended to protect your system resources, and you should not see a negative impact on the processing of data flows. However, if you want to allow a greater number of active data flow runs to be active at the same time, you can change the limits. For more information, see Limiting active data flow runs.

Enhanced optimized tables

Optimized tables now come with a greater range of options, such as support for sorting and filtering cell content in embedded sections. The new options also include passing parameter values from a data page to a table instead of manually entering the values for each of the parameters. For example, you can mark an organization name as a parameter to pass into a table. The new enhancements facilitate the transition to the more efficient optimized tables, and save time and effort.

For more information, see Optimizing table code.

Improved support for working with cases in multiple browser tabs

The Cosmos design system now provides enhanced support for opening and working on cases in multiple browser tabs. Cases that users open in new browser tabs are processed independently and include the portal’s main navigation bar, which allows users to conveniently browse other pages on any tab.

Support for Apache HBase 2.1 and Hadoop 3.0

Support for these versions extends Pega Platform™ compatibility with HBase releases to ensure that your database implementations integrate seamlessly with Pega Platform.

Pega Platform now supports:

• Apache HBase 2.1 for the HBase data set
• Apache Hadoop Distributed File System (HDFS) 3.0 for the HDFS data set

For more information, see Enhance your data sets with Apache HBase 2.1 and Hadoop 3.0 (8.5).

Improved identification and handling of code assembly errors

Code assembly error logs are now more meaningful and help you identify root causes with better accuracy. Pega Platform™ now also invalidates erroneous assembly to facilitate successful reassembly when the code is accessed again. For example, if a section is not correctly assembled when a user first signs in to the system, the application attempts to reassemble that section the next time a user signs in. In this way, you can avoid lingering issues and improve stability.