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.
Relevant records to define reusable assets
Valid from Pega Version 7.2
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
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.
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.
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.
Processes run by default when a stage is restarted
Valid from Pega Version 7.2
The Run on re-entry check box in Case Designer has been removed. As a result of this change, processes run by default each time that a stage is restarted. Users who previously had this check box cleared can use the Start when option in Case Designer instead to define the criteria for skipping a process.
For more information, see Adding a process to a stage.