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.

Geolocation tracking requires browser permission

Valid from Pega Version 7.1.6

When the geolocation tracking feature is enabled, a Map it link appears next to each requestor entry in the audit trail. When you click a link for the first time, the browser displays a notification asking whether you want to permit tracking. Make your yes/no selection in the prompt. Do not click "X" to close it, as doing so may render the session unresponsive. Refresh the browser if necessary and make your selection.

Geolocation tracking Map it links do not appear

Valid from Pega Version 7.1.6

If geolocation tracking is enabled, the first time you create a case in the first browser session, the Map it links do not appear next to the initial audit trail entries. When you submit the first flow action, the links appear next to all subsequent entries.

Add additional columns to customized work history tables

Valid from Pega Version 7.1.6

The standard work history table, pc_history_work, contains two new columns that return the latitude and longitude coordinate location of the action that prompted the history. Mobile devices can display this location as a street address. If you have a customized work history table, add these two columns to it:

  • <decimal name="pxLatitude" size="19" scale="9"/>
  • <decimal name="pxLongitude" size="19" scale="9"/>

Node description cannot match application server node name

Valid from Pega Version 6.3 SP1

A node's Short Description should not be the same value as the application server node name. If the node's Short Description is changed to be the same value as the application server node name, then the node description is automatically changed back to the original value after a system restart.

No longer supported translator configuration options

Valid from Pega Version 7.4

The following translator configuration options are not needed and are no longer supported. If you previously configured any of these system settings, remove them from the system settings to avoid a warning message. For example, if you set translator/useparserfamily, the following message is displayed at startup: "Translator option, 'translator/useparserfamily' is not needed and no longer supported. Remove this from the system settings."

  • translator/useparserfamily
  • translator/usecodegenerator
  • translator/usenativedouble
  • translator/optimization/use71BlockAnalysis
  • translator/optimization/use71ConstantFolding
  • translator/optimization/use71AssignmentTypeSimplification
  • translator/optimization/use71IntrinsicFunctions
  • translator/use71PropSetGeneration
  • translator/use71ParserAssignment
  • assembly/model/useBlock4ContiguousSets
  • /translator/pandc/comparepandcalgorithms
  • /translator/pandc/use6xalgorithms
  • /Compatibility/CheckForTopLevelClassMismatch

In addition, the com.pega.pegarules.generation.parseoverride bootstrap option is no longer supported. Remove this option from the system settings.

pxFeed replaces pxContextFeed and pxActivityFeed Pulse gadgets

Valid from Pega Version 7.4

The pxContextFeed and pxActivityFeed gadgets have been replaced by the pxFeed gadget to integrate the functionalities of viewing and posting messages in the Pulse activity feed. You can include this gadget within a section or harness across your application, for example, in the dashboard of the Case Manager portal, to display the activity feed. You must add the latest UI Kit ruleset to ensure that your application uses the pxFeed gadget instead of the pxContextFeed and pxActivityFeed gadgets to generate the activity feed.

For more information, see Pulse gadget and custom APIs.

Survey rules are deprecated

Valid from Pega Version 7.4

Surveys that were created prior to version 7.4 of Pega Platform are now deprecated. As a best practice, recreate your survey by using the Survey Management landing page, and then reuse questions or question pages from your survey library.

For more information about creating surveys, see Improved survey authoring.

Questionnaire shape replaces Survey shape in legacy flows

Valid from Pega Version 7.4

In flows that reference deprecated surveys, the Questionnaire shape has replaced the Survey shape. Although legacy surveys continue to function in this release, update your flows to use the Survey shape because it provides the latest survey capabilities, and deprecated features are not supported.

For more information about the new survey authoring experience, see Improved survey authoring.

Limited question and answer formats in new surveys

Valid from Pega Version 7.4

Complex questions and some answer formats for simple questions, such as attachment, are not supported by the new surveys that you create. Although you can create stand-alone questions in your survey library that use these formats, you can add these questions to legacy surveys only.

For more information about supported answer formats, see Answer formats for questions in a survey.

PegaDATA connection settings now required in the prconfig.xml file

Valid from Pega Version 7.4

If you use the default prconfig.xml file that is included with Pega® Platform, and you have not removed the PegaDATA connection settings, no action is required. If you use a custom prconfig.xml file, for example, for running tests, ensure that the database connection settings for PegaDATA are not blank.

For more information about the connection settings, see PegaDATA connection settings in the prconfig.xml file.

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