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.

Data synchronization does not resume after mobile app restart

Valid from Pega Version 8.3

If an offline-enabled mobile app that you build with Pega Infinity Mobile Client is stopped during an initial data synchronization session, the data synchronization does not resume when the mobile app is restarted. Users must not stop the mobile app before initial data synchronization finishes.

For more information about data synchronization, see Offline capability and Guidelines for creating an offline-enabled application.

Search and Reporting does not index large items

Valid from Pega Version 8.5

When using the Search and Reporting (SRS) microservice in Pega Platform™ 8.5, you might encounter problems with indexing large out-of-the-box rules. The issue is not visible in Queue Processors, but you can access logs to verify which items the system does not index.

Change logic does not work in Report Editor

Valid from Pega Version 7.1.2

The Report Editor​ change logic button does not work. As a workaround, use the rule form to change the logic.

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.

Source field not displaying in data transform

Valid from Pega Version 7.1.4

On the Data Transform rule form when using the Update Page action, if the Relation value is updated to “with values from”, the Source field will not be displayed.

(Note that for existing data transforms where the Source field has already been completed, this situation should not occur.)

Workaround

  1. Below is a data transform that has been configured to use Update Page.
    DataTransform1.jpg
  2. If a user were to choose an alternate source by updating the ‘with values from’ Relation value, they would not be prompted to provide a page name in the Source field.
    DataTransform2.jpg
  3. At this point, to be able to enter the Source page value, the user has to save the rule, which results in an error because the source page value is blank. This causes the field to appear.
    DataTransform3.jpg
  4. Once the field has appeared, the Source page value can be provided, and the form can be saved successfully.
    DataTransform4.jpg

Required Oracle optimization parameter

Valid from Pega Version 7.1.3

To optimize performance, set the Oracle parameter optimizer_index_cost_adj to a value between 20 and 25. If this value is not set, the system can run exceedingly slowly, potentially blocking users from login.

Slow WebSphere performance on Mac platforms

Valid from Pega Version 7.1.2

Use the following JVM setting to improve WebSphere performance on Mac platforms:

-Djava.net.preferIPv4Stack=true

Synchronized database and application server settings

Valid from Pega Version 7.1.3

Configure your database and application server to use the same time zone and character encoding to avoid conflicts.

Core Engine

Valid from Pega Version 7.1.4

This release contains fixes related to clipboard and declarative features, including data pages and autopopulate.

 

  • A rule may be changed using Private Checkout, and then checked into a higher RuleSet Version for that RuleSet.
  • Agents may now use a 24-hour time period for scheduling, as well as a 12-hour time period (which required the selection of AM or PM).
  • Caching and performance have been enhanced.
  • Declare expressions will work with embedded page lists when creating forms.
  • Mandatory parameters on a data page can handle blank values.
  • Properties may be auto-populated using a reference property which is created with a Property-Ref method in an activity.
  • System will use "private edit" rules in developer's personal RuleSet when that rule overrides the "standard" rule available to all.
  • The Page-Remove method will now remove Data Pages at the Thread level and the Requestor Level.
  • When copying a page using the "Set" action on a data transform, the Declare Indexes defined on that data will be updated.
  • When creating a data page, the Reload Once per Interaction checkbox can be checked to set the refresh strategy. 

Database

Valid from Pega Version 7.1.4

Improvements to data handling were made for search indexing, agent processing, and filtering.  Scripts were provided for proper population of the database tables.

 

  • Importing data from shared obj-external tables is now supported.
  • A validation warning will now display when an unexposed property is used in filter or join conditions.
  • A Global Search index may now be created across two databases.
  • Agent processing on multiple nodes has been improved.
  • Improvements were made to controls in Report Definition pages which are used in a dynamic grid.
  • Filtering functionality involving special characters has been enhanced.
  • Scripts have been provided to populate the RuleSetVersion Major, Minor, and Patch columns.

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