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.
Child case queries performance can be slow
Valid from Pega Version 7.2
Some customers have reported that performance is slow when they execute queries on child cases. This issue is often indicated by PEGA0005 (query time exceeded limit) alerts that can be correlated to these queries in the logs. To resolve the issue, add a database index to each of your work tables by using a multicolumn index on the pxCoverInsKey, pxObjClass, and pyStatusWork columns.
See Performance improvements for child case queries.
Updates to the Data Page rule form
Valid from Pega Version 7.2
You can use the enhanced Data Page rule form to specify the name of a source system in the System name field in the Data sources section. This field represents the name of the system that is associated with a data source. For example, if your data source is a REST connector that connects to an external weather service such as Google Weather API, you can enter Google Weather in the System name field for the data source. The system name is used to display the source systems for a data type on the External Data Entities landing page.
For more information, see Viewing external data entities.
Verify ML Readiness error: Upgrades from Pega 7.1.0 through 7.1.8 do not replace nonversioned rules
Valid from Pega Version 7.2
Upgrading from any Pega 7 Platform version between Pega 7.1 and Pega 7.1.8 to Pega 7.2 does not automatically replace nonversioned rules. If you revalidated and saved a Pega 7.1.x rule after the timestamp on the Pega 7.2 version of the rule, upgrading to Pega 7.2 does not overwrite the saved rule. You might see either of the following behaviors:
- The upgrade fails with the following error message:
Verify ML Readiness - The upgrade succeeds, but you might be unable to open changed rule forms.
If the upgrade fails, see the Pega 7 Platform Upgrade Guide to force the upgrade.
This known issue does not affect Pega 7.1.9. After the upgrade has finished, apply Hotfix 27288. For information about obtaining and applying hotfixes, see Hotfix Manager.
Unused agents run in background
Valid from Pega Version 7.2
The Update PegaRULES database table statistics agent and the Collect PegaRULES database blob size statistics agent have been added to support future development. These agents run in the background, but they do not do anything. You can, but do not need to, disable them from the Edit Agent Schedule landing page.
For more information, see Agent Schedule form - Completing the Schedule tab.
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.
Support for Apache Cassandra
Valid from Pega Version 7.3.1
The Pega® Platform can now read data from and write data to an Apache Cassandra database. Apache Cassandra is a NoSQL database that you can use when a NoSQL database better meets your scalability and processing requirements.
For a list of supported and unsupported features, see Apache Cassandra support.
Apply logic to data import fields
Valid from Pega Version 7.3.1
When importing data from an external system, you can translate data fields into values that can be read by Pega® Platform. From the Import wizard, you can do the following actions:
- Apply a decision tree or decision table to the data that is imported for a field.
- Use imported data for a field to look up a value in another record. For example, you can look up the key of a record that uses an external identifier to populate a foreign key field.
- Create templates that contain business logic, which eliminates the need to handle data transformations manually during preprocessing.
For more information, see Transforming data during import.