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.
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.
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.
View external data entities in one location
Valid from Pega Version 7.2
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 . 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
Valid from Pega Version 7.2
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.