Support for advanced validation of embedded and referenced data
Valid from Pega Version 8.5
To help you define validation conditions for a broader range of use case scenarios, Pega Platform™ now supports stage entry validation for embedded fields in the form of a validation matrix. You can now define validation conditions for both field groups and field group lists, and easily navigate between them. You can also select any fields and when conditions while building a condition for both field-level and stage-level validation.
For more information, see Validating field values for stage entry.
Complete email and notification approval in App Studio
Valid from Pega Version 8.5
App Studio now supports complete email approval configuration directly in the Case Designer. Email approval settings now include composing a new message or selecting a template, saving templates to a library for future reuse, and adding attachments to an email. Additionally, you can now send the approval as a push notification to mobile users. With full configuration of email approval in App Studio, you save time and create unique and personalized email messages and push notifications in a no-code, intuitive way.
For more information, see Obtain approvals from email and push notifications from App Studio (8.5), Requesting approval by email and push notification.
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.
Low-code styling in mobile apps
Valid from Pega Version 8.5
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
Valid from Pega Version 8.5
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
Valid from Pega Version 8.5
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
Valid from Pega Version 8.5
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
Valid from Pega Version 8.5
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
Valid from Pega Version 8.5
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
Valid from Pega Version 8.5
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.