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-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-123525 · Issue 186662
Added handling to maintain f ordered list styles in send correspondence
Resolved in Pega Version 7.1.9
In the send correspondence, if the ordered list format was selected and then deselected and again selected, then the bullet points or numbers appeared differently. Handling has been added to maintain the correct appearance through multiple changes.
SR-125651 · Issue 189974
Error icons and localization corrected for repeating tabs headers
Resolved in Pega Version 7.1.9
The error message indication was not appearing on the tab header of repeating tabs. In addition, the tooltip of that icon was not being correctly localized. These issues have been corrected.
SR-127915 · Issue 203511
Resolved NPE for URLEncryption in grids
Resolved in Pega Version 7.1.9
When URLEncryption is enabled in a grid scenario, the property reference was not generated as expected. In this scenario, the AjaxTrackID was not being passed from client to server due to it being a new harness load where normally a new AjaxTrackID would be created at the server end. To resolve this, the pzActionOpenURLInWindow API has been updated.