Published Release Notes

Automatically update dependent applications to use the latest versions of built-on applications

You can now automatically update dependent applications to use the latest versions of built-on applications. When you import an archive that you created from a product rule, you can update all dependent applications to be built on the latest application versions in the archive.

For more information, see Updating dependent applications with the latest versions of built-on applications.

Low-code styling in mobile apps

The mobile channel now supports enhanced low-code styling and branding of mobile apps. For example, you can customize app icons in three different ways: by uploading an image, by selecting from a list of font icons, or by using the default text-based icons. This enhancement helps you to conveniently customize the look of mobile apps to match the branding guidelines of your company and provide a consistent experience for users across different channels.

For more information, see Applying a custom theme to mobile apps.

Offline support for Cosmos-based mobile apps

Mobile apps that are based on the Cosmos design system now support offline mode. Previously, offline-enabled apps had to rely on the classic look. Now, you can use the low-code Cosmos solutions to design apps that operate reliably regardless of the connection status. 

For more information, see Designing apps for offline mode.

Removal of Pega Mobile Client 7

You can now use a single Pega Mobile Client™ that improves app performance, app development, and meets all your mobile needs. With the introduction of new functionalities for mobile apps, Pega Mobile Client 7 is removed in Pega Platform™ 8.5.

Upgrade impact

After an upgrade to Pega 8.5, you can no longer build mobile apps based on Pega Mobile Client 7, and existing apps based on Pega Mobile Client 7 no longer connect to Pega Platform. App developers can now configure mobile apps with Pega Mobile Client.

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

Existing clients that upgrade to Pega 8.5 are automatically switched to Pega Mobile Client.

Web portal reuse removed from the mobile channel

The reuse of web portals for creating mobile apps with a single web view is no longer supported. You can conveniently update your existing channels that reuse web portals to take advantage of the multiple-views experience and native mobile capabilities, such as native mobile list views or floating action buttons.

Upgrade impact

The Reuse web portal option is removed from Pega Platform 8.5 and later.

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

App developers need to use the migration tool available on the mobile channel to move their apps to the recommended new navigation designer. When users open existing mobile channel with the Reuse web portal option configured, they are prompted to run through the wizard to upgrade the mobile channel to the latest Pega Mobile Client based configuration. When this is done, app developers should rebuild the app.

Enhanced search in the mobile channel

The search configuration now includes up to three additional secondary fields, such as the case ID, category, cost, date, owner, and active channel. The enhancement increases the usability of search on mobile apps and provides more contextual information in the search results.

For more information, see Adding a search gadget.

Improved mobile channel user experience

Mobile channel authoring now includes two significant enhancements to the user experience. The new instant run-time preview makes security configuration more convenient. In addition, the offline tab is now present by default, to help you build offline-enabled mobile apps and complete assignments in areas with limited connectivity.

Enhanced swipe support for case actions

UI authoring in the mobile channel now offers more case-wide actions that can be performed by swiping on list items. For example, you can add a swipe action to attach an invoice to your expense work item. This enhancement increases usability and work efficiency as it allows for fast, instinctive mobile interactions.

For more information, see Designing a new mobile list page.

Alerts for long-running queue processor and job scheduler activities

Pega Platform™ now saves an alert in the performance alert log when a queue processor activity or a scheduled job runs longer than the configured threshold value. Use the alerts to identify potential performance issues with long-running processes.

The alerts are enabled by default. You can change the alerts for dedicated queue processors and job schedulers at the rules level. For standard queue processors, you can also set the threshold value for the Queue-For-Processing command in an activity. You disable the alerts in dynamic system settings.

For more information, see:

• PEGA0117 alert: Long-running queue processor activity
• PEGA0118 alert: Long-running job scheduler activity

Introduction of Search and Reporting Service

Pega Platform™ now uses Search and Reporting Service, which is an independent microservice. The new enhancement provides a convenient way to manage your application data, and is easier to maintain. For example, because of the cloud-based architecture of Search and Reporting Service, any bug fixes and performance improvements occur seamlessly, and have no impact on your overall experience in Pega Platform.

For more information, see Search and Reporting overview.