Improved Back button support in custom mobile apps for Android
Valid from Pega Version 7.4
In a custom mobile app for Android, you can press the Back hardware button to go back, instead of exiting the app. Custom mobile apps now function in the same way as native Android apps. For example, you can close a dialog box, dismiss an overlay, or collapse an expanded section by pressing the Back hardware button. On the home screen, pressing the Back hardware button displays a confirmation message before you can exit the app.
New data tables are non-Pega formatted
Valid from Pega Version 7.4
All new data tables are created as non-Pega formatted tables, that is, they do not contain a BLOB column, a pzInsKey column, or a pxObjClass column. The table's primary key will be the key that you specify, not pzInsKey. Data table construction was changed to improve performance of the Obj-Save method during batch operations, such as data imports, to make it easier to replace the table with an external system of record and to make it easier to share data among applications.
Browser unresponsive when logging in to Designer Studio
Valid from Pega Version 7.4
The What's new in 7.4 widget on the Designer Studio home page uses WebGL to render its background animation. If your browser is running on a virtual machine without hardware acceleration, your browser might become unresponsive because of this widget. Click the Hide this until next release button to remove the widget. At your next login, the widget will not be displayed.
Applications not working as expected when using fast processing for Connect REST and Service REST integration
Valid from Pega Version 7.4
In Pega® Platform 7.3.1, the Use fast processing option on Connect REST and Service REST rule forms did not work. The functionality has been fixed for Pega 7.4; however, some data model guidelines must be followed. If you use this option in Pega 7.3.1, and you did not follow the guidelines, your application might not work as expected after upgrading. Use the following data model guidelines when using fast processing:
- The JSON property names and the clipboard property names must match.
- The JSON tree structure and the clipboard tree structure must be similar.
- The scalar arrays in JSON must be mapped to the clipboard as page lists.
- Multi-dimensional arrays must be mapped into page lists of page lists with the same embedded property names.
In addition, page groups, value groups, and Java objects are not supported by fast processing.
Security fields in JFrog Artifactory repository do not work
Valid from Pega Version 7.3
The fields in the Security section of the JFrog Artifactory repository rule form, including the Secure protocol field, the Truststore field, and the Keystore field, were not implemented. In the Pega™ Platform 7.3 Designer Studio help, disregard the optional Security section in step 4 of the Configuring a JFrog Artifactory or Amazon S3 repository connection help topic, and disregard the optional Security section in step 5 of the Creating a repository configuration help topic in the 7.3.1 Designer Studio help.
Known issue: SAML IdP import uses only the last certificate
Valid from Pega Version 7.4
When you configure the identity provider for a SAML SSO authentication service, the backing keystore rule for the verification certificate is created with only the last certificate from the IdP metadata, instead of using all of the certificates.
Experimental high-speed data page support
Valid from Pega Version 7.3
An experimental implementation of high-speed, read-only data pages is available. This implementation is useful when data pages are used to hold static data that is used repeatedly. You can enable this feature for a specific read-only data page from the Load Management tab of the data page rule form by clicking Enable high-performance read-only data page. This feature does not support full clipboard page functionality; use with caution.
The following functionality is supported:
- Basic page and property access (read and write properties) for all normal data types
- Hierarchical data page structure (pages within pages)
- Dictionary validation mode
- Read-only data pages
The following functionality is not supported:
- Declarative rules
- Page messages
- Complex property references
- Saving pages to a database
- API access to the data page