Advance cases from a push notification screen
Valid from Pega Version 7.3.1
You can now approve and reject Pega® Platform cases from your mobile device without opening a custom mobile app. Push notifications that you receive on a mobile device now display buttons that allow you to advance a case.
For more information, see Notifications.
Post Pulse messages to cases from a push notification screen
Valid from Pega Version 7.3.1
If your mobile device uses Android 7.0 or later, or iOS 9.0 or later, you can now respond to Pulse messages in Pega® Platform cases without opening a custom mobile app. Push notifications received on a mobile device now display a
button so that you can respond immediately to the notification.For more information, see Notifications.
Mobile optimized grid enhancements
Valid from Pega Version 7.3.1
Grid (table) layouts optimized for mobile support conditional visibility layout, row, and cell content. You can configure visibility as a client-run expression for use offline, or use a when rule or server-run expressions for desktop and mobile applications. Conditional visibility allows applications to use the template-based rendering. The UI Gallery includes an example of such a grid.
For more information see Optimize grid layouts for mobile.
Adjust styling for UI elements with standard CSS helper classes
Valid from Pega Version 7.3.1
Rather than creating a new skin format to make minor formatting changes to a user interface element, click the Open helper class picker icon on the Presentation tab of the Properties panel and select a predefined Cascading Style Sheet (CSS) helper class to apply to the element. For example, you can use a CSS helper class to center an element in a cell or layout. Using helper classes saves development time, reduces maintenance by limiting the number of customized skin formats, and improves the consistency of your application's look and feel. By avoiding the introduction of unnecessary static content, you also improve your application's initial loading time.
For more information, see CSS helper classes.
Preview and select icons with the icon class picker
Valid from Pega Version 7.3.1
To see the standard, predefined icons that are available for a Button, Link, or Icon control, use the Open the icon class picker icon on the General tab of the Properties panel. From an overlay of icons, you can then select the one that is most appropriate for your control. By using a predefined icon, you bring greater consistency to your user interface and help users more easily understand the purpose of each control.
For more information, see Previewing and selecting predefined icons with the icon class picker.
Update activity for button and link formats
Valid from Pega Version 7.3.1
To update existing Button controls or Link controls to current, simplified formats (Strong, Standard, and Simple), use the pzUpdateButtonLinkFormats activity. Using the report definition and other parameters that you specify, the system retrieves the sections to be converted, loops through each section rule to find Button controls and Link controls, and updates their formats.
For more information, see Updated button and link formats and Update-Button-Link-Formats.
Precision of Oracle Timestamp property when using RDB-Save
Valid from Pega Version 7.1.8
DateTime properties that are mapped to an Oracle Timestamp column will experience a loss of precision when they are saved using the RDB-Save method. When you use RDB-Save for an Oracle Timestamp, precision will be accurate to the second. For example, a value of 20171119T124745.006 will be saved as 20171119T124745. When you use Obj-Save, precision will be accurate to the millisecond. For more information, see DateTime property mapping in Oracle for Pega 7.
Changes to User Interface menu in Designer Studio
Valid from Pega Version 7.3.1
The Application readiness.
menu in Designer Studio has changed. For example, menu options related to localization are now grouped underFor more information, see Designer Studio - Landing Pages.
Internal rules in search results and explorers
Valid from Pega Version 7.4
Using old: is no longer supported in search. You can include internal rules in search results and make them available in the Application and Records explorers. Include internal rules in search results either by adding the PegaDevelopmentruleset to your application or by clicking the Enable diagnostic features option in your operator preferences.
Support for controlling binary file upload in Pega Mobile Client
Valid from Pega Version 7.4
The Client Store API of Pega® Mobile Client has been modified so that you can suspend and resume the process of uploading binary files to the server. You can also check the state of the file uploading process. As a result, custom mobile app users can process their work items without having to wait for the synchronization process to finish.
For more information, see Pega Mobile Client API methods for controlling binary data upload and Client Store API.