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.

Post files and links with pxPostMessage API

Valid from Pega Version 7.1.4

The pxPostMessageAPI now supports text messages, file attachments, and hyperlinks. You can programmatically update Pulse streams using this API from activities or SLA rules.

Case Management

Valid from Pega Version 7.1.4

This release has continued to focus on improving the functionality of the design environment with improvements to the Case Designer and stage configuration. Additional end user capabilities were also added to allow for processing a wider variety of cases, for those with and without stages and improved bulk processing handling.

  • Flow action processing now uses the primary page instead of the interest page when using case/stage local actions, so that embedded flows are properly populated.
  • Case-wide local actions rely on pzInternalStageFlow when there are no active, non-hidden assignments on the case. These case-wide local actions will now appear on a stage-less flow with no assignments.
  • If a (valid) error is displayed in the outline view, saving or clicking around will not delete the error - the error will remain as a reminder to the developer to solve whatever problem is being flagged.
  • May now add Cascading Approval validation and edit the parameters from the Case Designer Stage and Step page.
  • Page labelling ("Page 1 of X") appears in the history list presented in the audit tab.
  • The bulk processing feature has been enhanced.
  • The Outline View functionality was changed so that the visible page will no longer refresh each time a flow is edited.
  • The Post value was added to the instructions text field, so data isn't lost between nodes in the outline View.
  • When Assign to Operator or workbasket is included as a filter, the bulk processing gadget is supposed to get a list of assignments. The UI for the results was enhanced for assignments to include a column for instructions so that the different assignments on the same work item can be distinguished.
  • When designing a case type’s stages, it is no longer possible to skip the last stage (by using the "skip stage when" setting). When creating or editing the last stage, developers may no longer set a skip when rule; if tried, the system will display a warning and prevent that. If a Skip When rule is set up for a stage, and then all the intervening stages are deleted so that this stage becomes the last stage, the warning will display, and the Skip When rule will not be visible. If another stage is then added after that, the Skip When rule becomes visible again.
  • When one or more locked work objects are processed using the Process Selected Items button, the action will be performed on the selected work objects. If the action is successful, a green tick appears on the work object. If it is not successful, a red cross will appear.
  • When the topmost RuleSet in the RuleSet Stack is locked, customers may now open up Outline View by clicking "Configure Process Details" and make exploratory changes to experiment. Because the RuleSet is locked, these changes may not be saved, but the experiment can be tried.

Quickly create ad-hoc cases

Valid from Pega Version 7.1.4

The My Cases work area on the Case Manager portal introduces a Quick Create feature that lets users create cases and assign tasks that are not included in the processing of business cases (instances of case types defined in the Cases Explorer).  For example, a manager can create a case and a task to set up a phone conference with her staff, or a reminder to enroll in an online seminar. Users can also set up a series of tasks to represent all they work they need to do to accomplish a specific goal.

Reporting & Data

Valid from Pega Version 7.1.4

This release fixed many existing unlocalizable elements in 7.1 reporting interfaces (The Report Viewer, Report Editor, Chart Editor, and the Report Browser) and now they are fully localizable. Changes were made to make Listview, summaryview,  and report viewer display possible WCAG 2.0 level A and AA support.

  • Parameters may now be used in a sub-report join condition.
  • Report Definition localization has been enhanced.
  • Standalone ListViews with embedded SmartInfo have been improved to resize appropriately when the SmartInfo section is expanded.
  • The data section of a report will now display in all of the available space when a fixed header option is selected.
  • When localizing a listview with filters, tool tips are translated.

Easily configure the live and interactive map control

Valid from Pega Version 7.1.8

The AddressMap control has been enhanced with a text input field so that users can mark a location on a map.

For example, an insurance adjuster can indicate the location of the accident when filing a case. By selecting Allow marker repositioning to change address value and dragging the marker pin, the Text Input field is automatically updated.

Quickly attach a file to a case directly on a user form

Valid from Pega Version 7.1.8

In form configuration, the Attachment field type allows users to attach files directly to the form rather than performing an additional action.

For example, an insurance adjuster can take a photo of a vehicle and add the photo directly to the form. When the field type is configured as an attachment, at run time a new section is auto-generated with an attachment control that includes a read-only text input field and a browse button.

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