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.

Tomcat log files moved to work directory

Valid from Pega Version 7.1.2

For Tomcat application server users, the default path for PRPC logs has been changed to the "work" directory for Catalina. For example:

<tomcat>\work\Catalina\localhost\prweb

This directory can be cleaned up during administration. To avoid loss of files, you can redirect logging to a different directory after installation:

  1. Navigate to the <tomcat-home>\webapps\prweb\WEB-INF\classes directory.
  2. Open the prlogging.xml file.
  3. Locate the "appender" definitions section that contains the "@{web.tmpdir}" string
  4. Update the FileNamePattern values to point to the new directory.

For more details, refer to the “Change the default path to PRPC logs” section in the Tomcat installation guide for your database.

Certain flow actions deprecated and replaced

Valid from Pega Version 7.1.7

To ensure compatibility with supported browsers and mobile devices and to enhance ease of design, the following flow actions are deprecated and replaced. As a best practice, use the replacement actions for new development. The deprecated rules are still supported and do not have to be updated.

DeprecatedReplacement
TransferTransfer Assignment
TransferAdvanced"
TransferToManager"
TransferToWorkbasket"
ApproveApproval
Reject"
AttachAFileAttach Content
pyAdjustSLAAdjust Assignment SLA
pyAdjustSLATimes"
pyChangeAssignmentSLA"
pyUpdate

Update Case

For example, the new Transfer Assignment action supports the most common routing options such as operator, workbasket, and reporting manager. Advanced options allow users to escalate, set due dates, update status, and provide instructions.

117841TransferAssignment1.png

Transform Assignment form

See Atlas - Standard Flow Actions (Local)​.

Service levels are available on stage steps

Valid from Pega Version 7.1.7

For greater flexibility when configuring stages, you can associate a service level (SLA) with a step within the context of the stage only. Because this SLA overrides the one associated (if defined) with a a step, other steps that employ the same flow are not affected and can be configured independently.

See Using the Stages & Processes tab.

Managers can create and update cases using the Bulk Actions tool

Valid from Pega Version 7.1.7

The capabilities of the Bulk Actions tool have been expanded so that managers can go beyond simply being able to make bulk updates to existing cases. They can now:

  • Create top-level cases for any case type in your application. By default, you can specify the label, description, and work status for each case.
  • Define the case information you want to display on the grid by overriding the section pyBulkUpdate and configuring the columns.
  • Update the case information you created in the Bulk Actions tool.

117851_BulkActions.png

Create Cases option in the Bulk Actions tool

See Case Manager Portal — How to process assignments and cases in bulk.

Define distinct names to implementation and framework class layers in Application Express

Valid from Pega Version 7.1.7

When generating both implementation and framework applications in Application Express, you can now name the framework application and workpool class layers independently. This eliminates the need to update a framework's class structure in the new application. Previously, the framework layers used the same names as the implementation and could not be updated.

117856_FWname.png

Class structure name fields in Advanced Configuration dialog

See Application Express — Advanced Configuration.

New case types contain one stage

Valid from Pega Version 7.1.7

When you create a new case type in the Cases Explorer or in Application Express, the system creates only one default stage. A single starting stage provides an intuitive design experience and eliminates the need to delete unused stages. Previously, a new case type contained three default stages.

Edit process-based case type flows in Case Designer Process Outline view

Valid from Pega Version 7.1.7

If your case type does not employ a stage-based design, you can now employ the Step Tree and other features available in Process Outline view to facilitate your design.

Click a process tile in the Stages & Processes tab to open the flow in Process Outline. In this example, the Graffitti report is selected.

117871SingleProcess11.png

Processes in Stages & Processes tab

The process opens in Process Outline view. Note that the tree view allows you to easily see and update the underlying shapes and subprocess that compose the Single Approval process.

117871SingleProcess22.png

Process in Process Outline view

See Using Process Outline.

Build contextual help for user interfaces with guided tour rules

Valid from Pega Version 7.1.7

The guided tour rule is now available, enabling you to showcase the key features on user forms or portals by providing users with information, instructions, or controls in a sequence of pop-up windows called tour stops. The rule allows you to configure the sequence, format, and location in which they are displayed. The content of each tour stop is defined in a referenced section.

118286GuidedTour_1.png

Guided tour rule form

This is what the users see when they click a control that links to the guided tour rule.

118286GuidedTour_2.png

Guided tour pop-up

See About Guided Tour rules.

Flow action and attachment category rule types moved to Process category

Valid from Pega Version 7.1.7

The flow action and attachment category rule types now appear in the Process category within the Record and Application Explorers. Previously, they were in the User Interface and Security categories, respectively.

Adaptive Decision Manager installation changes to support delayed learning

Valid from Pega Version 7.1.7

To support delayed adaptive learning, Adaptive Decision Manager (ADM) has been enhanced with database schema changes and no longer relies on Hibernate. This change has an impact in the way ADM is set up in the Decision Management service layer: the jdbc/admDataSource resource is now superseded by jdbc/adm7DataSource.

Additionally, Pega 7.1.7 further simplifies the ADM deployment by providing a single enterprise application or web archive:

  • Single EAR deployment archive that can used when deploying ADM on IBM WebSphere and Oracle WebLogic
  • Single WAR deployment archive that can be used when deploying ADM on Tomcat and JBoss

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