Conversion of single-step assignments is no longer required
Valid from Pega Version 7.2
You no longer need to create a single-step assignment in a case type and then convert it to another supported step type. Instead, you can use the + Add step option in Case Designer to add any step type directly to a process in a stage. This change delivers a more consistent experience to users who are working in Case Designer and Process Modeler.
The following table lists the step labels in Case Designer that were updated to support this change.
Step label in previous versions | Step label in Pega 7.2 |
|---|---|
| Single-step assignment | Collect information |
| Approval | Approve/Reject |
| Attachment | Attach Content |
| Case | Create Cases |
For more information, see Adding a step to a process in a stage.
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 My Teams page in Case Manager. 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.
Enhanced data modeling
Valid from Pega Version 7.2
You can now create data types quickly 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.
Support for rule rebasing
Valid from Pega Version 7.3.1
You can now rebase the rules on your development server with the most recently committed rules from a centralized system of record (SOR). For example, after rules are merged on the SOR, you can rebase your development application to refresh your application with the merged rules. Development teams working in two separate development environments can share their changes, keep their local rulebases synchronized, and reduce the probability of conflicts with other development teams.
For more information, see Rule rebasing.
Add new commands in the Facebook channel preview console
Valid from Pega Version 7.3.1
Now you can not only edit existing commands in the preview console for a Facebook channel but also add new command responses and associate them with intents. For example, you can add a new response command in the preview console in a case in which you entered a command and no response was found for the generated intent. This functionality gives you more control over the Facebook channel configuration and makes the preview console easier to use.
For more information, see Simulating a chatbot conversation.
Enhancements to PegaUnit test cases and test suites
Valid from Pega Version 7.3.1
Several enhancements have been made to PegaUnit test cases and test suites.
- You can now use advanced filters on the Automated Testing landing page and when you add test cases to a test suite to search for information.
- After you run a test case on the Edit Test Case form or a test suite on the Edit Test Suite form, the header now displays the expected and actual run-time values.
- You must now specify at least one assertion before you can save a test case.
- You can now compare a property to multiple values so that the assertion passes if any property meets the defined criteria.
- You can now use the is greater than and is less than comparators for date and date-time properties.
For more information about PegaUnit testing, see PegaUnit testing.
Execute Tests service now supports application name as a parameter
Valid from Pega Version 7.3.1
You can now use the application name and version as a parameter when running the Execute Tests service (REST API). When you build an application on Pega® Platform in a continuous delivery pipeline, you can use the Execute Tests service to validate the quality of the build by running PegaUnit test cases that are configured for the application.
For more information about the service, see Running PegaUnit test cases and test suites with the Execute Tests service in Pega 7.3.1.
Monitor application health on the Application Quality landing page
Valid from Pega Version 7.3.1
On the Application Quality landing page, you can view various quality-related data in one place so that you can monitor the quality of your application and correct any issues. The Application Quality landing page contains a summary of guardrails compliance, PegaUnit test coverage, and results of PegaUnit tests.
For more information, see Application Quality landing page.
View PegaUnit test reports
Valid from Pega Version 7.3.1
The Reports tab on the Automated Testing landing page contains tables and charts that display the percentage of rules on which PegaUnit test cases are configured, and the results of PegaUnit test execution. By looking at the data on this tab, you can see which tests failed and investigate them.
For more information, see Viewing PegaUnit reports.
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.