Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

   Go here for previous versions.

What's new in case management 8.7

Updated on December 15, 2021

Case management features help you enhance the resolution of your cases by providing efficient, intuitive, and time-saving solutions. Key enhancements in this release of Pega Platform focus on connecting case types between remote applications.

Automatic references between cases

For greater transparency and clarity of relationships between processes in your organization, you can now create automatic references between cases. Bidirectional case references help you understand how cases are related and access related data, both during design-time and run-time experiences.

Now, when you add a field of the case reference type to the data model of your case type, Pega Platform automatically creates a corresponding field in the data model of referenced case types. As a result, you save time and take advantage of the low-code solutions that are available by default in App Studio, because you can conveniently view and analyze references between case types without the need to create advanced report definitions in Dev Studio.

The following figures show data models of Manage account and Offer opportunity case types with corresponding fields of case reference and query types, as well as a run-time representation of the configuration:

References between cases
Data models of two case types with references configured.
Case reference at run time
A run-time representation of case references.

For more information, see Referencing a case type.

Data initialization at case creation in App Studio

Save time whenever a new case starts by configuring a simple data transform that initializes data for a case type in App Studio. As a result, your application preloads information that you might need at run time, such as location, and uses it to complete the fields when the case starts. For example, a sales application can preload the city field to provide offers that are relevant only for the residents of a particular city.

This enhancement saves time for citizen developers because the system can initialize data and prepopulate fields in a case, and for customers, who receive targeted service without entering their details every time. You configure a data transform for a case type so that the application can initialize data for each new case by authoring a simple data transform in the case type settings in App Studio, as in the following figure:

Accessing the Data initialization landing page
Accessing the Data initialization landing page from the case type settings menu.

For each field that you want to prepopulate, you either set the value manually or select another field as the source of the value. To configure more advanced data transforms, you switch to Dev Studio directly from the Data initialization landing page.

For more information, see Initializing data at case creation.

Other enhancements

Read about minor enhancements in Pega Platform version 8.7.

Optional actions for resolved cases

You can now use a new checkbox to control whether an optional action also applies to resolved cases, so that you can, for example, help users can make corrections in the case regardless of the case status.

For more information, see Displaying optional actions conditionally and Reopening a resolved case.

Default data pages for case types

Case types can now define the default data pages that load the information that is required in case processing. In the case type settings, you can provide the data pages that are used to interact with a case type. For example, when multiple data pages load the same data object, you can define a default data page that an application uses to retrieve the data.

For more information, see Defining default data sources.

New licensing category for case types

You can now select a Work Dispatch licensing category for your case types to communicate that case processing occurs outside of an application. As a result, you comply with business and software agreements even in complex scenarios. By selecting a license category, you adjust collecting and reporting usage data in your system, so that you can demonstrate compliance with your software license agreement.

For more information, see Selecting a license category for a case type.

Creating cases from optional actions in Cosmos React applications

You can now conveniently create cases on demand directly from the Actions menu without losing the context of the current case. This enhancement enables more granular and flexible processing in your business processes.

For more information, see Creating cases from optional actions.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us