Building custom mobile apps based on an explicit version of Hybrid Container
Valid from Pega Version 7.2.1
You can now lock the version of Hybrid Container on which your custom mobile app is built in Designer Studio. Locking the version helps avoid compatibility issues with the devices that are used in your organization. To lock the version of Hybrid Container, you must set the version in a .pyHCBuildVersion declare expression for a specific application.
For more information, see Building custom mobile apps based on a selected version of Hybrid Container.
Open cases in a mobile app with push notifications sent from Pega 7 Platform applications
Valid from Pega Version 7.2.1
Push notification smart shapes in a workflow of a Pega 7 Platform application can now send push notifications that open a case in a custom mobile app. Users working in the field can use this feature to instantly access priority assignments instead of having to search for changes manually.
For more information, see Configuring the Push Notification shape.
Improved security for clipboard pages
Valid from Pega Version 7.2.1
To prevent data leakage and inconsistency, the Pega 7 Platform does not allow properties on a clipboard page to refer to properties on pages with a lower scope. For example, an autopopulate property on a node type clipboard page cannot source data from a data page with scope “requestor” or “thread.”
For more information, see Page scope types for data and declare pages.
Store and source content in Box
Valid from Pega Version 7.2.1
You can now attach content from Box while working on a case in your application. You can attach files directly to your case or include them in a Pulse message. You can also store all the case and Pulse attachments in your application in Box. To enable content sourcing and storage in Box, configure the Content sourcing and Content storage sections on the Integration & security tab of your application rule.
For more information, see Storing and sourcing content in Box.
Cannot send mobile push notifications when the Pega 7 Platform is hosted on WebSphere Application Server
Valid from Pega Version 7.2.1
Push notifications are not sent to Android or iOS mobile apps when the Pega 7 Platform is hosted on WebSphere Application Server.
Show multiple views of data in your application
Valid from Pega Version 7.2.2
You can now show multiple views of data in your application by adding the record editor (pxRecordsEditor) section to a layout, another section, or a cell in a layout. You can configure the section to customize the display and enable the search, import, and export capabilities of the record editor.
For more information, see Multiple views of data in the record editor section.
Support for additional rule types for PegaUnit test cases
Valid from Pega Version 7.2.2
To compare the expected results with the results that are returned by running a rule, you can now create PegaUnit test cases for the following rule types:
- Activities
- Data transforms
- Strategies
- Decision trees
- Decision tables
After you unit test these rules, you can convert them to test cases and configure assertions on the test cases. You can also set up the clipboard with data before tests are run, and clean up the clipboard after tests are run.
For more information, see PegaUnit testing.
Page assertions are supported for PegaUnit test cases
Valid from Pega Version 7.2.2
You can now create page assertions for PegaUnit test cases. Because data transforms and activities can create or remove pages, you can configure page assertions to determine whether a page exists after you run PegaUnit test cases.
For more information, see Configuring page assertions.
Authenticate REST data sources by using OAuth 2.0
Valid from Pega Version 7.2.2
You can now authenticate the data sources that are created from your REST integration by configuring OAuth 2.0 authentication in the New REST Integration wizard. You can specify or create an OAuth 2.0 authentication profile in the wizard by using the client credentials or authorization code grant type.
For more information, see OAuth 2.0 in REST integration.
Pega Composite Gateway not required for Pega Web Mashup
Valid from Pega Version 7.2.1
The Pega Composite Gateway servlet (prgateway.rar file) is no longer required for Pega Web Mashup gadgets. You can now use web mashups without deploying the Gateway. Support for the Gateway will continue, but it is a best practice not to use it for the Pega Web Mashup in Pega 7.2.1 and later versions.