Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-B37923 · Issue 295190

null-pointer exception fixed for ForceCaseClose

Resolved in Pega Version 7.3

An exception was generated when running pxForceCaseClose due to an explicit call to the function before the Step Page was passed. This has been corrected.

SR-B39730 · Issue 301187

tempItem parameter added to createworkprocess API

Resolved in Pega Version 7.3

The parameter tempItem has been added to the createWorkProcess API to hold a temporary work object which is passed to AddWork activity. The same naming convention is used.

SR-B39792 · Issue 298418

Validation removed for survey name property

Resolved in Pega Version 7.3

If the survey driver parameter "survey" was configured with a property reference to provide the survey name in the subprocess SurveyDriver, adding validations to it caused the property panel to generate an error. This was due to Validations on the pySurvey property checking if the survey existed with the configuration. To avoid this, validations on the pySurvey property have been removed and an added required condition has been put on the pySurvey

SR-B41106 · Issue 298379

Bulk process with only 'case type any' properly assigns all processes

Resolved in Pega Version 7.3

When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.

SR-B41504 · Issue 299952

Tabbed navigation research wrap-up fixed

Resolved in Pega Version 7.3

Tabbed navigation Research interaction wrap-up was displaying the review harness instead of autoclosing. In order to resolve issues with the Autoclose harness being overridden, in cases where the user is not authorized to perform the assignment AND the harness is set as "Perform", the harness purpose will be set as "Review".

SR-B44001 · Issue 302395

Bulk Action filter handles rule withdrawn from landing page

Resolved in Pega Version 7.3

If a property was withdrawn in the Bulk Actions landing page, the other page properties no longer appeared in the Filter Property list. This was due to the getImmutableTerminalPropertyInfo function causing an exception whenever the rule availability was empty. To resolve this, the system will check the availability of the property rules in the "Rule-Obj-Property.LookupList" activity's 3rd step before processing/adding the embedded properties.

SR-B44787 · Issue 300852

work object lock released if nextAssignment is false

Resolved in Pega Version 7.3

The lock was not getting released on Work object creation even though back-to-back assignment processing was disabled for the flow. To correct this, the work object will be unlocked if the pynextAssignment parameter is false.

SR-B462 · Issue 271962

Event Late triggers expanded

Resolved in Pega Version 7.3

If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.

SR-B4620 · Issue 277531

Fixed dirty prompt save UI error

Resolved in Pega Version 7.3

The dirty prompt save action was causing corruption in the UI if there were validation errors present. This was traced to the On save of a work object with errors replacing the harness with section. As a result, styles and scripts in harness were lost and only plain/raw html was shown. This has been fixed by removing the Show-Stream step so Show-Harness takes care of refreshing the screen.

SR-B46718 · Issue 304110

pyFLowSLA property added to support pxObjClass change

Resolved in Pega Version 7.3

Validation errors occurred when using a data transform which changes the pxObjClass of primaryPage. Pega Platform tries to validate internally for all the properties during the page change class; in order to support the DT, the new property pyFlowSLA has been introduced. The previous pxFlowSLA property has been deprecated.

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