Low-code authoring of case pages
Valid from Pega Version 8.6
Mobile authoring for Cosmos React applications now supports the configuration of native mobile pages that include case details. Your mobile channel automatically generates these pages for each case type in your application. This enhancement improves the user experience in your app by providing users with native pages that you can adjust to best suit your business process. For example, you can highlight specific views on a page by modifying which tabs appear on the page, or add a floating action button to help your users edit the case.
For more information, see Authoring mobile case pages for Cosmos React applications.
In Pega Platform™ version 8.6, mobile features in Cosmos React applications are available only as a preview, with limited support for various interface elements and features, such as offline mode. The recommended production design system for Pega Mobile in Pega Platform 8.6 is Theme Cosmos.
For more information about the Cosmos React design system, see Cosmos React and UI architecture comparison.
Automatic packaging of cases for offline use
Valid from Pega Version 8.6
Newly created mobile channels now support automatic packaging of cases for use in offline mode. The packaging process includes case data from all native list pages that you create from offline-enabled case types and add to the navigation of your mobile app. Previously, automatic packaging was limited to assignments in the work list (and their related work items), and cases that were listed in the data page that you manually designated for packaging.
This enhancement improves the user experience for mobile app developers by ensuring that the data that is referenced in list pages for offline-enabled case types is automatically available for the users of your offline app.
Improved user experience for Cosmos React mobile apps
Valid from Pega Version 8.6
Mobile apps that you build for Cosmos React applications now feature a highly performant and responsive user interface that improves the overall user experience.
Native case pages
Prescriptive mobile case pages are now faster and more reliable. Mobile case pages display views and widgets as cards and group the cards into user-friendly tabs. Users can navigate the tabs by swiping left or right. From the case page, users can also edit case page details by selecting the floating action button, or choose an optional action from the case header drop-down menu.
To improve collaboration, prescriptive mobile case pages support the Pulse widget, as well as uploading, viewing, and downloading case attachments.
Improved case processing
The case processing interface on mobile devices is now more reliable and ensures a smooth experience for case workers. After users complete an assignment, Cosmos React apps display the task that is next in the flow that you define for the case type. Optional actions open in an overlay drawer component that users can minimize when they need to multitask while processing cases.
Form validation in real time
Validation of user input for mobile forms is now highly responsive thanks to real-time validation. To ensure that users enter data correctly, forms support validation expressions that you define in App Studio. Expressions are processed on the client side to further improve app performance.
Native Android and iOS controls
Cosmos React apps use a selection of native Android and iOS controls that make mobile apps faster and more intuitive to use. The native controls include map and location controls, date and time pickers, and controls for adding attachments.
In Pega Platform™ version 8.6, mobile features in Cosmos React applications are available only as a preview, with limited support for various interface elements and features, such as offline mode. The recommended production design system for Pega Mobile in Pega Platform 8.6 is Theme Cosmos.
Pinned classes in Application Explorer
Valid from Pega Version 7.1.6
The Application Explorer now includes a Pinned Classes section. This feature allows you to interact with a customized list of classes without having to explicitly switch context in the explorer.
Ability to deprecate a rule
Valid from Pega Version 7.1.6
You can deprecate any Rule- instance to indicate that it is no longer supported.
Users are warned when they open or reference a deprecated rule instance.
Ability to deprecate a class
Valid from Pega Version 7.1.6
You can deprecate any Rule- class to block users from creating new rule instances.
Users are warned when they open the class rule form or any instance of the class.
Designer Studio responds to deprecated rules
Valid from Pega Version 7.1.6
Deprecated classes and rule instances in Pega- rulesets are excluded from:
- Search results
- Application Explorer results
- Lists launched from the Records Explorer
- +Create menus
These restrictions do not apply to classes and rule instances deprecated in your application rulesets.
Retired Six R's
Valid from Pega Version 7.1.6
The Designer Studio > Application > Inventory > Six R's landing page has been retired.
Integration landing page updates
Valid from Pega Version 7.1.6
The following features and wizards now launch as landing pages in the Designer Studio:
Designer Studio > Integration > Tools > Wizard cleanup
Designer Studio > Integration > Email > Email Accounts
Designer Studio > Integration > Email > Email Listeners
Restructured Process & Rules landing pages
Valid from Pega Version 7.1.6
The Designer Studio > Process & Rules > Tools landing page menu has been restructured for better navigation and access:
- The Find Rules by Custom Field wizard now launches as a tab in Designer Studio.
- A new Find Rules menu item consolidates previous wizards. It launches a single landing page with different search criteria options: