Published Release Notes

Offline mobility improvements

Several offline mobility improvements have been made in this release. Additional use cases have been added for configuring offline-enabled mobile apps at design time. Read-only grids with limited features are now supported offline. You can configure auto-populated properties, and you can create work with parameters. It is also possible to open work by handle. You can use decision shapes with Boolean expressions (no when rules) in screen flows. Barcode scanning is now available in offline mode.

Mobile user interface updates

Several improvements have been made to the mobile-related user interface of the Pega 7 Platform. The content of the Mobile tab on the Application rule form has been redesigned. The Offline Configuration and Mobile Certificates landing pages are now available. The Signature Capture control has improved. Post-processing can now occur after the signature has been captured. You can auto-submit with the form submit. You can apply the signature to a page instead of applying it as an attachment to the case. The clear action completely removes the signature from the work object, keeping only the latest iteration of the signature. Touch interactions have been significantly improved. Response time is faster and there is better feedback on the touch action.

No private posts in new Pulse gadget

The new Pulse gadget does not support private posts. When you upgrade to the new gadget, any private posts of the following types that you created by using the previous version of the gadget become public.

• Operator posts
• Case posts
• Posts that used the generic pxPostMessage API with private posts enabled
• Posts that used the Pulse smart shape in PRPC 6.3 or earlier with private posts enabled

For more information about the new Pulse gadgets for developers, Pulse gadgets and custom APIs.

For more information about the using the new Pulse gadget, see Communicating with Pulse.

Relevant records to define reusable assets

Relevant records describe the collection of rules that refine the behavior, presentation, and definition of a case or data type. They are commonly used to designate records from an inherited class as important or reusable in a child class.

Use relevant records to define information displayed in certain Pega 7 Platform application screens and fields. The Pega 7 Platform provides a number of items marked as relevant records, and you can further manage relevant records for your own case and data types.

For more information, see Relevant records.

Current parameter page can now be passed into activities, collections, and data transforms

In collection rules, you can now pass the current parameter page into an activity, data transform, or another collection when you call the activity, data transform, or collection from either a primary or a response action instead of setting up parameters before you call one of these types of rules. The Pass current parameter page check box is now supported on the Collection rule form.

For more information, see Rules and methods supported by a collection.

Improved modularity of case life cycles

You can add processes to a stage in the life cycle of a case. By organizing related steps into processes, you can design a life cycle that is modular and easy to reuse. This change also makes it easier for stakeholders to understand the flow of events when reviewing your case types.

For more information, see Modular life cycles for cases.

View external data entities in one location

The External Data Entities landing page provides a consolidated view of all the existing data entities in your product. You can access this page by clicking Designer Studio > Data Model > View external data entities. Use this landing page to identify the data sources that are readily available to use and the sources that need to be replaced with production data sources.

Enhanced data modeling

You can now create data types quickly in the Pega 7 Platform and in Pega Express. Use the enhanced Data Designer user interface to define the data model for your data types. More field types have been added, and they are categorized as simple, fancy, and complex to meet your data modeling needs.

For more information, see Data Designer enhancements.

Updates to the Authentication Profile rule form

You can now create OAuth 2.0 authentication profiles by using the enhanced rule form. For this profile type, you can select an OAuth 2.0 Provider data instance, a grant type, and the client information that you obtained from your OAuth 2.0 provider, such as Box or Facebook. You can also revoke issued access tokens on this rule form.

For more information, see Access protected API resources by using OAuth 2.0.

Authorization code grant for OAuth 2.0 providers

You can now connect to OAuth 2.0-protected APIs by selecting the authorization code grant type on the OAuth 2.0 Provider rule form. Enter the authorization code, access token, and revoke token endpoints as indicated by your OAuth 2.0 provider, for example, Box or Facebook.

For more information, see Access protected API resources by using OAuth 2.0.