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.

DCO

Valid from Pega Version 7.1.4

This release focused on improving the user experience of creating new rules and tightening up the use of specifications in the Case Designer.  The layout of the New and Save As forms were made more intuitive and intelligent.  Specification actions were made to be more consistent across various aspects of the Case Designer.

  • After removing specification references, users can create and save a new specification.
  • Developers may now choose either an existing specification or create a new one for subflows and Split-For-Each shapes.
  • If a specification is not associated with flow shapes such as sub flows, Utilities, or Split-For-Each, it is possible to import speciications with the same names, and the flow shapes will default to using those imported specs.
  • In the outline view, specification changes will be preserved when switching from tab to tab.
  • The View Full Details functionality from either Configure Step or the Outline View will display all details, including the specification requirement links.

Decision Management

Valid from Pega Version 7.1.4

This release contains a number of fixes that improve the configuration and execution of Batch decisions – specifically, a number of usability improvements and addresses some issues when creating strategies on IE8.  

  • Batch Decision functionality has been enhanced in the NBAM environment.
  • In NBAM, users can run the strategy execution batch based on the Seed list class instead of the customer class. 
  • Interaction data will now work even if Action or Organization  dimensions do not have values set.
  • Running a strategy which includes a Data Import of a structured page reference will work in batch mode.
  • Security was enhanced on the VBD Planner.
  • The Access of Role to Object rules have been enhanced to allow users to create new Dimension Operator records.
  • The NBAM Segment On Canvas will now fetch the SegMap data, even when the generated extended segment class has not been added to the Pages and Classes of the strategy.  The SegMap property will (if it exists) be added to a list of properties to fetch, even if the strategy indicates that it is not used.
  • When a strategy is defined on a customer class, users may now specify the list of required properties to fetch for the input definition.
  • When creating a new strategy, there is now a section to add a Strategy Results class like Business Issue or Group.

Designer Studio

Valid from Pega Version 7.1.4

Many refinements to the Designer Studio were made around performance and user experience. Based on feedback, we have made a number of bug fixes and strategic improvements that improve the overall user experience.

  • The Developer Portal connects to the PDN's RSS feed without needing a DigiCert certificate for validation. The RSS feed is just headlines; to open and read any of the articles, users will still have to log into the PDN.
  • Expression Builder has been enhanced to work with IE8.
  • New applications built in Version 7.1 will automatically redirect users to the PRPC login page upon logout. A new template has been added, to allow developers to customize their applications to redirect users to a logout page, if they wish.
  • Performance improvements were made when saving and validating rules.
  • Performance of the Guardrails Dashboard has been improved.
  • The display of circumstanced rules in Application Explorer has been enhanced.

Integration

Valid from Pega Version 7.1.4

Critical customer-driven product improvements were made to SOAP services, SOAP connectors and connector wizard, CMIS connectors, and the Pega Image Viewer. These fixes addressed a handful of functionality gaps discovered in PRPC 7.1 and earlier releases by internal and external customers.

  • A Connect-CMIS instance which was created using a reference to an ATOM Server Instance may now use Global Resource Settings.
  • The Execute Synchronously (one-way operation) has been enhanced for SOAP Services.
  • The Silverlight version of PegaImageViewer has been enhanced to print ranges of multiple pages at once.
  • The SOAP Wizard has been improved to show all the ports which are available in the WSDL file.
  • Two way SSL has been enhanced for the Connect-REST rule.

 

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.

System Management

Valid from Pega Version 7.1.4

Refinements were made to out-of-place upgrade documentation and processes, as well as for how handling is performed for all of the database vendor specific nuances related to a deploying into a split schema environment.

  • A script was created to run the data schema upgrade for z/OS systems.
  • In a split-schema configuration, indexing has been enhanced.
  • The product installer has been enhanced.
  • The stand-alone Static Assembly Utility does not require a password for its process.
  • The UpdateManager tool has been improved.

User Interface

Valid from Pega Version 7.1.4

This release had a focus around improving support for accessibility for all the PRPC UI Components as well as extending capabilities for responsive design with grids and tabs. A series of cosmetic changes and fixes are included.

  • Improvements have been made for action items being opened in a dynamic container.
  • Row repeat functionality in sections has been improved to better handle source properties.
  • Screen layouts have been optimized for the iPhone platform
  • The display on dynamic containers has been enhanced to provide the same behavior for both single-mode and multi-mode.
  • The Launch Harness feature has been improved to launch into a pop-up window.
  • The operator menu will now display from the Case Manager portal.
  • The Primary Page functionality has been enhanced for control-defined Repeating Tab Headers.
  • Using local actions defined as modal windows has been enhanced to work in an iPAD using a Safari browser.
  • When using a modal dialog to open a flow action in a repeat grid, to add an item to the list, users may now cancel out of this dialog if no changes are needed.

Application Express and the Content Security Policy

Valid from Pega Version 7.1.7

Application Express copies (if defined) the Content Security Policy (CSP) name (pyContentSecurityPolicyName) from the built-on application in a new application. It also sets the CSP mode (pyContentSecurityPolicyMode) to report. The values appear in the Content Security area on the application rule's Integration & Security tab.

When checking an application in the DCO Compatibility tool, a warning appears if the CSP name is missing.

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.

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