Published Release Notes

Semantic URLs in Pega Platform

URL addresses for Pega Platform™ applications and application resources now appear as clear, meaningful paths. This enhancement helps users understand the structure of the application that they are using, which makes navigation quicker and more intuitive.

Loading cues in Pega Platform

Pega Platform™ applications that rely on the Cosmos React framework now feature a visual placeholder for the page that is being loaded. The system displays an indicator when loading portals, cases, simple pages, and list pages. This update provides users with a visual cue that their request is being processed, which improves the user experience.

Cosmos React UI is now available in Pega Platform

Pega Platform™ now provides you with tools to develop React-based applications in App Studio. This enhancement, which was developed as part of Project Fnx, uses components that rely on the ReactJS library to power the Cosmos design system. The updated UI technology improves application performance, creates a better user experience, and provides greater flexibility for front-end developers by drawing from a well-established open-source technology.

In Pega Platform 8.5, Cosmos React UI is an opt-in beta. For more information about using Cosmos React UI in your application, see Previewing Cosmos React UI.

To learn about Project Fnx, see Project Fnx.

Legacy rules removed to reduce Pega Platform installation size

The installation of Pega^® Platform 7.4 removes deprecated and unused rules. The smaller installation size decreases rule sync time and reduces the amount of storage required for Pega Platform. In addition, the smaller installation reduces the rule database size and shortens installation and upgrade times. You can access the legacy rules, if needed, in the PegaLegacyRules:01-01-01 in the Resource Kit on the Pega Platform media.

For more information see Finding legacy rules in sections.

Support for multiple custom mobile apps for a Pega Platform application

To enhance the user experience and provide support for native mobile components, you can create multiple custom mobile apps for a Pega Platform™ application. For each custom mobile app, you must create a different mobile channel interface. In addition, you can configure each custom mobile app to run only in a specific portal for an application. The custom mobile app uses this portal regardless of which default portal is defined for the access group.

For more information, see Selecting a portal for a custom mobile app.

Support for large binary data item storage in Pega Mobile Client and offline case attachments in Pega Platform

Pega^® Mobile Client can now store and synchronize large binary data items and their corresponding actions from the action queue on Android and iOS devices. As a result, custom mobile app users can view, attach, and delete data files, whether the device is online or offline. For this function to work, you must enable offline case attachment support, which allows your custom mobile apps to synchronize case attachments between the Pega Platform and the mobile device.

For more information, see Enabling offline case attachments support and Client Store API.

Open cases in a mobile app with push notifications sent from Pega 7 Platform applications

Push notification smart shapes in a workflow of a Pega 7 Platform application can now send push notifications that open a case in a custom mobile app. Users working in the field can use this feature to instantly access priority assignments instead of having to search for changes manually.

For more information, see Configuring the Push Notification shape.

Cannot send mobile push notifications when the Pega 7 Platform is hosted on WebSphere Application Server

Push notifications are not sent to Android or iOS mobile apps when the Pega 7 Platform is hosted on WebSphere Application Server.

Tab groups are deprecated

Beginning with Pega 7.3, tab groups have been replaced with layout groups, which offer better performance and flexibility. Tab groups are based on the Yahoo User Interface (YUI) library, which is no longer supported on the Pega 7 Platform.

User interface rule forms now use layout groups instead of tab groups to place layouts in forms.

For more information, see Adding a Layout Group.

PegaWAI ruleset deprecated in 8.5

Accessibility functions that were contained in the PegaWAI ruleset are now integrated into the main Pega Platform™. Consequently, the user interface in your applications now features accessibility functions out of the box, so you no longer need to use the PegaWAI ruleset to ensure accessible behavior in your application.

For more information, see Building an accessible UI.