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-A5588 · Issue 212799

Added check to halt case progression if open assignments present in parallel flow

Resolved in Pega Version 7.2

If "Launch On Re-entry" was unchecked and parallel flows were present in the current stage, it was possible to progress to the next stage even if open assignments were present in the current stage. In addition, all steps in the parallel flow were created if the open assignments in the activated flow were completed. To avoid this, the stage history will be checked for all the stages whether or not the 'Stage on Re-entry' check-box is in use. Previously, only the last stage was checked: with this update. if the requested stage has any unprocessed flow missed in previous visit then it will be considered.

SR-A8496 · Issue 219309

Corrected page property setting for pxAddChildWork smart shapes

Resolved in Pega Version 7.2

The page property parameter was being ignored in favor of the WorkPage in the the pxAddChildWork activity. This should only have happened if the PageProperty Param was null or empty, but was occurring in scenarios where a child case was created using the Create Case smart shape. A check has been added to consider the top level page of the step page as the Primary Page parameter in order to prevent this issue.

SR-A11576 · Issue 222779

pzShowConflicts message localized

Resolved in Pega Version 7.2

Localization has been added for pzShowConflicts by adding the configurable field "pyMessageLabel.ShowConflictMessage".

SR-A11935 · Issue 223901

Application creation allowed without case selection

Resolved in Pega Version 7.2

When attempting to create an application based on CS 7.1.4 using the New Application Wizard with no cases selected, the application was not created and an error was displayed. This was traced to the RulesetName and rulesetversion params not being passed to the "pyPrepareFrameworkAssetsForGenerationPost" activity: those params are set only when Case Types from FW are selected. The system has now been updated to pass the RulesetName and rulesetversion params to the activity even when Case Types from FW are not selected.

SR-A9535 · Issue 218667

Localization added for stage names on audit history tab

Resolved in Pega Version 7.2

Localization has been added to the stage names present under the Audit > History tab of the work item.

SR-A11491 · Issue 223818

Updated security for "Attach a URL"

Resolved in Pega Version 7.2

A potential vulnerability has been closed in the "Attach a URL" functionality to ensure any code contained in the URL cannot be executed.

SR-A9299 · Issue 221030

Updated delete criteria for WorkObjectPage in clipboard

Resolved in Pega Version 7.2

When working with a very large amount of data in pyWorkPage, a copy of the workpage was appearing in the clipboard when the work object was resolved. This could result in a memory consumption issue. The WorkObjectPage was already being deleted conditionally when local.isPrimaryPageUsed is 'false', but the activity has now been updated to also delete the WorkObjectPage if local.isPrimaryPageUsed is 'true'.

SR-A7110 · Issue 216218

Case Narrative section of Audit localized

Resolved in Pega Version 7.2

Localization has been added to the Case Narrative section of Audit ( "pzFetchSubcaseAttachments" activity).

SR-A5412 · Issue 219159

Error marking fixed for TreeNavigation7 screen flow

Resolved in Pega Version 7.3.1

When using the TreeNavigation7 harness in the screen flow to call the validation from the post action, any property error in any of the flow-actions caused only the first flowaction to be marked as having an error while the rest were marked as successful. This has been fixed.

SR-A11956 · Issue 223935

Logic added to RUFs for Self-looping FlowAction

Resolved in Pega Version 7.2

In previous versions, it was possible to add a self-looping FlowAction on an AssignmentService shape. After upgrade, attempts to use this structure resulted in the error message ?Java generation failed; see log for details?. This was traced to handling for self-looping connectors logic not being included in the newly written pzGetDisplayableIncomingShapeIDs RUFs. This has been added.

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