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-133538 · Issue 205317

Smart Prompt fixed for DT column headers

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.9

Smart Prompt was not working when configuring Decision Table column headers. The Decision table rule (including the smart prompt control and pages&classes tab) was updated as part of rule form conversion from form-based to harness-based. However, the smart prompt is loaded in a separate frame and did not have the necessary access to the decision table rule which contained page&classes values. While there was a workaround of manually typing in and saving the 'page.propertyname', this has been corrected.

SR-131055 · Issue 201905

JNDIurl information picked up for Transport rule test scenarios

Resolved in Pega Version 7.1.9

JNDIurl information was not being picked up from the Transport rule during the testconection flow even though the implementation logic was present at runtime. The proper function has now been added to the test scenario. In addition, handling was added for the retrieval of the destination name from endpoint URL when the endpoint URL doesn't contain '?'.

SR-132169 · Issue 202845

Addressed sporadic NPE while restoring passivated newassign pages

Resolved in Pega Version 7.1.9

A sporadic NPE error was appearing in a single node of a multi-node environment when attempting to restore the passivated page 'newAssignPage' for Thread STANDARD. This was traced to the absence of a null safety check while retrieving pagelists from xmlcontentmap, and this has been added.

SR-133179 · Issue 206242

Resolved outbound email data mapping error

Resolved in Pega Version 7.1.9

Email service was failing with the error message 'Outbound data mapping failed In ServiceHelper.getOutboundDataValue()'. This was traced to a new executable instance being created for the execution of a correspondence message and never popped out (causing it to stay in thread object forever). Stack popping has been added to fix the issue.

SR-133754 · Issue 203810

Enhanced handling for URLs with multiple Connect-REST parameters

Resolved in Pega Version 7.1.9

When there were two parameters present in a URL, the Connect-REST parsing was incorrect because only the outer braces were removed (the first brace from the first parameter and the second brace from the second parameter). To handle this correctly, the URL logic has been broken out into a separate activity. In addition, new information such as body and content type has been added to the results.

SR-129260 · Issue 196814

Improved passivation handling for long page names

Resolved in Pega Version 7.1.9

An issue where sporadic 'database serialization failed for requestor' errors were being logged was traced to certain page names that are very large. During passivation, if the pxInsName was larger than 128 characters, it did not fit in its associated column in the pr_page_store table and generated the error. It was also noted that while pzinskey is 255, pxinsname is 128. To resolve this error, pxinsname has been increased to 255, and DatabasePassivation will hash the page name for storage if it exceeds the maximum allowable length.

SR-129984 · Issue 203634

Error handling added for skin check-in

Resolved in Pega Version 7.1.9

A 'string index out of range' error when checking in a skin was causing the rule to hang. This was caused by an exception generated by the ordering of clipboard results, and handling for this has been added to resolve this problem.

SR-130496 · Issue 203385

Fixed ruleset cache population after passivation

Resolved in Pega Version 7.1.9

After a session was idled, a 'RulesetName not specified' error appeared during checkout when the session was resumed. This was an issue with SnapshotApplicationContext not being activated properly to populate the cache after passivation, and has been fixed.

SR-130754 · Issue 200600

Remove locale consideration from toDecimal string conversion

Resolved in Pega Version 7.1.9

The 'toDecimal' function was unable to convert the string to decimal properly when the user locale is set to Indonesia. As the 'toDecimal' RUF should not be doing localized conversions, this RUF has been updated to ignore user locale.

SR-131553 · Issue 203114

Passivation handling added to changelist

Resolved in Pega Version 7.1.9

A Rule-Declare-Index defined on a Context page property was intermittently failing to fire. This was traced to a missing changelist following passivation. Changelists were never originally designed to be passivated, but it is possible to passivate requestor or PRThreads which then affected the pages with changelists. The system has now been updated to properly passivate changelists in order to prevent this issue.

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