Current parameter page can now be passed into activities, collections, and data transforms
Valid from Pega Version 7.2
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.
Team management
Valid from Pega Version 7.2
As a case manager or manager of a team, you can manage all your teams and direct reports on the Team management landing page. You can create teams or delete existing ones, as well as update team membership and work queues assigned to the team. You can also update and manage workload, time off, and skills information for individual team members. Social collaboration through Pulse is also available for both teams and individual users.
For more information, see Managing team information and work queues.
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.
New Pulse gadget for users
Valid from Pega Version 7.2
You can use Pulse to communicate and collaborate with other users. For example, in Pulse you can post messages, share files, search for content, and view an activity feed on your dashboard that aggregates your Pulse posts.
For more information, see Pulse for social collaboration.
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.
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 Viewstab 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 properties
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.
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.