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.

Drag-and-drop functionality for lists and tables

Valid from Pega Version 8.3

Lists and optimized tables now support the reorganization of their content by reordering items. By configuring repeating dynamic layouts and tables to support drag-and-drop modifications, you enable users to move items between lists and within lists and tables. This enhancement ensures that you can create a flexible and dynamic user interface that helps users display and manage data.

The drag-and-drop functionality can also include custom actions that automate the processes that run when users move items.

For more information, see Configuring drag-and-drop functionality for lists and Configuring drag-and-drop functionality for tables.

Usability improvements to Admin Studio

Valid from Pega Version 8.3

Admin Studio offers a variety of usability enhancements, including:

  • New access groups to differentiate between full and read-only access to Admin Studio
  • A Java class lookup utility
  • A requestor list for the logged-on operator
  • The ability to display system node type in the logs

Also, if your environment uses Predictive Diagnostic Cloud (PDC), the Admin Studio overview page now includes a link to PDC.

For more information, see Managing requestors.

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.

 

Table toolbar functions

Valid from Pega Version 8.3

Optimized tables now support a table toolbar, that provides application users with the ability to adjust the data display to their needs. The toolbar conveniently groups several standard functions and custom actions. By using the toolbar, users can change the visibility of columns, group table data by fields, adjust the height of rows, and then save their personalized view. The toolbar is generated automatically, which provides a consistent design throughout your application.

For more information, see Configuring the table toolbar.

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.

Role-based page access in App Studio

Valid from Pega Version 8.3

App Studio now supports the management of access to pages in your application based on user roles. You can use this functionality to define which pages are visible for every role, for example, make an analytics page available only to an administrator.

For more information, see Configuring role-based page access.

Visual enhancements and native search in UI-Kit 14

Valid from Pega Version 8.3

In addition to general bug fixes, UI-Kit 14 provides new font icons and enhancements to support Pega Infinity Mobile Client™ apps, such as a default native search configuration for finding case data. The improvements reflect the latest design trends and Pega Platform™ UI capabilities. By using UI Kit's sample end-user UI styling and components, you provide a consistent user experience across your applications.

In addition, the UI-Kit 14 introduces the following changes:

  • The red triangle icon has been removed from error messages.
  • The color of the calendar icon is now consistent with other icons.
  • All caret down icons for auto-complete and multi-select lists use the caret-down.svg file.
  • Checkbox alignment has been improved with the reduction of the left margin by 1px.
  • The border-radius value has been reduced to 4px.
  • The background and box shadow for rich text editor have been removed.
  • The bottom margin for radio buttons has been removed.
  • The header height of the None container format has been changed to 50px.
  • The label font size has been changed to 14px.
  • The label and border color have been slightly darkened.

Tertiary AJAX container support

Valid from Pega Version 8.3

Harnesses can now contain up to three AJAX containers which helps you to use the screen area even more efficiently and effectively organize content on the screen.

For more information, see Adding an AJAX container.

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