SR-133382 · Issue 205957
Updated paragraph styles in Security policy
Resolved in Pega Version 7.1.9
Using ie, the History tab and Policy Definition tab had incorrect content while viewing Security policy rules. This was found to be an issue with the styles present in the paragraph rule 'pzScriptSrcDescription', and the styles have now been updated.
SR-133538 · Issue 205317
Smart Prompt fixed for DT column headers
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-133538 · Issue 204972
Smart Prompt fixed for DT column headers
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-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.