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-A94493 · Issue 262430

JSON error resolved for empty section render

Resolved in Pega Version 7.2.2

While rendering a section, a JSON error was thrown in the console that prevented all click actions on the screen. Analysis showed this was due to an extra comma that was present when the page doesn't have any values, and has been fixed with a check that will only add the comma after DataPage scope after confirming the page is not empty.

SR-A96096 · Issue 264802

Tenant hash preserved for SOAP to accommodate load balancer SSL termination

Resolved in Pega Version 7.2.2

With Cloud 2.1, there was a need to set prconfig settings in order to accommodate SSL termination at the load balancer side, but the SOAP messages between a client (tenant) and PDC were having their tenant hash stripped by the engine. This was due to SOAP requests made to a specific Tenant by a monitored node (client) of PDC(MT) being redirected to a Shared tenant in PDC. To resolve this, even when "initialization/contextrewriteenabled" is set to true, the value for "pxReqPathInfo" will be set by HttpRequestMapper.buildRequestorDataFromHttpRequest() in the Map returned by it.

SR-A87407 · Issue 265098

XML stream assembly handles parentheses

Resolved in Pega Version 7.2.2

XML stream assembly was not properly handling parentheses; this has been fixed.

SR-A100503 · Issue 268474

Harness name field in flow accepts expression

Resolved in Pega Version 7.2.2

After upgrade, a harness issue was encountered where the generated flow was treating the pxFormName as String literal instead of Expression. This caused an error when trying to save a flow. To correct this, FlowFUA PopulateFlowActions function code used for Expression parsing in the harness has been updated.

SR-A93826 · Issue 264612

Corrected Field level audit issue

Resolved in Pega Version 7.2.2

Field level auditing was creating two extra "TrackSecurityChange_Change" entries when a new item was added to a Page List at the same time an existing item was removed. It was also updating audit incorrectly the item value was changed for one row at the same time another row was added. This has been fixed by modifying the Memo audit functions to update the values correctly on save when an entry or row is added/edited and other is removed.

SR-A86001 · Issue 259595

Extraneous row removed from field level auditing

Resolved in Pega Version 7.2.2

When tracking a Page list property, an extra row was being appended in the repeat layout. A null check has been added to correct this.

SR-B2033 · Issue 272929

Help doc corrected for Clipboard save location

Resolved in Pega Version 7.2.2

An error in the help file indicated the Save feature in the Clipboard Viewer should save to the database. In Pega 7, the Save feature in Clipboard Viewer only saves the page in memory and does not perform any database transactions, and the documentation has been updated to reflect this.

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.

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