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.

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.

Designer Studio

Valid from Pega Version 7.1.3

Numerous usability improvements were made for this release. A group of cosmetic, functional, and performance enhancements were also included.

  • Treegrid controls work more quickly in IE9 and IE10.
  • On application ruleforms, the 5.4 "Place Properties on Thread Page" checkbox will work in 7.1.
  • Message error handling has been improved.
  • Log messages have been cleaned up.
  • Connectors may now be used in Data Pages.
  • Move Rules wizard has been enhanced to work in Version 7.1.

Guardrails compliance score

Valid from Pega Version 7.1.5

The Application Guardrails landing page has been enhanced to help you build more guardrail-compliant applications. Increase transparency and accountability on your projects by responding to the following compliance score metrics:

  • A weighted compliance score (0-100) based on warnings, severity, and justification
  • A percentage of compliant rules in your application
  • Total number of rules in your application
  • Total number of rules in your application with warnings (justified and unjustified)

Additional metrics include alert and interaction count trends over the last four weeks.

For more information, see Guardrails compliance score.

Directed inheritance view in Application Explorer

Valid from Pega Version 7.1.5

You can now specify which inheritance model is used to populate classes in the Application Explorer. From the top level menu, use the “Explorer Inheritance” option to choose between:

  • Pattern: only display class names whose prefix matches the root node class name.
  • Directed: first display classes that explicitly name the root node as the parent class; then display classes with pattern inheritance.

108936_ExplorerInheritance.png

By default, the Application Explorer loads using Pattern inheritance. 

Service levels for case stages

Valid from Pega Version 7.1.5

Service levels are available for stages in stage-based case management applications.

The service level starts when a case enters a stage and stops when it exits. The service level is defined in the Service level for stage field on the "Stage Configuration" dialog, which is accessed on the Case Designer Stages and Processes tab.

108951_stagesla.png

Alternatively, you can add a stage service level on the case type record's Stages tab.

Customize your starting flow list

Valid from Pega Version 7.1.5

The Designer Studio Create menu now populates the list of starting flows by referencing the case types that you select (including case types in Create Menu checkbox) on the application form's Cases and Data tab. The order of the case types on the tab dictates the order of flows that appear on the menu.

108956_CreateCaseMenu.png

Previously, the Create menu displayed all starting flows in the current workpool. This new feature enables you to control which flows appear on the menu.

You can change the sort order by customizing the extension activity pySortStartingFlows. For example, you can sort the flows by their short descriptions.

Where-Am-I? includes stage and step progress

Valid from Pega Version 7.1.5

In stage-based case management applications, the Where-Am-I? display includes a read-only presentation of primary stage and step shapes. Green checkmarks indicate completed steps. A red arrow indicates the current step.

108961_whereami_0.png

Stop active processes on stage exit

Valid from Pega Version 7.1.5

The Change Stage smart shape provides a "Remove processes on exit stage" option that stops all active processes in a stage when a case leaves it. The system removes the stage's open assignments from user forms.

Standard page lists for attachments

Valid from Pega Version 7.1.5

The following new standard page lists allow you to easily reference attachments in your designs:

  • pyAttachments — Holds a list of attachments of the current case.
  • pyAttachmentCategoriesList — Holds a list of attachment categories of the current case. This property can be used to fetch the attachment information by category (pyAttachmentsByCategory).
  • pyAttachmentsByCategory — Holds a list of attachments for the category set in the pyAttachmentCategory property in the current case.

When a user or system adds an attachment, the system automatically associates the page lists with the case, and populates them when the properties are referred to.

Creating an attachment category in a case type record automatically creates a property reference. See Redesigned Attachment Categories tab on Case Type record.

In addition, you validate the existence of an attachment by referencing the new function alias pxIsAttachmentOfCategoryInCase in a validate record. For example, you can use the properties and a validate record for building when logic that makes it necessary for a user to attach a document of category "SECCompliance" before the case can enter a stage.

Redesigned Attachment Categories tab

Valid from Pega Version 7.1.5

The Attachment Categories tab on the case type record has been redesigned as follows:

  • In the Category field, you can associate case types with a case by selecting one in the application ruleset stack, or create a new one by typing a name in the field.

    When you add a category to the list and save the record, the system automatically generates a page list property that that can be used to easily reference attachments by category.

    ​In the example shown below, the page list property AuditComplianceAttachments can be used to access a list of attachments in the Audit Compliance category.
    108697_attachments1.png

For ease of use during your design session, you can access this functionality using the "Attachments" option on the Case Designer Details tab.

The new function alias pxIsAttachmentOfCategoryInCase checks if an attachment of a particular category is attached to a case.

  • Auto-Attach capabilities are deprecated but still supported. The tab displays a read-only list of attachments that were configured with this feature in previous releases.
    • To remove this capability, delete the item.
    • For new development, use the Attach Content smart shape in your process diagram.

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