Improved view authoring
Valid from Pega Version 8.5
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.
Default views for cases and data objects
Valid from Pega Version 8.5
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.
Table toolbar functions
Valid from Pega Version 8.3
Optimized tables now support a table toolbar, that provides application users with the ability to adjust the data display to their needs. The toolbar conveniently groups several standard functions and custom actions. By using the toolbar, users can change the visibility of columns, group table data by fields, adjust the height of rows, and then save their personalized view. The toolbar is generated automatically, which provides a consistent design throughout your application.
For more information, see Configuring the table toolbar.
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.