Published Release Notes

Logic-based assignment routing

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

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:

• Integration of desktop automations with your Pega 7 application
• Robotic Process Automation

Improvements to guided tour creation

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

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

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.

Unit testing support for more rule types

You can now create unit tests for the following additional rule types. You can also create assertions to validate activity status. The expanded rule types for unit testing enable developers to more thoroughly perform regression testing of their application, thereby improving application quality.

• Collection
• Declare expression
• Map value
• Report definition

For more information about unit testing rules, see Pega unit test cases.

Upgrade impact

With the four new rule types, unit test execution and unit test compliance metrics will change. Reports on automated unit testing of the customer application decrease due to the increased pool of supported rules.

What steps are required to update the application to be compatible with this change?

After a successful upgrade, create Pega unit test cases for the newly supported rules to see updated and accurate unit test metrics.

View application quality metrics by data type

You can now view application quality metrics by data type on the Application Quality landing page. The new Data Types tab displays metrics for data types grouped by data objects, which enables you to more quickly understand the overall coverage of the application's integrations and interfaces.

For more information about data type metrics, see Application Quality landing page.

Scenario tests are reusable

Existing scenario tests are now reusable in different business scenarios. Before Pega 8.3, you had to create a new test every time a user interface or process flow changed significantly. Now, scenario tests are editable to help you maintain the test stack more effectively.

For more information, see Updating scenario tests.

Business logic-based routing to process cases more efficiently

Process cases more efficiently by defining business logic-based routing options to route tasks to customer service representatives (CSRs) who have a specified availability or skillset. For example, you can ensure that a task is routed to a CSR with a high level of a German language if it is your business need. You can also create custom lists of operators and work queues to filter CSRs who can receive an assignment.

For more information, see Choosing an assignee at run time in Dev Studio, Choosing an assignee at run time in App Studio, Configuring business logic-based routing APIs.

Improvements for automated scenario testing

Test automation authors can group related scenario tests into suites. The scenario test suites can be run manually from the Scenario Testing landing page as part of purpose-specific tests such as smoke tests, regression tests, and outcome-based tests. Additionally, automation authors or release managers who monitor tests for an application can disable or quarantine unstable scenario tests so that they do not run.

For more information about creating and managing test suites for scenario testing, see Creating test suites for scenario testing.