Logic-based assignment routing
Valid from Pega Version 7.2.2
You can now define business logic that controls when and by whom an assignment is processed in a case. By routing assignments to a specific user or group of users, you can help ensure that cases are resolved faster.
For more information, see Logic-based assignment routing.
Robotic Process Automation (RPA) support for Pega 7 applications
Valid from Pega Version 7.2.2
You can now use Robotic Process Automation (RPA) to automate repetitive and unattended back-office activities directly from your Pega 7 application. By using RPA with your application, you can batch process large volumes of cases faster and with fewer errors compared with manual case processing. You configure the automations in Pega Robotics Automation Studio.
For example, when an automobile insurance claim is submitted, an automation can analyze the submitted information, look up and verify policy holder information, and update web and desktop applications with case information.
For more information, see:
Improvements to guided tour creation
Valid from Pega Version 7.2.2
Usability improvements to creating and managing guided tours enable you to more efficiently create tours that introduce the key features of your application. Now, you configure the Manage guided tour action on a control to start, continue, or dismiss a tour, instead of specifying an API script.
For more information, see Managing a guided tour.
Upgrade utility for Get Next Work performance
Valid from Pega Version 7.2.2
You can run a utility to upgrade Get Next Work processing to more quickly process assignments that were created in versions of the Pega 7 Platform earlier than 7.2.2. Performance is automatically improved on new installations.
For more information, see Upgrading Get Next Work performance.
Create case and Wait smart shapes available in Case Designer
Valid from Pega Version 7.2.2
Two smart shapes have been added in Case Designer. Use the Create case smart shape in a case step to create another case, a child case, or multiple child cases. Use the Wait smart shape to pause the process of a case under specified conditions.
For more information, see Adding a preconfigured step to a process.
Class structure expanded for surveys and questions
Valid from Pega Version 7.3.1
You can now create surveys and questions at any class level. Because there is no longer a restriction on which class of flows can use the Survey and Question smart shapes, you can create more contextual surveys that reference embedded properties, or instances of classes, that you define outside the Work- class structure.
For more information about using the Survey or Question smart shapes in a flow, see Integration methods for surveys.
Locatable pages are deprecated
Valid from Pega Version 7.3.1
Locatable pages are deprecated. Use a data page instead. Data pages provide improved performance. When you save a rule that has a Locate Page Activity or when you create an activity of type Locate page, a guardrail warning is displayed indicating that this feature has been deprecated.
For information about data pages, see Data pages.
Like and bookmark Pulse messages
Valid from Pega Version 7.3.1
You can now like messages that are posted to Pulse and view the number of likes for each message. You can also bookmark the messages that you want to view in your activity feed.
For information about Pulse enhancements, see:
- Pega Express 7.3.1 – Communicating with Pulse
- Pega Platform 7.3.1 – Pulse enhancements for social collaboration
Real-time updates in Pulse
Valid from Pega Version 7.3.1
You can now view real-time updates of messages in Pulse. If a user posts a comment on a Pulse conversation while you are viewing the conversation, you receive a notification in real time, which you can click to refresh the conversation and see the comment.
For information about Pulse enhancements, see:
- Pega Express 7.3.1 – Communicating with Pulse
- Pega Platform 7.3.1 – Pulse enhancements for social collaboration
Conditional paths added to case life cycle
Valid from Pega Version 7.3.1
You can now add a conditional path to a process in the life cycle of a case. By defining the decisions that cause a process to follow different paths, you can create cases that support more than one outcome.
For more information about conditional paths, see Conditional paths in a case life cycle.