Native header with left and right actions for mobile apps
Valid from Pega Version 8.3
With Pega Infinity Mobile Client™, mobile apps can now use a native header with custom left and right actions for navigation. A native header standardizes the user experience of navigating between the screens of your app. For example, users can navigate to the previous screen with a swipe right gesture or the native back button.
For more information, see Enhancing a mobile app with the native header.
Mobile search with sources from any data page
Valid from Pega Version 8.3
When you configure search for mobile apps, you create custom categories that limit the scope of the search and group the search results. In the previous versions of Pega Platform™, you had to add specific properties to the data page that you wanted to use as a source for a search category. Now, mobile search categories support any data page without modifications to help you effectively configure mobile search.
For more information, see Configuring categories for mobile search.
Fast-track change requests for high-priority business needs
Valid from Pega Version 8.3
Perform urgent rule updates through fast-track change requests. The new type of change requests supports addressing high-priority business needs and deploying them immediately, without the need to disrupt an ongoing revision.
For more information, see Release urgent business rule updates through fast track change requests (8.3) and Creating application overlays.
Customizable fonts for the native components of the mobile app
Valid from Pega Version 8.3
The mobile app executable files now include font packages, which provides more flexibility in replacing and customizing the fonts. You can now style the native header and the bottom bar more effectively, and improve readability or branding. In native elements, both text and icons support custom fonts.
For more information, see Configuring a custom font for the bottom bar.
References to parameters in text control
Valid from Pega Version 8.3
The enhanced Text control now supports referencing the parameters in the Property field, and a more flexible application of the Field Value, that you can now use in the Value field. As a result, you can now use more development options, increase reuse, and more accurately reference specific data.
For more information, see Adding a Text control.
Pagination for repeating dynamic layouts
Valid from Pega Version 8.3
Repeating dynamic layouts now support pagination, so that you can display extensive sets of data in smaller portions. Additionally, you can add custom icons or messages to inform users whether more data is available.
For more information, see "Pagination" in Configuration options for layouts.
Faster starting offline-enabled mobile apps
Valid from Pega Version 8.3
Pega Platform™ and Pega Infinity Mobile Client™ now support access group data prepackaging when you build the executable files for an offline-enabled mobile app. This shortens the time needed to start a mobile app for the first time, because only the data that differs between the package and the current server state is synchronized. The data that is prepackaged comes from the access group cache, and you can decide what access group cache data should be excluded or additionally included in the package.
For more information, see Enabling access group data prepackaging during build.
More action types on the bottom bar
Valid from Pega Version 8.3
Pega Infinity Mobile Client™ now provides more flexible bottom bar configuration with a broader choice of actions, so that your apps can be more useful. For example, users can now create work items, open work items, or log out directly from the bottom bar of a mobile app.
For more information, see Configuring the bottom bar.
Change tracking tab removed from declare expressions
Valid from Pega Version 8.3
To simplify the configuration of a declare expression, the Change tracking tab has been removed from the declare expression rule form. To use the Change tracking tab, on the declare expression rule form, click Actions > Use legacy expression.
For more information, see Supported and unsupported configurations in simplified declare expressions.
Upgrade impact
The declare expression rules have been moved from the pr4_rule
table to the new pr4_rule_declare_expression
table.
The upgrade can fail if you customize the pr4_rule
table, such as increasing the length of an existing column.
After a successful upgrade, the declare expression rule form is simplified and lightweight pages support declare expressions.
What steps are required to update the application to be compatible with this change?
Read-only data pages by default are lightweight. You could also enable lightweight pages for:
- Editable data pages by selecting the Enable option in the editable data page rule form.
- For all pages in a REST service by using the Lightweight clipboard mode in the Service REST form in the Rest API service.
Only simplified declare expressions are supported in lightweight pages. In simplified declare expressions, context-bound rules are not supported. However, a page context could be specified on the New or Save As form of declare expressions. For more information, see Declare Expression rules - Completing the New or Save As form.
Redirectguests mashup configuration has been removed
Valid from Pega Version 8.3
The authentication/redirectguests server configuration and data-pega-redirectguests attribute have been removed and are no longer required when you configure a mashup. This prevents you from needing to maintain multiple nodes to support some use cases that require the configuration value to be true and other uses cases that require the configuration value to be false.
For more information, see Configuring the Mashup channel.