New location for case-type settings
Valid from Pega Version 7.2
The configuration options for case-type settings have been moved from the property panel to the Settings tab in Case Designer. This change separates behavioral settings from life-cycle settings so that you can stay focused as you design your case types.
For more information, see Configuring case-type behavior.
Support for large reference data in offline mobile apps
Valid from Pega Version 7.2
A data page in a Pega 7 Platform mobile application with offline capability enabled can now be marked as a large data page. This feature improves performance significantly when you have a large amount of data in which only individual records change.
In this situation, after the initial sync to the mobile app, only the changes in the large data page are synced instead of the entire large data page. The database table is created for such large data pages in the encrypted SQLite database on the device. Changes such as add, delete, or update are reconciled as row-level updates. Furthermore, you can use JavaScript to query against this data. A large referenced data page is supported by list-based components such as repeating dynamic layout, auto-complete, a dropdown list, and radio button.
Support for offline and online cases in a single mobile app
Valid from Pega Version 7.2
A single offline-enabled application can now support both the creation and processing of online-only and offline-ready cases.
For online-only cases, a list of both the offline and online cases is always available. Case assignment and processing is performed on the server so that a case is available only when the device is connected to the Internet or to data. When a connection is not available for processing an online-only case, an error message is displayed.
For offline-ready cases, a user can open an assignment and perform tasks on that case. There is also an option to explicitly display a harness from a server instead of a client store.
Offline mobility improvements
Valid from Pega Version 7.2
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
Valid from Pega Version 7.2
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
Valid from Pega Version 7.2
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.
Improved modularity of case life cycles
Valid from Pega Version 7.2
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.
Quickly make a calculation based on a repeating field group
Valid from Pega Version 7.2
After you add a calculated (read-only) field to a form, you can create simple calculations that reference numeric fields within repeating groups. The expression can use common functions (Sum of, Average of, Minimum of, or Maximum of) or can be a custom expression.
For more information, see Calculations based on a repeating field group.
Add validation to fields on a form
Valid from Pega Version 7.2
You can now validate the values of single-value fields when you build a form. You can also provide messages that are displayed to users when any condition fails.
For more information, see Field validation on a form.
Cannot view all custom context posts in Pulse
Valid from Pega Version 7.2
When you use Pulse in a custom context, the custom context label is displayed as plain text instead of as a link that you can click to view all posts that are associated with the custom context.
For more information about Pulse, see the help topic Pulse.