Ability to include all properties in search results
Valid from Pega Version 7.4
You can now include all properties in a class in search results so that they can be used in report filtering. When the Enable search results for all properties option is selected on the Custom Search Properties rule form, all top level and embedded page scalar properties for the class are indexed and returned in search results, and all embedded page list, page group, value list, and value group properties for the class are indexed but not returned in search results. Selecting this option might affect performance.
In addition, by default, properties defined in the Data-Tag-RelevantRecord instance for a class are indexed and returned in search results and do not need to be explicitly configured.
You must reindex search after selecting or clearing Enable search results for all properties and after changing the properties that are defined in the Data-Tag-RelevantRecord instance.
For more information, see Specifying custom search properties.
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.
Support for large binary data item storage in Pega Mobile Client and offline case attachments in Pega Platform
Valid from Pega Version 7.4
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.
Improvements in the process engine for offline-enabled applications
Valid from Pega Version 7.4
The offline process engine includes several improvements. To provide more options when you develop an offline-enabled application, a decision shape as the first shape in a flow and parameters for the CreateNewWork action are now supported. Offline-enabled applications now also display information about the last data synchronization.
For more information, see Flow processing in offline mode.
Compact style sheet for creating PDF files
Valid from Pega Version 7.4
You can now use a compact style sheet when you create PDF files by using the Create PDF smart shape in a case type or when you use the HTMLtoPDF activity. This style sheet overrides the style sheet that is used by the harness skin and correctly renders certain elements such as headings and inline grid tables. It also renders PDF files more quickly.
For more information, see Creating PDF files by using a compact style sheet and PDF file rendering scenarios.
Touch response supported on mobile devices
Valid from Pega Version 7.4
When displayed on a mobile device, all active elements of the Pega® Platform user interface now respond to touch by changing their appearance. No additional configuration is available or necessary.
Setting a build version of the custom mobile app
Valid from Pega Version 7.4
When you build a custom mobile app, you can now configure a build version and leave the custom mobile app version unchanged. This way you can upload an updated custom mobile app to the Apple App Store and Google Play Store without having to increment the app version.
For more information, see Setting the app build version.
The worklist appears to be empty when you go back from an opened case in an offline-enabled mobile application
Valid from Pega Version 7.4
In a Pega® Platform offline-enabled application, when you go back to the worklist from an opened case, the worklist appears to be empty even though it contains cases. This issue will be fixed in the next release of Pega Platform. Only portals that use the key principles and design of the pyCaseWorker portal are supported in offline-enabled applications.
For more information, see Offline mobility guidelines.
Custom mobile app assets file validation at upload
Valid from Pega Version 7.4
When you build a custom mobile app, and upload branding assets or custom modules within a compressed file, Pega® Platform validates the file that you upload and displays confirmation and warning messages. For more information, see Uploading branding assets and custom modules.
New appearance of smart app banners
Valid from Pega Version 7.4
When you build a custom mobile app, you can use smart app banners to advertise your app. The look of these smart app banners has been modernized. Also, if you upload branding assets to customize the appearance of your custom mobile app, the smart app banners now display an icon that you upload as the main icon of your custom mobile app.
For more information, see Adding a banner for mobile app download.