New search option for optimized tables
Valid from Pega Version 8.5
Optimized tables now support the display of a search box at the top of the table. The new search option provides an efficient way to enhance tables with a convenient text-based search functionality without coding.
For more information, see Enabling search in a table.
Improved access to Cosmos UI settings
Valid from Pega Version 8.5
The Settings tab in the App Studio case designer now includes tools for configuring Cosmos UI. With this enhancement, you can adjust design system settings without the need to specialize individual When rules in Dev Studio, which simplifies UI creation and saves development time.
For more information, see Managing Cosmos UI settings in case designer.
Additional multistep forms in Cosmos UI
Valid from Pega Version 8.5
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
Valid from Pega Version 8.5
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.
Business logic routing of approval steps
Valid from Pega Version 8.5
Pega Platform™ now supports routing of approval steps by applying business logic, in both App Studio and Dev Studio. Business logic uses a set of conditions to determine the most appropriate worker to approve a case by routing the approval based on defined conditions. For example, in a loan request case, the application can route the approval step to a manager if the importance of the case is set to high. For greater accuracy, business logic can also use skill set, availability, and workload to determine the appropriate worker. With business logic routing, you increase work efficiency and speed up case resolution.
For more information, see Determine a relevant case approver by using business logic (8.5), Requesting approval from users.
Improved case auditing in App Studio
Valid from Pega Version 8.5
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
Valid from Pega Version 8.5
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
Valid from Pega Version 8.5
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
Valid from Pega Version 8.5
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
Valid from Pega Version 8.5
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.