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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A99473 · Issue 266934

Documentation updated for Obj-Delete-By-Handle method

Resolved in Pega Version 7.2.2

The documentation for the Obj-Delete-By-Handle method has been updated to clarify that the Obj-Delete-By-Handle method will require the object to be locked if either the class or class group allows locking.

SR-A95291 · Issue 270315

Deprecated Access Groups documentation updated

Resolved in Pega Version 7.2.2

The documentation lead-in to the Deprecated Access Groups section has been updated for clarification: These access groups are retained after upgrades to support applications created in Version 4.2 and Version 5.X systems. They are deprecated and not recommended for continued use. These access groups appear only on systems that are upgraded from PRPC 6.x or earlier.

SR-A99855 · Issue 266703

Help file corrected for JSP tag

Resolved in Pega Version 7.2.2

The help for the JSP Tag "" is incorrect: It reads: example string of 'pyActivityName', but it should be 'pyActivity'. This has been fixed.

SR-A94342 · Issue 263882

Inserted missing word in property-set-html doc

Resolved in Pega Version 7.2.2

The missing word "is" has been added in In the doc article that comes up when the "?" is clicked while filling in the parameters for the property-set-html activity method, which previously read "Identify the property that to receive its value from stream processing".

SR-A76148 · Issue 251342

Documentation updated for running BIX from the command line

Resolved in Pega Version 7.2.2

When attempting to run BIX from the command line within a Linux environment, an error is thrown: Error: Could not find or load main class com.pega.pegarules.data.internal.access.ExtractImpl This was a local error in the setup of the bix.sh script, and the BIX documentation has been updated to clarify the requirements.

SR-A77514 · Issue 239717

@baseclass!pyMemo has been made available

Resolved in Pega Version 7.2.2

Opening up property pyMemo (which applies to Link-) and trying to save it into a custom ruleset generated an error due to @Baseclass having a final version of pyMemo. To correct this, @baseclass!pyMemo has been made available.

SR-B5634 · Issue 274715

Stack frame handling made more robust

Resolved in Pega Version 7.2.2

Stack frame handling has been made more robust to prevent the stack trace from getting out of sync in cases where the strategy execution throws an exception.

SR-A89757 · Issue 258099

SaveAs history carries previous version and ruleset info

Resolved in Pega Version 7.2.2

When saving as a rule from particular version, the rule history did not correctly carry over the information about the origin ruleset version (Previous version and ruleset) This was an error caused by recent changes to the WBSaveAs record management API, and has been fixed with new parameters added to "call SaveAs" on Rule-!WBSave into the record management API.

SR-D37415 · Issue 508967

Parameter page update added to improve backwards compatibility for ShowTestLibraryTab

Resolved in Pega Version 8.2.4

An error was observed on the first attempt to modify the 'when' rule "ShowTestLibraryTab" located in PegaProjectMgmt:08-01-01. Analysis showed the when rule (Always, Never) which was called from this rule was not found, which was an issue traced to the Rule-Obj-When function alias parameter name being changed from "strWhen" to "blockName" in the 8.1 release. Subsequent attempts to save the modified rule succeeded due to step#7 in the Embed-UserFunction.pzPopulateDropdownFBUIParameters activity upgrading the pyParameters page with the latest data. To resolve this backwards compatibility issue, the activity step#6 has been modified to upgrade the parameter name for the Rule-Obj-When function alias.

SR-D38053 · Issue 508225

Upcase case shape will fall back to pyWorkCover if multiple pages are present

Resolved in Pega Version 8.2.4

In the Update a Case shape, selecting "A Single Case" and providing .pxCoveredInsKeys(1) for the With ID field worked as expected, but using the same data transform and selecting either "All child cases and descendants" or a specific child case resulted in no update on the children. This was traced to the findPageByHandle API not returning the most appropriate page, which created an issue whenever multiple pages were present in the clipboard. To correct this, the system has been updated to use pyWorkCover if present.

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