Enhanced performance of autopopulated properties
Valid from Pega Version 7.2
You can improve performance when accessing data from autopopulated properties that are defined by keys or parameters. If the properties were created in an earlier version of the product, run the pzReSaveAutoPopulateProperties activity to gain a performance improvement.
For more information, see Enhancing performance when loading autopopulated properties.
New types of steps in a process
Valid from Pega Version 7.2
You can add assignments, subprocesses, and preconfigured steps to a process in Case Designer. By using these new step types, you can quickly enhance your case life cycle and identify opportunities for reuse. This change also delivers a more consistent experience to users who are working in Case Designer and Process Modeler.
For more information, see Steps in the life cycle of a case.
Reusable components in a case life cycle
Valid from Pega Version 7.2
You can easily add an existing process or user action to the life cycle of a case type. By reusing functionality in your application, you can reduce the time that it takes to configure a case type.
For more information, see Steps in the life cycle of a case.
Process Outline view is unavailable
Valid from Pega Version 7.2
Process Outline view is no longer available as of this release. Use Case Designer instead to configure your processes. For advanced options, you can open the underlying flow for a process in Process Modeler.
For more information, see Designing a case type and Diagram tab on the Flow form.
Simplified creation of case types
Valid from Pega Version 7.2
You can create a case type in a single step, which enables you to process cases and use Case Designer immediately. Because some features are now extracted from the process of creating a case type, you can gradually add complexity at your own pace. For a guided experience of adding a data model or life cycle to your case type, follow the prompts in Case Designer.
For more information, see Adding a case type to your application.
Data modeling in context for case types
Valid from Pega Version 7.2
You can access the part of your data model that is relevant to your context. By using the Data model tab in Case Designer, you can quickly add, remove, or configure the fields that are used by an individual case type.
For more information, see Data models for case types.
Access views in one location
Valid from Pega Version 7.2
You can access the relevant views for your case type in one place. By using the Views tab in Case Designer, you can review and edit views that are used in your case life cycle. You can also configure standard views to quickly customize the fields that are displayed when a user creates, edits, or reviews a case.
For more information, see Views in a case type.
Offline support for mobile applications
Valid from Pega Version 7.2
You can work on assignments and create cases while your mobile device is offline. By enabling offline support for a case type, you can move cases closer to resolution while your application is disconnected from the network.
For more information, see Enabling offline for support for a case type.
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.