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-B92674 · Issue 349429

Added check to prevent pxFlow page corruption

Resolved in Pega Version 7.4

The code in Work-!ReassignToWorkBasket assumed that if the property pxFlow existed then newAssignPage.pxFlowName must also exist, and went on to use the pxFlowName as a subscript to set several properties on the pxFlow page. If pxFlow existed but as an empty Page Group, there was no pxFlowName and the pxFlow page group ended up with a corrupted work object. This has been fixed by adding an additional check for the pxFlowName on newAssignPage. If the flow name is empty, the property will not be set.

SR-B94982 · Issue 343407

Check added to prevent looping on nested data flows

Resolved in Pega Version 7.4

It was not possible to create a data flow run via the UI that contained a different data flow as its primary source because pzDataFlowContainsEventStrategy is a recursive function with the potential to loop forever when one of the sub-dataflows is the same as the current dataflow. To enhance use of this function, a check has been added to prevent the function from calling itself if the sub-dataflow is the same as the current dataflow.

SR-C11188 · Issue 352704

Backwards progress restored for unsaved cases

Resolved in Pega Version 7.4

If an unsaved case was quit from the middle of a flow, "previous" was no longer working when the application was exited and a new login session was started. When attempted, the pop-up error "This action does not work" appeared. It was possible to go forward with the flow from this point, but it was not possible to proceed backwards beyond the new start point. This occurred when going back from a subflow (a) through another subflow without shapes, then into another subflow (b) when the intervening subflow had no cases, and was due to incorrect placement in the code of the needed pyCompletedSubFlowPath. This has been corrected.

SR-C155 · Issue 343722

Flow parsing modified to accommodate new DP syntax

Resolved in Pega Version 7.4

DE was generating the error "declare page parameters not supported by PropertyRef". This was traced to the PropRefPool not being able to handle the '[' character which is part of the new DP syntax; since the parsing call with this conflict is contained in the flow but is not absolutely necessary in this stage, the system will skip the parsing at this point to avoid the error.

SR-C6264 · Issue 348027

Change stage fixed for backwards compatibility

Resolved in Pega Version 7.4

After upgrade, the stage name was incorrect on change stages utility shapes. This was traced to a backwards compatibility issue with new handling in the pzChangeStage section and has been corrected.

SR-C7459 · Issue 349535

Flow action label not reset after local action

Resolved in Pega Version 7.4

After creating a flow action where the ID and short description were different, after the local action was launched and then closed the Flow action short description displayed as expected but the Flow action label displayed the ID instead of the short description. In this case, when a local action is launched the ProcessAction activity triggers the PerformPreProcessing activity, but that activity was passing TaskIndex as Empty. This was causing the Current Action Label to be set to empty, and a check has been added to avoid that condition.

SR-B65131 · Issue 330322

Fixed 'when' rules for showing privileged escalation buttons

Resolved in Pega Version 7.4

Privileged escalation was displayed for a user with access to manager reports due to missing 'when' rules for hiding the Add report/Add category buttons. This has been fixed.

SR-B67967 · Issue 330128

Data explorer displays all associations and optimized nested properties are supported

Resolved in Pega Version 7.4

The rule resolved RDB query used to list the associations for the report class was not returning all associations. The logic for this has been modified to use a rule resolved report definition to correct the issue. In addition, the pzAddPropListForClass_TreeGrid function has been refactored in order to correctly support nested properties.

SR-B67967 · Issue 331406

Data explorer displays all associations and optimized nested properties are supported

Resolved in Pega Version 7.4

The rule resolved RDB query used to list the associations for the report class was not returning all associations. The logic for this has been modified to use a rule resolved report definition to correct the issue. In addition, the pzAddPropListForClass_TreeGrid function has been refactored in order to correctly support nested properties.

SR-B72915 · Issue 331477

Correct day calculated for AU timezone

Resolved in Pega Version 7.4

The Report Filter is subtracting one day when the timezone was set to Australia/Sydney. This was caused by an error in pyUILabel, and has bene fixed.

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