Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Business logic-based routing to process cases more efficiently

Valid from Pega Version 8.3

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.

Simple associations for quickly joining classes

Valid from Pega Version 8.3

Associations now have a simple mode. Use a simple association to quickly and easily join a class to another class. The simple association defines a left join, using a foreign key in the source class and the class key in the target class. Use an advanced association for all other conditions. In addition, simple associations are drawn in the Visual data model reporting mode to visualize the relationships that are available for reporting.

Upgrade impact

The new simple mode draws a map of where all the classes defined in the application rule are drawn as nodes. Relationships between the nodes that are defined by relevant properties are drawn as lines linking the two classes. This feature only includes Case and Data classes that are defined on the Application rule form's Cases and Data tab. It also only includes relevant fields for those classes in order to define the relationships from one class to another.

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

After a successful upgrade, add the data and case type classes to the application rule in Dev Studio to have the selected classes appear as a node. In addition, if you want a relationship to display as relevant, set the properties (of the class that defines that relationship) as relevant.

 

For more information, see Exploring the data model.

Association changes after upgrade

Valid from Pega Version 8.3

Associations now have a simple mode. Simple associations are those that join to only one class, use a left join, and have one filter condition to a class key in the target class. Existing associations that define a simple foreign key relationship are upgraded to simple associations when opened; all others are treated as advanced associations. All associations continue to work in reporting.

Making an association simple changes only one piece of metadata; all other data on the association rule is not affected.

Upgrade impact

The new simple mode draws a map of where all the classes defined in the application rule are drawn as nodes. Relationships between the nodes that are defined by relevant properties are drawn as lines linking the two classes. This feature only includes Case and Data classes that are defined on the Application rule form's Cases and Data tab. It also only includes relevant fields for those classes in order to define the relationships from one class to another. 

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

After a successful upgrade, add the data and case type classes to the application rule in Dev Studio to have the selected classes appear as a node. In addition, if you want a relationship to display as relevant, set the properties (of the class that defines that relationship) as relevant.

 

For more information, see Associations.

 

Task board enhancements for improved tracking of tasks

Valid from Pega Version 8.3

App Studio and end-user portals, such as Case Manager, now provide an enhanced task board which helps you improve collaboration on task resolution. For example, you can create a checklist within a task, and then update the checklist to inform other users about the progress of the task. Attach content to a task to ensure that all users have the information that they need, and to make tasks more meaningful. Now you can also categorize tasks, and then filter them by category, to quickly access relevant information.

For more information, see Monitoring and tracking tasks in Dev Studio, Monitoring and tracking tasks in App Studio.

Support for advanced validation of embedded and referenced data

Valid from Pega Version 8.5

To help you define validation conditions for a broader range of use case scenarios, Pega Platform™ now supports stage entry validation for embedded fields in the form of a validation matrix. You can now define validation conditions for both field groups and field group lists, and easily navigate between them. You can also select any fields and when conditions while building a condition for both field-level and stage-level validation.

For more information, see Validating field values for stage entry.

Complete email and notification approval in App Studio

Valid from Pega Version 8.5

App Studio now supports complete email approval configuration directly in the Case Designer. Email approval settings now include composing a new message or selecting a template, saving templates to a library for future reuse, and adding attachments to an email. Additionally, you can now send the approval as a push notification to mobile users. With full configuration of email approval in App Studio, you save time and create unique and personalized email messages and push notifications in a no-code, intuitive way. 

For more information, see Obtain approvals from email and push notifications from App Studio (8.5), Requesting approval by email and push notification.

Business logic routing of approval steps

Valid from Pega Version 8.5

Pega Platform™ now supports routing of approval steps by applying business logic, in both App Studio and Dev Studio. Business logic uses a set of conditions to determine the most appropriate worker to approve a case by routing the approval based on defined conditions. For example, in a loan request case, the application can route the approval step to a manager if the importance of the case is set to high. For greater accuracy, business logic can also use skill set, availability, and workload to determine the appropriate worker. With business logic routing, you increase work efficiency and speed up case resolution.

For more information, see Determine a relevant case approver by using business logic (8.5), Requesting approval from users.

Default Create stage in a case life cycle

Valid from Pega Version 8.5

Pega Platform™ now adds a default Create stage to a case life cycle every time you create a new case type, both in App Studio and Dev Studio. The default Create stage includes a view that users interact with to provide initial data before case processing begins. Consequently, you can now easily locate the view to make any necessary changes. In the background, the Create stage makes a case type independent from the starting process, which removes relevant advanced configurations and makes application development faster.

For more information, see Capture initial data faster with the default Create stage (8.5), The Create stage.

Case Management

Valid from Pega Version 7.1.3

This release had a focus on extending key capabilities to improve the ease of configuration based on early adopter feedback.  Improvements were made in run-time performance, especially in high volume situations with complex case configurations.  A series of cosmetic changes and fixes are included.

  • The Wait shape now supports dynamic references.
  • Issues were addressed with the CreatePDF and the CascadingApproval Smartshapes.
  • Attachments have been improved.
  • Issues with the Create Case Type functionality were addressed.
  • The Pega Pulse functionality has been improved, including its performance.
  • When auditing a work item, History is now the default tab.

Reporting

Valid from Pega Version 7.1.3

This release had a focus on extending key capabilities to improve the functionality and ease of use of reporting features based on early adopter feedback.  A series of cosmetic changes and fixes are also included.

  • Multiple boxes may be checked on List view checkboxes
  • Dashboard Charts slider has been improved.
  • Summary View reports and charts have been enhanced.
  • Column properties can be added to a report in the Report Editor.
  • List view column widths can be set by Smart Info.
  • Listviews will display correctly for updated systems.
  • Improvements to the GuardRail Report.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us