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-B2191 · Issue 275647

Fixed Chrome position resetting with proposition change

Resolved in Pega Version 7.3

When duplicating a proposition in Chrome, any change in an attribute refreshed the screen and reset the scrollbar all the way to the top. This has been fixed.

SR-B2228 · Issue 273457

WordTextArea control updated for IE

Resolved in Pega Version 7.3

Erratic behavior was seen in saving and displaying a Word document when launched from the WordTextArea control. This was a compatibility issue with IE, and the DoLaunchExtWord function has been modified to fix this.

SR-B2362 · Issue 274142

Corrected newline comparisons for pega.comparePages

Resolved in Pega Version 7.3

When mapping an external table partially to PRPC class, updating the table with Obj-Save caused the un-mapped columns to be updated to null. This was due to the comparePages API not doing an appropriate comparison whenever a property in one of the pages had a new line as a CR ("\r\n") and in the other page had new line("\n"). This has been corrected.

SR-B2591 · Issue 273763

Resizing delegated decision table works

Resolved in Pega Version 7.3

Attempting to resize a Decision table column that had been delegated to a business user was not working due to an actionable border not being defined. This has been fixed.

SR-B2595 · Issue 274239

Enabled process cleanup for change stage shape

Resolved in Pega Version 7.3

When using the "Approve\Reject" step in case designer on a flow containing logic to jump back to a previous stage on rejection, the system created the new assignment needed for jumping back to the previous stage but did not clean up the existing assignment. This caused two parallel flows at the same time and the old assignment was loaded on the screen. This has been fixed by enabling the CleanUpProcesses parameter in the Change stage shape function of pzPostApprovalActions.

SR-B26249 · Issue 290765

Flickering in Tabbed Layout header corrected

Resolved in Pega Version 7.3

In a Tabbed Layout with four tabs using expandable Repeat grid sections, the first column table header had extra grey space generated intermittently. The pzpega_ui_Grid js file has been updated to correct this.

SR-B26257 · Issue 288790

Fixed SMA broken item requeue

Resolved in Pega Version 7.3

When attempting to requeue a broken item using the SMA, the requeue failed with an error about Attribute Based Access Control. This was traced to the API passing a thread object that did not have any executable associated with it; the system will now create a new executable instance if the getThread().retrieveContext() is null.

SR-B269 · Issue 284289

Multinode SOAP made more robust for rule resolution

Resolved in Pega Version 7.3

After updating an application rule on a multinode environment, SOAP service stopped working and generated the error "Failed to open Rule-Parse-XML record". In this case, the application index was written to the DB after updating in-memory variables, leading rule resolution to search in the DB with the wrong application hash. To avoid this, the system will now write the DB index first then update in-memory variables.

SR-B2709 · Issue 276670

Fixed OOM exception during DL import on JVM

Resolved in Pega Version 7.3

An OOM exception was generated during DL import on JVM when the DL being deployed had an very large number of hotfixes relating to CarDirectories. This was traced to each directory deployment creating a new instance of JarLoaderTool to internally build the cache (VersionedJdbcJarReader) which was then never cleared from the Mbean cache. This has been corrected by adding a check to release memory.

SR-B2709 · Issue 272341

Resolved ConcurrentModification exception in getclass name

Resolved in Pega Version 7.3

Attempting to getclass name while iterating over values of mPageProperties in expandAllToProperties (in the putPropertyOntoClipboard call) was causing a ConcurrentModificationException that resulted in queues being blocked and loss of synch to the server. In order to more cleanly set the pxObjClass for the classless page-properties, pxObjClass has been added to the lookupDictionaryDefinition.

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