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.

SR-132185 · Issue 205500

Corrected reference matching for relative pagegroup properties

Resolved in Pega Version 7.1.9

During page copy, the references in pagegroup property were becoming corrupted when given as a relative reference. Reference matching has been updated to resolve this.

SR-133606 · Issue 204762

Corrected reference matching for relative pagegroup properties

Resolved in Pega Version 7.1.9

During page copy, the references in pagegroup property were becoming corrupted when given as a relative reference. Reference matching has been updated to resolve this.

SR-133681 · Issue 206951

Added handling for two declare index rules on two pagelist properties in the same work class

Resolved in Pega Version 7.1.9

Given two declare index rules on two pagelist properties in the same work class, the second declare index was working while the first declare index was behaving inconsistently. It was found that even though there were two records for the property, at run time only the second record was getting inserted because only one insert command fired for Accounts Pagelist and the Declare index did not update even after using pzReindex is true. To ensure proper function firing, the system has been updated so when pzReindex is true, the existing pzIndexes page group value will not be considered.

SR-132637 · Issue 203591

Added path checking to FirstLogCreationTime.log

Resolved in Pega Version 7.1.9

FirstLogCreationTime.log was being written to a temp folder using hard-coded logic to use a relative path within the install directory. This caused errors if the installer was trying to write the logs in an absolute path. FirstLogCreationTime.log should be written to the same directory as the rest of the logs, and this issue has been fixed by adding a condition in LogDeleteUtil.getLogCreationTimeFile() method to check for absolute paths.

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-133747 · Issue 203813

Corrected hashtag handling for Oracle SQL generation

Resolved in Pega Version 7.1.9

Given a column name with a hashtag in an Oracle environment, the system was compiling SQL statements which caused ORA-00904 errors due to replacing the # in one variable name with an _ but leaving it as a # in another. This has been corrected.

SR-133057 · Issue 205124

System updated to better handle multi-node rule resolution

Resolved in Pega Version 7.1.9

In an upgraded multi-node environment, the error 'com.pega.pegarules.pub.database.MultipleRuleVersionException: Rule resolution identified 2 versions of the rule' was sporadically appearing. Once the issue occurred, it would persist and the only way to resolve it was to bounce the server. This was an issue with an instance of one rule being found in one node and not found in other node, and was related to the trigger logic. This should not occur with the current Pega7 version, as trigger logic has been moved into the engine and there is no longer a database trigger to fix. In order to ensure continued smooth trigger resolution, tests have been added that will check for this condition in the updates cache table to ensure that this scenario does not occur again

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