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-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-133557 · Issue 202993
Schema URL' field in Parse XML rule now supports Global Resource Settings
Resolved in Pega Version 7.1.9
The 'Schema URL' field in Parse XML rule now supports Global Resource Settings (GRS), and the developer help documentation has been updated to reflect this.
SR-A1538 · Issue 209276
prvisiointerface.cab unblocked
Resolved in Pega Version 7.1.9
Effective with earlier ML versions of Pega7, several OCX functions were intentionally deprecated and replaced with Silverlight functions: Prbatchscanning prDeveloper prpackagecominterface prvisiointerface. However, it was found that there are two Word features around the embed merge function requiring prvisiointerface.cab that will produce some visual problems on the screen referring to the missing cab break if the files are ported from an earlier version of PRPC and prvisiointerface.cab is unavailable. Therefore, prvisiointerface.cab has been unblocked and restored for use.
SR-A2027 · Issue 205651
Reworked decision table conflict check logic for combined rows
Resolved in Pega Version 7.1.9
In a decision table, using expressions like property-property caused the decision table to report a non-existent logic conflict because there was another column with different data present. This has been fixed by adding a new property pyColumnDataType for Decision tables which will hold the data type of the expression/function/property mentioned in the column during FUAssembly, and then using it in the testConsistency code instead of the existing design.
SR-A204 · Issue 205451
Resolved sporadic NPE on TransferAssignment
Resolved in Pega Version 7.1.9
A null pointer exception was sporadically being being generated by the pxTransferAssignment activity. This was found to be an issue where a previous step to open the work object failed and the TransferWorkPage was therefore not created, followed by the absence of that page leading to the failure of the WHEN condition that was using the Rule-Utility-Function hasMessages. The handling has been updated to avoid this issue.
SR-A2047 · Issue 205630
Resolved AddWorkHistory length error
Resolved in Pega Version 7.1.9
The "AddWorkHistory? activity was generating an error when the property pyInstructions contained more than 64 characters and was copied into pyLabel without taking care of the length restrictions imposed on these properties. This has been resolved by implementing the required length restrictions before copying.